This skill should be used when the user asks to "review my paper", "give me feedback on my draft", "editorial review", "is my paper ready to submit", "check my paper for issues", or needs structured editorial feedback on a paper draft. Launches a multi-agent review system with 8 specialists (2 literature scouts + 6 domain reviewers) orchestrated by an area chair agent. Produces a unified report in .papermill/reviews/. Updates .papermill/state.md.
From papermillnpx claudepluginhub queelius/claude-anvil --plugin papermillThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Generates FastAPI project templates with async routes, dependency injection, Pydantic schemas, repository patterns, middleware, and config for PostgreSQL/MongoDB backends.
Launch a comprehensive multi-agent review of a research paper. The review system uses 8 specialist agents orchestrated by an area chair to evaluate logic, novelty, methodology, prose, citations, and formatting — grounded in literature context.
Read .papermill/state.md (Read tool) for:
If .papermill/state.md does not exist, the review can still proceed by reading the manuscript directly — but the review will be less targeted without thesis and venue context. Note this limitation to the user and suggest running /papermill:init first for best results.
Locate the manuscript files:
.papermill/state.md for format and any recorded manuscript path.*.tex, *.Rmd, paper.md, manuscript.md.Read the manuscript to confirm it has enough content for review.
Before launching the review, ask the user:
I'll launch a multi-agent review with specialists covering:
- Logic & proofs — mathematical correctness and argument structure
- Novelty — contribution evaluation against the literature
- Methodology — experimental design and statistical rigor
- Prose — writing quality and narrative structure
- Citations — reference accuracy and completeness
- Formatting — build verification and venue compliance
Are there specific areas you want me to focus on, or should I run the full review?
If the user specifies focus areas, note them for the orchestrator. If they want the full review, proceed with all specialists.
Launch the reviewer agent (Task tool with subagent_type: "papermill:reviewer").
Pass the agent:
.papermill/state.md (if it exists)The agent will:
.papermill/reviews/YYYY-MM-DD/After the agent completes, read .papermill/reviews/YYYY-MM-DD/review.md (Read tool).
Present a summary to the user:
Review Complete
Recommendation: [ready | minor-revision | major-revision | not-ready]
Severity Count Critical N Major M Minor P Suggestions Q Top findings:
- [Most important finding]
- [Second most important finding]
- [Third most important finding]
The full report is at
.papermill/reviews/YYYY-MM-DD/review.md. Individual specialist reports are in the same directory.
Then ask: "Would you like to go through the findings in detail, or address the critical issues first?"
Update .papermill/state.md (Edit tool):
Add a review record to review_history:
review_history:
- date: "YYYY-MM-DD"
type: "multi-agent-review"
findings_major: N
findings_minor: M
recommendation: "ready | minor-revision | major-revision | not-ready"
notes: "Brief summary of key findings"
report_path: ".papermill/reviews/YYYY-MM-DD/review.md"
Append a timestamped note to the markdown body.
Based on the recommendation, suggest the most relevant next step:
/papermill:polish to prepare, then /papermill:venue if no venue is selected yet./papermill:review./papermill:outline. If issues are with the argument, suggest /papermill:thesis. Then re-run /papermill:review./papermill:thesis. Insufficient evidence → /papermill:experiment or /papermill:simulation. Missing related work → /papermill:prior-art. Proof gaps → /papermill:proof.