SkillAgentSearch skills...

aaai-supplementary

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…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-supplementary

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of aaai-supplementary

aaai-supplementary scores 83/100 on our quality scale, 2894th of 4,610 Development & Engineering skills we index.

Its SKILL.md is 3.3 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 18 days ago, so aaai-supplementary is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

aaai-supplementary compared with similar skills

All 4 of these similar skills score higher than aaai-supplementary; compare them before choosing.

SkillScoreStarsUpdatedFormat
aaai-supplementary (this skill)by brycewang-stanford831.2k18d agoSKILL.md
ai-job-searchby MadsLorentzen10044.8ktodayCLAUDE.md
claude-howtoby luongnv8910041.7k3d agoCLAUDE.md
algorithmic-artby anthropics100177.9k10d agoSKILL.md
pptxby anthropics100177.9k10d agoSKILL.md

Frequently asked questions

How do I install aaai-supplementary?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-supplementary. The install tabs above show the steps for each supported agent.
Which AI agents does aaai-supplementary work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aaai-supplementary safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aaai-supplementary still maintained?
The repository was last updated 18 days ago, so aaai-supplementary is actively maintained.

name: aaai-supplementary 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.

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 key result is only in the appendix." Fix: promote it to the main paper; AAAI reviewers are not obligated to find a load-bearing claim buried in supplement.
  • "Supplement contradicts the checklist." Fix: reconcile every appendix number with the checklist before submission, since neither can be edited later.
  • "Multimedia is huge but adds nothing." Fix: drop spectacle clips; include video only when it is the evidence, not decoration.

Worked vignette

A vision paper hides its ablation table in the ZIP and leaves only a teaser figure in the paper. The navigation map exposes the gap: a disputed claim points to a file a skimming reviewer will miss. The fix moves the ablation summary into the main paper, keeps full per-class numbers in the technical appendix, and scrubs the ZIP's metadata so nothing deanonymizes the immutable supplement.

Output format

[Supplement plan] technical appendix / multimedia appendix / code-data ZIP / none
[Main-paper dependencies] <material that must not be hidden in supplement>
[Navigation map] <claim -> supplement file/section>
[Anonymity risks] <paths, metadata, links, ownership>
[Submission risk] <missing/corrupt/too large/not allowed>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated18d ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions