Skip to content
cccskills
FreePublished on GitHub

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 references, and the wording stays double-blind.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 patternAAMAS-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>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 before SPC/AC discussion.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 final public artifact release.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 reproducibility-checklist alignment for Phase-1 survival.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 related-work section legible to non-specialist reviewers.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

See all skills by brycewang-stanford

Report a problem with this skill