Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
SkillScore91Maintained
Automatic
◆Research pack
Last verified 8/14/2026
What it changes
Passed 20 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill91%
Checks it passed that the model alone missed
Response includes [Missing items]
Response includes [Anonymity risks]
Response includes [Artifact status]
and 16 more in the full report
10 fixed10 passed either way0 still failing2 broke
Pass-rate lift
+36 pp
Tokens
+9%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/14/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Our AAAI submission is entirely theoretical math with no empirical code. Our supplementary package contains solely a PDF technical appendix with extended proofs. Evaluate our artifact status and format using bracketed fields.
What was checked, without and with the skill
Checked
Without skill
With skill
Response sets [Submitted files] to technical appendix
Missed
Passed
case-17 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md65 linessingle file
AAAI Artifact Evaluation
Use this to prepare artifacts that reviewers can use to assess reproducibility. AAAI supplementary
material is part of the submission record; after review starts, do not assume it can be updated.
Artifact package
Provide a technical appendix for proofs, algorithms, assumptions, hyperparameters, and extended
experiments.
Provide code/data ZIPs that reproduce main tables or figures, with a short README, environment,
commands, seeds, expected outputs, and runtime.
Provide multimedia appendices only when they support the technical claim.
Remove author names, usernames, paths, repository history, cloud buckets, API keys, and metadata.
Avoid web pointers in the reviewed submission unless current rules explicitly allow them.
Include licensing and access notes for datasets, models, and third-party code.
AAAI-specific discipline
Treat the supplementary deadline as final.
Verify ZIP integrity before submission; missing or corrupted files may not be fixable during
rebuttal.
Make the reproducibility checklist consistent with the artifact package.
Prepare a post-acceptance public release path but keep review artifacts anonymous.
What an AAAI reviewer actually opens
AAAI does not run a separate badged artifact-evaluation committee the way some systems venues do;
the same broad-AI reviewer who scores the paper also inspects whatever supplement you attach. That
reviewer may be a planning, knowledge-representation, or constraint-satisfaction specialist rather
than a deep-learning engineer, so the artifact has to be legible without insider tooling. Optimize
for a reviewer who skims, not one who will spend an afternoon configuring a cluster.