/aamas-review-process
Use when explaining or planning around AAMAS peer review, covering OpenReview review release, the double-blind rebuttal on preliminary reviews, area-chair discussion, the mixed game-theory, MARL, and systems reviewer pool, the public posting of reviews and decisions, and how
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aamas-review-process --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-review-process
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when explaining or planning around AAMAS peer review, covering OpenReview review release, the double-blind rebuttal on preliminary reviews, area-chair discussion, the mixed game-theory, MARL, and systems reviewer pool, the public posting of reviews and decisions, and how
SKILL.md
aamas-review-process.SKILL.mdname: aamas-review-process
description: Use when explaining or planning around AAMAS peer review, covering OpenReview review release, the double-blind rebuttal on preliminary reviews, area-chair discussion, the mixed game-theory, MARL, and systems reviewer pool, the public posting of reviews and decisions, and how acceptance criteria weigh the interaction contribution.
AAMAS Review Process
Use this to reason about review-stage strategy. Reopen the current CFP, OpenReview group, author and reviewer instructions, and the code of conduct before making process claims; AAMAS review specifics move between editions.
Process model
- AAMAS runs submission and review on OpenReview under the IFAAMAS namespace in recent cycles.
- Reviewers evaluate technical correctness, the significance of the interaction contribution,
the reality and rigor of the multiagent evaluation, clarity, reproducibility, and fit with agents-and-multiagent-systems scope.
- A rebuttal lets authors respond to preliminary reviews before the final decision; area chairs
then synthesize.
- Accepted papers and their reviews are published, so the review record is durable and public.
- The most useful rebuttal gives the area chair a clean rationale for acceptance, not a
point-by-point defense of every comment.
Who reviews here
- The pool mixes game theorists, multiagent-RL researchers, mechanism-design and social-choice
specialists, and systems-minded reviewers; expect at least one to read the game definition and solution concept line by line.
- Because AAMAS is specialized, a paper is likely to meet a reviewer who works on exactly its
subarea, so a vague equilibrium claim or an under-specified opponent set gets caught rather than skimmed.
- Borderline interaction papers usually fail on one of three edges: the result turns out to be
single-agent in disguise, the solution concept is never pinned down, or the multiagent evaluation is thin (self-play only, no seeds, no held-out opponents).
Scoring leverage table
| Review dimension | What raises it | What sinks it | |---|---|---| | Correctness | A stated game, a named solution concept, and a body-level proof sketch | Hidden information structure; an equilibrium asserted but never defined | | Significance | A finding that only exists because agents interact | An incremental single-agent gain wearing a multiagent label | | Empirical support | Experiments that probe strategy: held-out opponents, deviation tests | Self-play-only curves disconnected from the claim | | Clarity | One notation source and a legible game description | Notation and payoff conventions that shift between sections |
Stage-by-stage realism
- Initial reviews: triage by what the area chair would weigh, not by reviewer tone.
- Rebuttal: windows are short; an early, precise reply anchored in submitted evidence beats a
late exhaustive one.
- Decision: the area chair synthesizes, and one unanswered correctness or interaction-reality
objection outweighs several resolved clarity complaints.
- Public record: assume the reviews and your rebuttal will be visible with the paper, and keep
the exchange professional and concrete.
Output format
[Current stage] submitted / reviews / rebuttal / decision / camera-ready
[Decision actors] <reviewers / area chair / program chairs>
[Likely leverage] <correctness / interaction-reality / significance / experiments / clarity>
[Forbidden moves] <identity leak / new results / revised-paper upload if disallowed>
[Next response move] <one action>
Read more
name: aamas-review-process description: Use when explaining or planning around AAMAS peer review, covering OpenReview review release, the double-blind rebuttal on preliminary reviews, area-chair discussion, the mixed game-theory, MARL, and systems reviewer pool, the public posting of reviews and decisions, and how acceptance criteria weigh the interaction contribution.
AAMAS Review Process
Use this to reason about review-stage strategy. Reopen the current CFP, OpenReview group, author and reviewer instructions, and the code of conduct before making process claims; AAMAS review specifics move between editions.
Process model
- AAMAS runs submission and review on OpenReview under the IFAAMAS namespace in recent cycles.
- Reviewers evaluate technical correctness, the significance of the interaction contribution,
the reality and rigor of the multiagent evaluation, clarity, reproducibility, and fit with agents-and-multiagent-systems scope.
- A rebuttal lets authors respond to preliminary reviews before the final decision; area chairs
then synthesize.
- Accepted papers and their reviews are published, so the review record is durable and public.
- The most useful rebuttal gives the area chair a clean rationale for acceptance, not a
point-by-point defense of every comment.
Who reviews here
- The pool mixes game theorists, multiagent-RL researchers, mechanism-design and social-choice
specialists, and systems-minded reviewers; expect at least one to read the game definition and solution concept line by line.
- Because AAMAS is specialized, a paper is likely to meet a reviewer who works on exactly its
subarea, so a vague equilibrium claim or an under-specified opponent set gets caught rather than skimmed.
- Borderline interaction papers usually fail on one of three edges: the result turns out to be
single-agent in disguise, the solution concept is never pinned down, or the multiagent evaluation is thin (self-play only, no seeds, no held-out opponents).
Scoring leverage table
| Review dimension | What raises it | What sinks it | |---|---|---| | Correctness | A stated game, a named solution concept, and a body-level proof sketch | Hidden information structure; an equilibrium asserted but never defined | | Significance | A finding that only exists because agents interact | An incremental single-agent gain wearing a multiagent label | | Empirical support | Experiments that probe strategy: held-out opponents, deviation tests | Self-play-only curves disconnected from the claim | | Clarity | One notation source and a legible game description | Notation and payoff conventions that shift between sections |
Stage-by-stage realism
- Initial reviews: triage by what the area chair would weigh, not by reviewer tone.
- Rebuttal: windows are short; an early, precise reply anchored in submitted evidence beats a
late exhaustive one.
- Decision: the area chair synthesizes, and one unanswered correctness or interaction-reality
objection outweighs several resolved clarity complaints.
- Public record: assume the reviews and your rebuttal will be visible with the paper, and keep
the exchange professional and concrete.
Output format
[Current stage] submitted / reviews / rebuttal / decision / camera-ready [Decision actors] <reviewers / area chair / program chairs> [Likely leverage] <correctness / interaction-reality / significance / experiments / clarity> [Forbidden moves] <identity leak / new results / revised-paper upload if disallowed> [Next response move] <one action>
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

