paper-reviewer-simulator
Paper Reviewer Simulator
Run a pre-submission shadow review from the perspective of target-conference reviewers. The goal is to find the objections reviewers are likely to raise before the paper is submitted, then turn those objections into concrete revision priorities.
Use this skill for:
- reviewer-style paper critique
- venue-specific predicted scores and confidence
- likely reject reasons and reviewer questions
- adversarial "Reviewer 2" stress tests
- area-chair or meta-review summaries
- rebuttal-readiness checks
- risk register creation for a paper under revision
- learning from example reviews, OpenReview discussions, and target-venue guidelines
Do not use this skill to rewrite the paper directly. Pair it with conference-writing-adapter after the review if the paper needs structural or paragraph-level changes. Pair it with citation-audit for reference correctness and submit-paper for final submission hygiene.
Pair this skill with research-project-memory when simulated reviewer risks should become project-level risks and actions.
More from a-green-hand-jack/ml-research-skills
project-init
Initialize an ML research project control root. Use for paper/code/slides repos, shared memory, GitHub Project alignment, agent guidance, worktree policy, and lifecycle handoffs.
39init-python-project
Initialize or enhance a Python/ML project. Use for new repos or forks needing production structure, uv environment setup, and research evidence docs.
37new-workspace
Create Git branches or worktrees for research code and paper versions. Use for experiments, baselines, rebuttal fixes, arXiv/camera-ready branches, and worktree memory.
36project-sync
Sync verified code-side experiment results into paper memory. Use when logs, reports, run docs, or user-confirmed metrics should become paper-facing evidence.
36init-latex-project
Initialize a LaTeX academic paper project. Use for new conference or journal papers needing templates, macros, venue preambles, and writing guidance.
36add-git-tag
Create annotated Git milestone tags. Use when completing a phase, releasing a version, or marking a research checkpoint.
36