aamas-author-response
Use when drafting an AAMAS rebuttal to preliminary OpenReview reviews, covering the double-blind constraint, the no-new-results and no-revised-paper norms, how to answer game-theory, MARL, and systems reviewers at once, and how to give the area chair a clean acceptance rationale within a short response window.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-author-response --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AAMAS Author Response Use this after AAMAS preliminary reviews are released. Reopen the current OpenReview instructions and the rebuttal-window rules before drafting; response mechanics are cycle-specific and AAMAS reviews and decisions become public afterward. ## Triage - Answer only what can move the decision: correctness of the game model or proofs, the reality of the interaction claim, baseline/opponent fairness, reproducibility, and scope. - Use evidence already in the submission: sections, appendices, the supplement, theorem statements, learning curves, and opponent-set definitions. AAMAS rebuttals do not add new results and typically do not upload a revised paper. - Keep the reply anonymous: no institution, no named system, no private URLs or repository owners. - Correct outright factual errors first, then address requests for missing comparisons, ablations, equilibrium analysis, or seeds. ## Drafting pattern 1. State the decision-critical correction or concession in the first line. 2. Point to the exact submitted evidence (section, figure, appendix, or theorem number). 3. Explain the strategic or empirical consequence for the reviewer's concern. 4. Promise a camera-ready
- Triage
- Drafting pattern
- Multi-reviewer pushback patterns
- Response micro-example
- Discussion-window calibration
- Output format
What does the aamas-author-response skill do?
Use when drafting an AAMAS rebuttal to preliminary OpenReview reviews, covering the double-blind constraint, the no-new-results and no-revised-paper norms, how to answer game-theory, MARL, and systems reviewers at once, and how to give the area chair a clean acceptance rationale within a short response window.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-author-response --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.