aaai-artifact-evaluation
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 AA
- Artifact package
- AAAI-specific discipline
- What an AAAI reviewer actually opens
- Phase-1 artifact red flags
- Worked vignette
- Output format
What does the aaai-artifact-evaluation skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.