ijcai-supplementary — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ijcai-supplementary (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this when assembling or auditing IJCAI supplementary material. Reopen the current CFP and FAQ because deadlines, file types, and size limits are cycle-specific.
material into the technical supplement.
not use separate later deadlines for these files.
material in PDF or ZIP format.
screenshot, notebook output, and URL.
OS files, credentials, API keys, or large irrelevant artifacts.
IJCAI reviewers may never open the supplement, so placement is a scoring decision. Sort each artifact before assembling.
| Artifact | Where it belongs | Why |
|---|---|---|
| Theorem statement, main result table | 7-page body | Load-bearing; reviewers must see it without the supplement |
| Full proof, extra derivations | Technical Appendix | Supports credibility but not required reading |
| Hyperparameter grids, full per-domain tables | Technical Appendix | Detail that would crowd the body |
| Runnable code, simulator, instance generator | Code/data ZIP | Reproducibility evidence reviewers may sample |
| Prior reviews and rejected version | Resubmission File only | Must stay out of the technical supplement |
A planning paper has a soundness theorem, a 40-domain coverage table, and a planner implementation. Decision: the theorem statement and a condensed coverage summary stay in the body; the proof and the full 40-domain table go to the Technical Appendix; the planner plus a deterministic instance generator and seeds go in the ZIP; nothing from a prior IJCAI rejection goes anywhere except the Resubmission File. This keeps the paper self-contained while giving a skeptical search/planning reviewer a re-runnable artifact.
appendix should deepen, not define, the contribution.
anonymity or policy flag.
strip OS and cache files before the full-paper deadline, since there is no later upload.
[Supplement status] Ready / Needs fixes / Not ready
[Files] <technical appendix / code-data zip / resubmission file>
[Deadline coupling] <same as full paper? source needed>
[Anonymity checks] <passed/issues>
[Reviewer dependency] <what breaks if supplement is ignored>~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.