Skip to content
FunCoding

Search

Search docs, Skills and MCP

aaai-review-process

Use when explaining or planning around AAAI's two-phase review process, Phase 1 rejection risk, Phase 2 additional reviews, AI-assisted review pilot, author feedback, SPC/AC discussion, and final decisions.

文档与办公1.2kAAAI-Skills/skills/aaai-review-process/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/brycewang-stanford/awesome-journal-skills/aaai-review-process/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

AAAI Review Process

Use this to plan around AAAI review rather than treating it as a generic OpenReview rebuttal. Reopen the current review-process page and author FAQ before advising on timing or strategy.

Process model

  • AAAI main technical track uses double-blind reviewing.
  • AAAI-27 uses a two-phase review process. Phase 1 allocates three reviewers — two human reviews supplemented by one non-decisional AI-generated review. Papers with sufficiently negative reviews are rejected before author feedback (AAAI-27: notified 2026-09-24).
  • Papers continuing to Phase 2 receive additional reviews, up to five in total, and one author feedback phase (AAAI-27: 2026-10-19 to 10-25, final decisions 2026-11-30). Phase 2 reviewers are not shown the Phase 1 reviews until they have submitted their own — so a Phase 2 review is an independent read, not a reaction to the earlier ones.
  • Final decisions were made through reviewer discussion and senior program committee oversight, not by the AI review.
  • Author feedback is short and constrained; it is mainly for correcting misunderstandings, not replacing the paper.

Author strategy

  • Reduce Phase 1 reject risk before submission by making contribution, evidence, and checklist compliance obvious.
  • When reviews arrive, distinguish human-review claims, AI-review errors, and AC/SPC decision questions.
  • Use rebuttal to resolve the highest-impact factual issue under the character limit.
  • Do not attack the AI review. Correct it when it contains consequential false statements.
  • Avoid new experiments in rebuttal; use submitted evidence and camera-ready promises sparingly.

Stage-by-stage decision map

AAAI's pipeline differs from a single-round OpenReview venue, so plan actions per stage rather than treating every signal as a rebuttal opportunity.

StageWhat is happeningAuthor leverage
Pre-submissionPhase-1 bar is set by clarity and checklistmaximal: fix the paper itself
Phase 1human reviews plus advisory AI reviewnone yet; summary reject possible
Phase 2additional reviews, one feedback roundone short response, no new results
Discussionreviewers and SPC/AC weigh feedbackindirect: a clean correction can swing it
DecisionSPC/AC oversight, not the AI reviewarchive everything for appeal or journal

Why papers die in Phase 1

Because the reviewer pool is large and submission volume is high, clearly-below-bar papers are cut early to protect later effort. Common triggers: an unreadable first page, a contribution a non-specialist cannot place, a checklist that contradicts the paper, or evidence too thin to trust. None of these can be repaired after the Phase-1 cut, so they must be eliminated before submission.

Worked vignette

An NLP paper with strong results buries its contribution under three pages of setup. A Phase-1 reviewer from a planning background cannot find the AI claim and scores it a reject; the paper never reaches feedback. The fix belongs entirely pre-submission: a first-page contribution statement and a checklist that matches the experiments, so the broad-AI reviewer can place and trust it fast.

Output format

[Stage] pre-submission / Phase 1 / Phase 2 / rebuttal / discussion / decision
[Decision risk] summary reject / borderline / likely accept / ethics-policy risk
[Best action] revise before submission / rebut / clarify evidence / escalate
[AI-review handling] ignore / correct / cite submitted evidence
[Rationale] <why this fits AAAI process>

Similar Skills

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Docs & office

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

Docs & office

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Docs & office

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Docs & office

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

Docs & office

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Docs & office