Best for
- Conducting peer review of scientific manuscripts for journals
- Evaluating grant proposals and research applications
- Assessing methodology and experimental design rigor
synthetic-sciences/openscience/backend/cli/skills/research/peer-review/SKILL.md
Systematic peer review toolkit. Evaluate methodology, statistics, design, reproducibility, ethics, figure integrity, reporting standards, for manuscript and grant review across disciplines.
Decision brief
Systematic peer review toolkit. Evaluate methodology, statistics, design, reproducibility, ethics, figure integrity, reporting standards, for manuscript and grant review across disciplines.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/synthetic-sciences/openscience --skill "backend/cli/skills/research/peer-review"Inspect the Agent Skill "peer-review" from https://github.com/synthetic-sciences/openscience/blob/95be136c06386eb18546ce94d134d2c7e66976ac/backend/cli/skills/research/peer-review/SKILL.md at commit 95be136c06386eb18546ce94d134d2c7e66976ac. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Conduct peer review systematically through the following stages, adapting depth and focus based on the manuscript type and discipline.
Begin with a high-level evaluation to determine the manuscript's scope, novelty, and overall quality.
Conduct a thorough evaluation of each manuscript section, documenting specific concerns and strengths.
Evaluate the technical quality and rigor of the research with particular attention to common pitfalls.
Assess whether the research meets modern standards for reproducibility and open science.
Permission review
The documentation asks the agent to run terminal commands or scripts.
python scripts/generate_schematic.py "your diagram description" -o figures/output.pngThe documentation asks the agent to create, modify, or delete local files.
Save outputs in the figures/ directoryThe documentation asks the agent to run terminal commands or scripts.
python skills/scientific-slides/scripts/pdf_to_images.py presentation.pdf review/slide --dpi 150The documentation asks the agent to read local files, directories, or repositories.
Read and inspect EACH slide image file sequentiallyEvidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 90/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 3,338 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Peer review is a systematic process for evaluating scientific manuscripts. Assess methodology, statistics, design, reproducibility, ethics, and reporting standards. Apply this skill for manuscript and grant review across disciplines with constructive, rigorous evaluation.
This skill should be used when:
Related Resource: The venue-templates skill provides reviewer_expectations.md with detailed guidance on what reviewers look for at different venues (Nature/Science, Cell Press, medical journals, ML conferences). Use this to calibrate your review standards to the target venue.
When creating documents with this skill, always consider adding scientific diagrams and schematics to enhance visual communication.
If your document does not already contain schematics or diagrams:
For new documents: Scientific schematics should be generated by default to visually represent key concepts, workflows, architectures, or relationships described in the text.
How to generate schematics:
python scripts/generate_schematic.py "your diagram description" -o figures/output.png
The AI will automatically:
When to add schematics:
For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.
Conduct peer review systematically through the following stages, adapting depth and focus based on the manuscript type and discipline.
Begin with a high-level evaluation to determine the manuscript's scope, novelty, and overall quality.
Key Questions:
Output: Brief summary (2-3 sentences) capturing the manuscript's essence and initial impression.
Conduct a thorough evaluation of each manuscript section, documenting specific concerns and strengths.
Critical elements to verify:
Common issues to identify:
Red flags:
Evaluate the technical quality and rigor of the research with particular attention to common pitfalls.
Statistical Assessment:
Experimental Design:
Computational/Bioinformatics:
Assess whether the research meets modern standards for reproducibility and open science.
Data Availability:
Code and Materials:
Reporting Standards:
references/reporting_standards.md for common guidelinesEvaluate the quality, clarity, and integrity of data visualization.
Quality Checks:
Integrity Checks:
Clarity:
Systematically check presentation details that human reviewers frequently identify.
Table Audit:
| Check | Pass | Fail |
|---|---|---|
| Numeric values | Has actual numbers | Uses "Higher", "Better", "↑" |
| Column headers | Clear, complete | Ambiguous abbreviations |
| Units specified | All units shown | Missing units |
| Significant figures | Appropriate precision | Excessive or insufficient |
| Caption completeness | Self-explanatory | Requires text reference |
Figure Audit:
| Check | Pass | Fail |
|---|---|---|
| Legibility | Readable at 100% zoom | Tiny text, blurry lines |
| Axis labels | Present with units | Missing or unclear |
| Legend placement | Within figure | Overlapping data |
| Resolution | Print quality (300+ dpi) | Pixelated |
| Color scheme | Colorblind-friendly | Red-green only |
Notation Audit:
| Check | Pass | Fail |
|---|---|---|
| Variable definitions | Defined before use | Used without definition |
| Consistency | Same symbol = same meaning | Reused symbols |
| Standard notation | Field conventions | Idiosyncratic choices |
Structure Audit:
| Check | Pass | Fail |
|---|---|---|
| Section redundancy | Each section has unique content | Repeated information |
| Cross-references | Figures/tables referenced in text | Orphan figures |
| Citation completeness | All claims supported | Unsupported assertions |
See references/paper_mechanics.md for detailed checklists and common issues.
Verify that the research meets ethical standards and guidelines.
Human Subjects:
Animal Research:
Research Integrity:
Assess the manuscript's clarity, organization, and accessibility.
Structure and Organization:
Writing Quality:
Accessibility:
Organize feedback in a hierarchical structure that prioritizes issues and provides actionable guidance.
Provide a concise overall assessment (1-2 paragraphs):
List critical issues that significantly impact the manuscript's validity, interpretability, or significance. Number these sequentially for easy reference.
Major comments typically include:
For each major comment:
List less critical issues that would improve clarity, completeness, or presentation. Number these sequentially.
Minor comments typically include:
For each minor comment:
For manuscripts requiring detailed feedback, provide section-specific or line-by-line comments:
List specific questions that need clarification:
Maintain a constructive, professional, and collegial tone throughout the review.
Best Practices:
Avoid:
Maintain calibrated, fair language that distinguishes between reporting issues and scientific misconduct.
| Situation | Use This | NOT This |
|---|---|---|
| Missing details | "needs clearer reporting" | "misleading" |
| Incomplete info | "would benefit from" | "fails to" |
| Scope limitation | "limited to [context]" | "flawed because" |
| Acknowledged limitation | "as authors note..." | (no penalty >1 point) |
| Different interpretation | "alternative explanation" | "contradictory" |
Too Harsh (Avoid):
"The authors misleadingly present their results without adequate baselines, fundamentally undermining the validity of all claims."
Appropriately Calibrated:
"The baseline comparisons could be strengthened. Adding [specific baseline] would help contextualize the reported improvements (see Section 4.2, p. 8)."
Calibrate scores to match human reviewer standards and avoid over-penalization.
If ALL of these conditions are met, the overall score MUST be ≥6:
| Score | Label | Description |
|---|---|---|
| 9-10 | Strong Accept | Significant contribution, excellent execution, high impact |
| 7-8 | Accept | Solid work, minor issues, clear contribution |
| 6 | Weak Accept | Sound methodology, acknowledged limitations, narrow scope acceptable |
| 5 | Borderline | Significant concerns but salvageable with major revisions |
| 3-4 | Reject | Fundamental issues with methodology or validity |
| 1-2 | Strong Reject | Major scientific or ethical concerns |
See references/scoring_rubric.md for detailed scoring criteria and calibration examples.
See references/calibration_guidelines.md for calibration principles based on human reviewer alignment.
⚠️ CRITICAL: For presentations, NEVER read the PDF directly. ALWAYS convert to images first.
When reviewing scientific presentations (PowerPoint, Beamer, slide decks):
NEVER attempt to read presentation PDFs directly - this causes buffer overflow errors and doesn't show visual formatting issues.
Required Process:
python skills/scientific-slides/scripts/pdf_to_images.py presentation.pdf review/slide --dpi 150
# Creates: review/slide-001.jpg, review/slide-002.jpg, etc.
Print when starting review:
[HH:MM:SS] PEER REVIEW: Presentation detected - converting to images for review
[HH:MM:SS] PDF REVIEW: NEVER reading PDF directly - using image-based inspection
Visual Design and Readability:
Layout and Formatting (Check EVERY Slide Image):
Content Quality:
Structure and Flow:
Scientific Content:
Common Presentation Issues to Flag:
Critical Issues (Must Fix):
Major Issues (Should Fix):
Minor Issues (Suggestions for Improvement):
Summary Statement:
Layout and Formatting Issues (By Slide Number):
Slide 3: Text overflow - bullet point 4 extends beyond right margin
Slide 7: Element overlap - figure overlaps with caption text
Slide 12: Font size - axis labels too small to read from distance
Slide 18: Alignment - title not centered
Content and Structure Feedback:
Design and Accessibility:
Timing and Scope:
[14:30:00] PEER REVIEW: Starting review of presentation
[14:30:05] PEER REVIEW: Presentation detected - converting to images
[14:30:10] PDF REVIEW: Running pdf_to_images.py on presentation.pdf
[14:30:15] PDF REVIEW: Converted 25 slides to images in review/ directory
[14:30:20] PDF REVIEW: Inspecting slide 1/25 - title slide
[14:30:25] PDF REVIEW: Inspecting slide 2/25 - introduction
...
[14:35:40] PDF REVIEW: Inspecting slide 25/25 - acknowledgments
[14:35:45] PDF REVIEW: Completed image-based review
[14:35:50] PEER REVIEW: Found 8 layout issues, 3 content issues
[14:35:55] PEER REVIEW: Generating structured feedback by slide number
Remember: For presentations, the visual inspection via images is MANDATORY. Never attempt to read presentation PDFs as text - it will fail and miss all visual formatting issues.
This skill includes reference materials to support comprehensive peer review:
Guidelines for major reporting standards across disciplines (CONSORT, PRISMA, ARRIVE, MIAME, STROBE, etc.) to evaluate completeness of methods and results reporting.
Catalog of frequent methodological and statistical issues encountered in peer review, with guidance on identifying and addressing them.
Detailed scoring rubric with severity calibration, sub-dimension criteria (Soundness, Originality, Clarity, Significance), and score anchoring examples for consistent evaluation.
Human reviewer alignment guidelines based on empirical comparison with actual peer reviews. Contains calibration principles, common over-penalization patterns, and examples of appropriately calibrated feedback.
Comprehensive checklist for paper presentation mechanics (tables, figures, notation, structure) based on issues frequently identified by human reviewers but sometimes missed by automated systems.
Before finalizing the review, verify:
Content Evaluation:
Paper Mechanics (Stage 5b):
Tone Calibration:
Score Calibration:
Frequently asked questions
Systematic peer review toolkit. Evaluate methodology, statistics, design, reproducibility, ethics, figure integrity, reporting standards, for manuscript and grant review across disciplines.
The source record exposes this install command: npx skills add https://github.com/synthetic-sciences/openscience --skill "backend/cli/skills/research/peer-review". Inspect the command and pinned source before running it.
Static rules flagged exec-script, write-files, read-files in the source; the page lists the matching lines and excerpts.
Alternatives
Aperivue/medsci-skills
Peer review assistant for medical journals. Generates structured review drafts with journal-specific formatting. Constructive developmental tone with systematic manuscript analysis.
prowler-cloud/prowler
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
brucesongs/kali-claw
Insecure Design (OWASP A06:2025) focuses on security flaws in system architecture and design phases, rather than code implementation-level bugs.
NintendaDev/unikit-ai
Generate and maintain the project's TECHNICAL documentation from its codebase — scans the project structure, tech stack, and module boundaries, then writes a lean README landing page plus detailed topic pages (architecture, modules, setup, build, APIs), only the docs that are relevant. Use whenever the user wants to create, update, or validate documentation of the CODE or the project itself, e.g. "generate documentation", "create docs", "write the README", "update the project docs", "document th