Skip to content
cccskills
FreePublished on GitHub

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 acceptance criteria weigh the interaction contribution.

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

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 dimensionWhat raises itWhat sinks it
CorrectnessA stated game, a named solution concept, and a body-level proof sketchHidden information structure; an equilibrium asserted but never defined
SignificanceA finding that only exists because agents interactAn incremental single-agent gain wearing a multiagent label
Empirical supportExperiments that probe strategy: held-out opponents, deviation testsSelf-play-only curves disconnected from the claim
ClarityOne notation source and a legible game descriptionNotation 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>

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