/aamas-supplementary
Use when preparing AAMAS supplementary material - proofs, extended game and mechanism definitions, extra multiagent experiments, opponent-set details, and the anonymized artifact zip - under the size cap, anonymity, and reviewer-discretion limits, including how to split a
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-supplementary --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/aamas-supplementary
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when preparing AAMAS supplementary material - proofs, extended game and mechanism definitions, extra multiagent experiments, opponent-set details, and the anonymized artifact zip - under the size cap, anonymity, and reviewer-discretion limits, including how to split a
SKILL.md
aamas-supplementary.SKILL.mdname: aamas-supplementary
description: Use when preparing AAMAS supplementary material - proofs, extended game and mechanism definitions, extra multiagent experiments, opponent-set details, and the anonymized artifact zip - under the size cap, anonymity, and reviewer-discretion limits, including how to split a game-theory-plus-experiments paper across the 8-page body and the supplement.
AAMAS Supplementary
Use this when assembling AAMAS supplementary material. The supplement can support the paper, but the 8-page main submission must stand on its own; a body that is unintelligible without the appendix reads as unreviewable within the page limit.
Supplement structure
- Put full proofs, extended game and mechanism definitions, extra ablations, opponent-set
documentation, and robustness tables in a clean appendix or supplementary document.
- Put executable assets - game code, environments, learning rules - in the anonymized zip when
the current OpenReview form allows it.
- Respect the current supplement size cap (25 MB single zip in 2026) and the deadline.
- Keep every supplementary file double-blind: no authors, institutions, acknowledgements,
private paths, repository owners, or identifying metadata.
- Do not hide essential motivation, the core game definition, the main theorem statements, or
the primary interaction results in the supplement.
- Verify the archive opens on a clean machine and carries no credentials, caches, or OS
metadata.
Appendix architecture for proofs and games
- Order appendix sections to mirror the body: game and notation, main proofs, auxiliary lemmas,
additional agents/opponents, then extended experiments.
- Restate each theorem and the relevant game before its proof so the appendix reads standalone
without flipping back to the two-column body.
- Keep one proof sketch and the full game definition in the body itself; an AAMAS paper whose
entire strategic argument lives in the appendix cannot be judged in eight pages.
- Cross-reference every appendix table, lemma, and opponent set from the body at least once;
orphaned supplement material is invisible under reviewer discretion.
What gets opened first
| Supplement item | Inspection likelihood | Practical implication | |---|---|---| | Proof of the headline equilibrium/mechanism result | High | Polish to main-text standard | | Extended game or environment definition | High | Reviewers reconstruct the interaction from it | | Extra opponent/population results | Medium | Reference each from the body | | Code/environment archive | Variable, reviewer discretion | README must orient a reader in one minute | | Raw episode logs | Low | Include for completeness, never rely on them |
Vignette: splitting a mechanism-design paper
A submission proving a truthful decentralized mechanism plus a self-play study: the body keeps the mechanism definition, the dominant-strategy theorem, one proof sketch, and the two decision-critical figures (truthfulness under learning and the efficiency gap); the appendix holds full proofs and sensitivity sweeps; the zip carries the game generator and the strategic-deviation harness. Nothing decision-critical lives only in the zip, because archive inspection is discretionary.
Output format
[Supplement status] Ready / Needs fixes / Not ready
[Files] <appendix/proofs/game-defs/code/logs>
[Size/deadline] <current cap and deadline with source>
[Anonymity checks] <passed/issues>
[Main-paper dependency] <what breaks if supplement is ignored>
Read more
name: aamas-supplementary description: Use when preparing AAMAS supplementary material - proofs, extended game and mechanism definitions, extra multiagent experiments, opponent-set details, and the anonymized artifact zip - under the size cap, anonymity, and reviewer-discretion limits, including how to split a game-theory-plus-experiments paper across the 8-page body and the supplement.
AAMAS Supplementary
Use this when assembling AAMAS supplementary material. The supplement can support the paper, but the 8-page main submission must stand on its own; a body that is unintelligible without the appendix reads as unreviewable within the page limit.
Supplement structure
- Put full proofs, extended game and mechanism definitions, extra ablations, opponent-set
documentation, and robustness tables in a clean appendix or supplementary document.
- Put executable assets - game code, environments, learning rules - in the anonymized zip when
the current OpenReview form allows it.
- Respect the current supplement size cap (25 MB single zip in 2026) and the deadline.
- Keep every supplementary file double-blind: no authors, institutions, acknowledgements,
private paths, repository owners, or identifying metadata.
- Do not hide essential motivation, the core game definition, the main theorem statements, or
the primary interaction results in the supplement.
- Verify the archive opens on a clean machine and carries no credentials, caches, or OS
metadata.
Appendix architecture for proofs and games
- Order appendix sections to mirror the body: game and notation, main proofs, auxiliary lemmas,
additional agents/opponents, then extended experiments.
- Restate each theorem and the relevant game before its proof so the appendix reads standalone
without flipping back to the two-column body.
- Keep one proof sketch and the full game definition in the body itself; an AAMAS paper whose
entire strategic argument lives in the appendix cannot be judged in eight pages.
- Cross-reference every appendix table, lemma, and opponent set from the body at least once;
orphaned supplement material is invisible under reviewer discretion.
What gets opened first
| Supplement item | Inspection likelihood | Practical implication | |---|---|---| | Proof of the headline equilibrium/mechanism result | High | Polish to main-text standard | | Extended game or environment definition | High | Reviewers reconstruct the interaction from it | | Extra opponent/population results | Medium | Reference each from the body | | Code/environment archive | Variable, reviewer discretion | README must orient a reader in one minute | | Raw episode logs | Low | Include for completeness, never rely on them |
Vignette: splitting a mechanism-design paper
A submission proving a truthful decentralized mechanism plus a self-play study: the body keeps the mechanism definition, the dominant-strategy theorem, one proof sketch, and the two decision-critical figures (truthfulness under learning and the efficiency gap); the appendix holds full proofs and sensitivity sweeps; the zip carries the game generator and the strategic-deviation harness. Nothing decision-critical lives only in the zip, because archive inspection is discretionary.
Output format
[Supplement status] Ready / Needs fixes / Not ready [Files] <appendix/proofs/game-defs/code/logs> [Size/deadline] <current cap and deadline with source> [Anonymity checks] <passed/issues> [Main-paper dependency] <what breaks if supplement is ignored>
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /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.
Open skill - /aaai-author-response
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round
Open skill - /aaai-camera-ready
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and
Open skill - /aaai-experiments
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and
Open skill - /aaai-related-work
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a
Open skill - /aaai-reproducibility
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that
Open skill

