/aamas-writing-style
Use when revising an AAMAS paper so the interaction contribution leads the first page, the solution concept or incentive property is named, the game and agents are legible, claims are paired with proofs or multiagent experiments, the argument fits eight two-column pages plus
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-writing-style --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-writing-style
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when revising an AAMAS paper so the interaction contribution leads the first page, the solution concept or incentive property is named, the game and agents are legible, claims are paired with proofs or multiagent experiments, the argument fits eight two-column pages plus
SKILL.md
aamas-writing-style.SKILL.mdname: aamas-writing-style
description: Use when revising an AAMAS paper so the interaction contribution leads the first page, the solution concept or incentive property is named, the game and agents are legible, claims are paired with proofs or multiagent experiments, the argument fits eight two-column pages plus references, and the wording stays double-blind.
AAMAS Writing Style
Use this when revising the main paper. AAMAS papers need a compact statement of why an *interaction* result matters and enough detail for a game theorist and an empiricist to both validate it.
Revision rules
- Put the interaction contribution on the first page: the multiagent problem, why single-agent
or centralized fixes fail, the mechanism or learning rule, the strategic property, and the evidence.
- Name the solution concept or incentive property (Nash, correlated, coarse-correlated,
no-regret, dominant-strategy truthful, Pareto); an unnamed "equilibrium" is a review flag.
- Make the game legible: agents, actions, information structure, and payoffs stated once and
clearly.
- Pair every major claim with a proof sketch, a self-play or population experiment, or a
deployment result.
- Use the 8-page body for the core argument and push long proofs, extra opponents, and extended
ablations to the appendix (references are unlimited, so cite generously).
- Keep double-blind wording in self-citations, prior-system references, acknowledgements, and
artifact descriptions.
Interaction-first discipline
- State early why the result is genuinely multiagent - what breaks if the other agents are
frozen into a static environment. If nothing breaks, the AAMAS framing does not hold.
- Give each theorem a body-level proof sketch; the appendix proof supports the sketch but never
replaces it.
- Keep the game's information structure visible; who knows what and when is where multiagent
proofs live or die.
- Separate a *proved* strategic property from an *observed* one; mixing "is truthful" and
"appears cooperative" in one paragraph is a credibility leak here.
Sentence-level rewrites
| Draft pattern | AAMAS-safe rewrite | |---|---| | "Our agents outperform the baselines..." | "reduce social cost by X (SE Y) over Z seeds against held-out opponents" | | "The agents reach equilibrium..." | "converge to a coarse-correlated equilibrium (Def. 2) under Assumptions 1-3" | | "The mechanism is fair and efficient..." | "is dominant-strategy truthful (Thm. 1) with efficiency loss bounded by ... (Thm. 2)" | | "In a multiagent setting..." | Name the game, the number of agents, and the information structure |
Vignette: compressing into eight two-column pages
A draft with two theorems, a mechanism, six figures, and a sprawling related-work section: keep both theorem statements with one sketch each, the mechanism definition, and the two decision-critical figures (truthfulness-under-learning and the efficiency gap); compress related work into precise contrasts; move secondary lemmas and four figures to the appendix with forward references. The test of a good cut: a reviewer reconstructs the whole interaction argument without opening the supplement.
Output format
[Writing diagnosis] clear / interaction-buried / concept-unnamed / overloaded
[First-page fix] <new interaction framing>
[Claim discipline] <claim -> proof / experiment / limitation>
[Compression cuts] <move / delete / merge>
[Anonymity edits] <phrases to rewrite>
Read more
name: aamas-writing-style description: Use when revising an AAMAS paper so the interaction contribution leads the first page, the solution concept or incentive property is named, the game and agents are legible, claims are paired with proofs or multiagent experiments, the argument fits eight two-column pages plus references, and the wording stays double-blind.
AAMAS Writing Style
Use this when revising the main paper. AAMAS papers need a compact statement of why an *interaction* result matters and enough detail for a game theorist and an empiricist to both validate it.
Revision rules
- Put the interaction contribution on the first page: the multiagent problem, why single-agent
or centralized fixes fail, the mechanism or learning rule, the strategic property, and the evidence.
- Name the solution concept or incentive property (Nash, correlated, coarse-correlated,
no-regret, dominant-strategy truthful, Pareto); an unnamed "equilibrium" is a review flag.
- Make the game legible: agents, actions, information structure, and payoffs stated once and
clearly.
- Pair every major claim with a proof sketch, a self-play or population experiment, or a
deployment result.
- Use the 8-page body for the core argument and push long proofs, extra opponents, and extended
ablations to the appendix (references are unlimited, so cite generously).
- Keep double-blind wording in self-citations, prior-system references, acknowledgements, and
artifact descriptions.
Interaction-first discipline
- State early why the result is genuinely multiagent - what breaks if the other agents are
frozen into a static environment. If nothing breaks, the AAMAS framing does not hold.
- Give each theorem a body-level proof sketch; the appendix proof supports the sketch but never
replaces it.
- Keep the game's information structure visible; who knows what and when is where multiagent
proofs live or die.
- Separate a *proved* strategic property from an *observed* one; mixing "is truthful" and
"appears cooperative" in one paragraph is a credibility leak here.
Sentence-level rewrites
| Draft pattern | AAMAS-safe rewrite | |---|---| | "Our agents outperform the baselines..." | "reduce social cost by X (SE Y) over Z seeds against held-out opponents" | | "The agents reach equilibrium..." | "converge to a coarse-correlated equilibrium (Def. 2) under Assumptions 1-3" | | "The mechanism is fair and efficient..." | "is dominant-strategy truthful (Thm. 1) with efficiency loss bounded by ... (Thm. 2)" | | "In a multiagent setting..." | Name the game, the number of agents, and the information structure |
Vignette: compressing into eight two-column pages
A draft with two theorems, a mechanism, six figures, and a sprawling related-work section: keep both theorem statements with one sketch each, the mechanism definition, and the two decision-critical figures (truthfulness-under-learning and the efficiency gap); compress related work into precise contrasts; move secondary lemmas and four figures to the appendix with forward references. The test of a good cut: a reviewer reconstructs the whole interaction argument without opening the supplement.
Output format
[Writing diagnosis] clear / interaction-buried / concept-unnamed / overloaded [First-page fix] <new interaction framing> [Claim discipline] <claim -> proof / experiment / limitation> [Compression cuts] <move / delete / merge> [Anonymity edits] <phrases to rewrite>
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

