Skip to content
Content
Skill

/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

From plugin
awesome-journal-skills
965200 skills
Install
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-author-response --agent claude-code

How 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-author-response

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

aamas-author-response.SKILL.md
name: aamas-author-response
description: 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.

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 wording fix only if it adds no unsupported new claim.

Multi-reviewer pushback patterns

AAMAS pools game theorists, MARL researchers, and systems-minded reviewers on one paper, so a single rebuttal often answers three different lenses at once.

| Pushback | What it signals | AAMAS-ready fix | |---|---|---| | "This is really a single-agent method" | The interaction claim did not land | Point to where the result depends on other agents co-adapting; cite the ablation that freezes them | | "Which equilibrium do you converge to?" | A game theorist read the solution concept | Name it (Nash / correlated / coarse / no-regret) and cite the proof or convergence plot | | "Baselines are self-play only" | Opponent set looks weak | Anchor to the held-out opponents or population in the appendix, or concede a camera-ready addition | | "Seeds and variance are missing" | An empirical reviewer checked rigor | Reference the seeded runs and standard errors; do not promise new experiments as fact |

Response micro-example

Reviewer objection: the cooperation result may be an artifact of a single random seed. Reply skeleton:

1. Note that Figure 3 already aggregates 30 seeds with standard errors. 2. Quote the exact aggregate so the reviewer need not re-open the PDF. 3. Point to Appendix C for the per-seed spread and the opponent set used. 4. Offer one camera-ready sentence stating the seed count in the caption.

Discussion-window calibration

  • One decision-critical point per reviewer beats an exhaustive reply; the area chair reads for

whether the central interaction or correctness objection was actually resolved.

  • Never paste a fresh proof or a new game variant into the response box; sketch the argument

and anchor it in submitted material.

  • Reply early - AAMAS rebuttal windows are short and reviewers who engage once rarely return.
  • Remember the reviews and your response may become public with the paper; write as if they

will.

Output format

[Priority issue] <reviewer concern>
[Decision dimension] correctness / interaction-reality / significance / reproducibility / scope
[Draft response] <AAMAS-ready anonymous text>
[Evidence anchor] <section/appendix/figure/theorem>
[Forbidden content removed] <identity leaks, new results, revised-paper promises>
Read more
Ships withawesome-journal-skills

Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证

Get the whole plugin
Stats
965
Stars
121
Forks
Active
Maintenance
Stata
Language
MIT
License
13h ago
Last commit
2mo ago
Created

Repo: brycewang-stanford/Awesome-Journal-Skills

Other skills on awesome-journal-skills.