
peer-review
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
- Installs
- 240
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/poemswe/co-researcher --skill peer-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads peer-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
1. Dimensional Evaluation
- Significance/Novelty: Does it move the needle?
- Methodological Soundness: Is the design appropriate and flawlessly executed?
- Presentation/Clarity: Is the narrative arc cohesive and the data visualization professional?
- Ethical Compliance: Are there concerns with sampling, COIs, or data reporting?
2. Structural Critique
- Abstract/Introduction: Clear problem statement and stated contribution.
- Results/Discussion: Correct interpretation and grounding in existing literature.
- References: Identification of missing seminal works or over-citation of self.
3. Decision Logic
- Accept: Rare, minor formatting only.
- Major/Minor Revision: Path to publication exists.
- Reject: Fatal flaws in methodology or lack of original contribution.
<source_resolution>
Verify references and survey the field through the database backends owned by the literature-review skill, not web search alone: uv run <literature-review-dir>/scripts/openalex_cli.py (resolve DOIs/titles, citation counts, related work), europepmc_api.py (life-science full text and citation graphs), search_arxiv.py (preprints), read_paper.py (full text for any DOI/arXiv/PMCID — use it to read a cited paper before asserting it was mischaracterized). Prerequisite uv: see the literature-review skill's <search_backend> section for setup and invocation details.
</source_resolution>
<output_format>
Peer Review Report: [Title/Subject]
Recommendation: [Accept/Minor Rev/Major Rev/Reject]
Executive Summary: [2-3 sentences on core contribution and primary concern]
Dimensional Scores (1-5):
- Novelty: [S] | Rigor: [S] | Impact: [S] | Clarity: [S]
Detailed Comments:
- Major Points:
- [Point] | [Evidence] | [Actionable Change]
- Minor Points:
- [Formatting, Citations, Typos]
Final Verdict Justification: [Detailed PhD-level reasoning for the recommendation] </output_format>
<checkpoint> After the review, ask: - Should I check for specific "Seminal Works" that might have been missed? - Would you like me to refine the "Response to Reviewers" strategy? - Should I analyze the manuscript's fit for a specific target journal (e.g., CVPR, Nature, NEJM)? </checkpoint>FAQ
What does the peer-review skill do?
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
How do I install peer-review?
Run npx skills add https://github.com/poemswe/co-researcher --skill peer-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/peer-review/ (personal) or .claude/skills/peer-review/ (project).
Which AI agents can use peer-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is peer-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains peer-review?
It is published by poemswe in poemswe/co-researcher. It has 240 recorded installs.
More from poemswe/co-researcher
academic-writing
poemswe/co-researcher
You must use this when producing any research prose — literature reviews, syntheses, analyses, methodology descriptions, discussion sections, abstracts, or any written output intended for an academic audience.
quantitative-analysis
poemswe/co-researcher
Open the skill to read its SKILL.md instructions.
qualitative-research
poemswe/co-researcher
You must use this when designing qualitative studies, developing coding schemes, or performing thematic analysis.
research-methodology
poemswe/co-researcher
You must use this when matching research questions to appropriate designs, sampling strategies, or validity controls — or when a research problem is stuck and needs creative reframing (cross-domain analogies, first-principles deconstruction).
systematic-review
poemswe/co-researcher
You must use this when conducting PRISMA-standard systematic reviews, protocol development, or Risk of Bias assessment.
literature-review
poemswe/co-researcher
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.