/aamas-reproducibility
Use when strengthening AAMAS reproducibility evidence for interaction claims, including proofs and game definitions, opponent and population sets, self-play protocols, random seeds, compute, uncertainty on strategic outcomes, baselines, and consistency between what the paper
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-reproducibility --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-reproducibility
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when strengthening AAMAS reproducibility evidence for interaction claims, including proofs and game definitions, opponent and population sets, self-play protocols, random seeds, compute, uncertainty on strategic outcomes, baselines, and consistency between what the paper
SKILL.md
aamas-reproducibility.SKILL.mdname: aamas-reproducibility
description: Use when strengthening AAMAS reproducibility evidence for interaction claims, including proofs and game definitions, opponent and population sets, self-play protocols, random seeds, compute, uncertainty on strategic outcomes, baselines, and consistency between what the paper claims about agents and what the artifact can actually show.
AAMAS Reproducibility
Use this before submission and again before camera-ready. The reproducibility question at AAMAS is not only "can I rerun the model" but "can I reproduce the *interaction* - the same agents, the same game, the same emergent outcome."
Evidence map
- Map each theorem, mechanism property, convergence claim, and empirical interaction claim to a
verifiable location in the paper, appendix, supplement, or artifact.
- For theory, state the game, the information structure, the solution concept, assumptions,
proof dependencies, and failure modes clearly enough for a game theorist.
- For experiments, report the environment, number of agents, opponent/population set, training
regime, evaluation opponents, metrics, hyperparameter ranges, chosen settings, seeds, repeated runs, compute, and runtime.
- For small or noisy strategic differences, add uncertainty: standard errors, confidence
intervals, or paired tests over seeds and over opponents.
- Explain any missing code or environment honestly, and describe how a reader could reproduce
the interaction in principle.
- Keep the artifact consistent with the paper; a claim the artifact cannot demonstrate is a
review-risk multiplier.
Claim-to-evidence audit table
| Claim | Pure-theory answer | Learning-plus-game answer | |---|---|---| | Solution concept reached | Proof with the game and information structure stated | Plus convergence curves under other agents' adaptation | | Opponents / population | NA if fully analytical | The exact opponent set and how it was chosen | | Seeds and variance | NA for deterministic results | Required for every stochastic curve and payoff table | | Compute | NA | Hardware, per-run time, and total number of self-play runs |
Claiming an equilibrium result while the evaluation only shows two fixed agents playing once is the recognizable AAMAS gap: reviewers read the mismatch between the strategic claim and the thinness of the interaction evidence as carelessness about the rest.
Vignette: a MARL-plus-convergence paper
Consider a submission proving convergence to a coarse-correlated equilibrium in a repeated game, validated by self-play. Its reproducibility spine: the game generator and payoff scale, the learning rule and its step sizes, the opponent set, the replication seeds, the convergence metric, and one honest sentence on the regime where convergence is only empirical, not proved.
Degrees of reproducibility
- Turnkey: one command reruns the game and regenerates each convergence figure from logged
seeds.
- Scripted: scripts exist but require documented manual steps or an external environment.
- Descriptive: prose detailed enough that a competent reader could rebuild the game and agents.
For AAMAS, the strategic core should be turnkey because reviewers actually re-run small games; large real-world or human-in-the-loop pipelines may stay scripted with deviations documented. Stating the achieved level honestly beats overpromising turnkey behavior that fails on a clean machine.
Output format
[Claim inventory] <claim -> evidence location>
[Artifact consistency] complete / inconsistent / missing
[Interaction reproducibility gaps] <game/opponents/seeds/uncertainty/compute>
[Paper fixes] <must appear in main PDF>
[Supplement fixes] <appendix or artifact additions>
Read more
name: aamas-reproducibility description: Use when strengthening AAMAS reproducibility evidence for interaction claims, including proofs and game definitions, opponent and population sets, self-play protocols, random seeds, compute, uncertainty on strategic outcomes, baselines, and consistency between what the paper claims about agents and what the artifact can actually show.
AAMAS Reproducibility
Use this before submission and again before camera-ready. The reproducibility question at AAMAS is not only "can I rerun the model" but "can I reproduce the *interaction* - the same agents, the same game, the same emergent outcome."
Evidence map
- Map each theorem, mechanism property, convergence claim, and empirical interaction claim to a
verifiable location in the paper, appendix, supplement, or artifact.
- For theory, state the game, the information structure, the solution concept, assumptions,
proof dependencies, and failure modes clearly enough for a game theorist.
- For experiments, report the environment, number of agents, opponent/population set, training
regime, evaluation opponents, metrics, hyperparameter ranges, chosen settings, seeds, repeated runs, compute, and runtime.
- For small or noisy strategic differences, add uncertainty: standard errors, confidence
intervals, or paired tests over seeds and over opponents.
- Explain any missing code or environment honestly, and describe how a reader could reproduce
the interaction in principle.
- Keep the artifact consistent with the paper; a claim the artifact cannot demonstrate is a
review-risk multiplier.
Claim-to-evidence audit table
| Claim | Pure-theory answer | Learning-plus-game answer | |---|---|---| | Solution concept reached | Proof with the game and information structure stated | Plus convergence curves under other agents' adaptation | | Opponents / population | NA if fully analytical | The exact opponent set and how it was chosen | | Seeds and variance | NA for deterministic results | Required for every stochastic curve and payoff table | | Compute | NA | Hardware, per-run time, and total number of self-play runs |
Claiming an equilibrium result while the evaluation only shows two fixed agents playing once is the recognizable AAMAS gap: reviewers read the mismatch between the strategic claim and the thinness of the interaction evidence as carelessness about the rest.
Vignette: a MARL-plus-convergence paper
Consider a submission proving convergence to a coarse-correlated equilibrium in a repeated game, validated by self-play. Its reproducibility spine: the game generator and payoff scale, the learning rule and its step sizes, the opponent set, the replication seeds, the convergence metric, and one honest sentence on the regime where convergence is only empirical, not proved.
Degrees of reproducibility
- Turnkey: one command reruns the game and regenerates each convergence figure from logged
seeds.
- Scripted: scripts exist but require documented manual steps or an external environment.
- Descriptive: prose detailed enough that a competent reader could rebuild the game and agents.
For AAMAS, the strategic core should be turnkey because reviewers actually re-run small games; large real-world or human-in-the-loop pipelines may stay scripted with deviations documented. Stating the achieved level honestly beats overpromising turnkey behavior that fails on a clean machine.
Output format
[Claim inventory] <claim -> evidence location> [Artifact consistency] complete / inconsistent / missing [Interaction reproducibility gaps] <game/opponents/seeds/uncertainty/compute> [Paper fixes] <must appear in main PDF> [Supplement fixes] <appendix or artifact additions>
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

