SkillAgentSearch skills...

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 word…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-writing-style

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of aamas-writing-style

aamas-writing-style scores 83/100 on our quality scale, 895th of 1,179 Content & Media skills we index.

Its SKILL.md is 3.4 KB long, split into 6 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 aamas-writing-style 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.

aamas-writing-style compared with similar skills

All 4 of these similar skills score higher than aamas-writing-style; compare them before choosing.

SkillScoreStarsUpdatedFormat
aamas-writing-style (this skill)by brycewang-stanford831.2k18d agoSKILL.md
siyuanby siyuan-note10046.6ktodayMCP Server
algorithmic-artby anthropics100177.9k10d agoSKILL.md
pptxby anthropics100177.9k10d agoSKILL.md
designby nextlevelbuilder100130.2k12d agoSKILL.md

Frequently asked questions

How do I install aamas-writing-style?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-writing-style. The install tabs above show the steps for each supported agent.
Which AI agents does aamas-writing-style 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 aamas-writing-style 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 aamas-writing-style still maintained?
The repository was last updated 18 days ago, so aamas-writing-style is actively maintained.

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>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
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