# Aaai Supplementary

Use when organizing AAAI supplementary material, including the technical appendix...

- Repository: https://github.com/brycewang-stanford/Awesome-Journal-Skills (1346 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-supplementary -g -a claude-code -y`
Codex: `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-supplementary -g -a codex -y`
Cursor: `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-supplementary -g -a cursor -y`
Gemini CLI: `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-supplementary -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add brycewang-stanford/Awesome-Journal-Skills`

## Description

Use when organizing AAAI supplementary material, including the technical appendix, multimedia appendix, and code/data ZIPs, while respecting that AAAI supplements are due with the paper, treated as immutable after submission, must stay double-blind, and should never hide main-paper-critical evidence from reviewers who skim the appendix.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# AAAI Supplementary

Use this when deciding what belongs in the main paper, technical appendix, multimedia appendix, or
code/data ZIP. AAAI supplementary material is due with the paper and should be treated as immutable
once submitted unless current instructions say otherwise.

## Supplement structure

- Keep the central contribution, method, core results, and checklist-relevant evidence in the main
  paper.
- Put proofs, extra ablations, extended qualitative examples, implementation details, and additional
  error analysis in the technical appendix.
- Put videos, audio, interactive demos, or visualizations in a multimedia appendix only when they are
  technically necessary.
- Put scripts, datasets, logs, model configs, and checkpoints in code/data ZIPs.
- Add a compact appendix map so reviewers can find support for each disputed claim.

## Anonymity and immutability

- Remove identity from file names, metadata, paths, Git history, author comments, and license
  headers.
- Do not use web pointers for extra material if current AAAI rules disallow them.
- Submit final, uncorrupted files. Do not rely on rebuttal to repair missing content.
- Keep the supplement consistent with the reproducibility checklist.

## Where each item belongs

A broad-AI reviewer will skim the appendix, not study it, so placement decides whether evidence is
actually seen. Anything a claim depends on belongs in the main paper; the appendix only deepens it.

| Material | Main paper | Technical appendix | Multimedia | Code/data ZIP |
| --- | --- | --- | --- | --- |
| Core result | yes | no | no | no |
| Full proof | sketch | full | no | no |
| Extra ablation | summary | detail | no | no |
| Demo of behavior | no | no | yes | no |
| Scripts and configs | no | no | no | yes |

## Reviewer-pushback patterns

The rest: https://github.com/brycewang-stanford/Awesome-Journal-Skills/blob/HEAD/AAAI-Skills/skills/aaai-supplementary/SKILL.md