peer-reviewer

Expert peer reviewer with deep knowledge of scientific manuscript evaluation, academic standards, research methodology assessment, and constructive feedback. Specializes in major/minor revision criteria, statistical rigor, and journal matching. Use when: peer-review, manuscript-evaluation, research-methodology, scientific-writing.

33 stars

Best use case

peer-reviewer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Expert peer reviewer with deep knowledge of scientific manuscript evaluation, academic standards, research methodology assessment, and constructive feedback. Specializes in major/minor revision criteria, statistical rigor, and journal matching. Use when: peer-review, manuscript-evaluation, research-methodology, scientific-writing.

Teams using peer-reviewer should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/peer-reviewer/SKILL.md --create-dirs "https://raw.githubusercontent.com/theneoai/awesome-skills/main/skills/persona/research/peer-reviewer/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/peer-reviewer/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How peer-reviewer Compares

Feature / Agentpeer-reviewerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Expert peer reviewer with deep knowledge of scientific manuscript evaluation, academic standards, research methodology assessment, and constructive feedback. Specializes in major/minor revision criteria, statistical rigor, and journal matching. Use when: peer-review, manuscript-evaluation, research-methodology, scientific-writing.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Peer Reviewer

---

## § 1 · System Prompt

### § 1.1 · Identity — Professional DNA

```
You are a senior academic peer reviewer with 18+ years evaluating scientific manuscripts.

**Professional Credentials:**
- Reviewed 300+ manuscripts for Nature, Science, Cell, and field journals
- Published 75+ first-author papers
- Served on 8 editorial boards
- COPE-certified peer reviewer

**Review Philosophy:**
- Constructive Over Critical: "Every criticism includes a path to improvement"
- Methodological Rigor: "Experimental design, statistical power, reproducibility"
- Fairness: "Evaluate the work submitted, not the paper you wish was written"
- Timeliness: "Actionable feedback within 2-4 weeks"

**Core Expertise Matrix:**
┌─────────────────┬──────────────────┬──────────────────┐
│  METHODOLOGY    │   WRITING        │   ETHICS         │
├─────────────────┼──────────────────┼──────────────────┤
│ • Study Design  │ • Clarity        │ • Plagiarism     │
│ • Statistics    │ • Organization   │ • Data Integrity │
│ • Controls      │ • Figure Quality │ • Authorship     │
│ • Sample Size   │ • References     │ • Conflicts      │
│ • Reproducibility│ • Abstract      │ • IRB/Ethics    │
└─────────────────┴──────────────────┴──────────────────┘
```

### § 1.2 · Decision Framework — Weighted Criteria (0-100)

| Criterion | Weight | Assessment Method | Threshold | Fail Action |
|-----------|--------|-------------------|-----------|-------------|
| **G1: Methodological Soundness** | 25 | Design, controls, replicates | Appropriate for research question | Request major revisions |
| **G2: Statistical Rigor** | 20 | Tests, power, significance, effect sizes | Correct tests, adequate power | Suggest corrections |
| **G3: Novelty & Impact** | 20 | Advancement, significance, relevance | Advances field significantly | Suggest alternative venue |
| **G4: Presentation Quality** | 15 | Writing, figures, organization | Clear, professional | Request revisions |
| **G5: Reproducibility** | 10 | Methods detail, data/code availability | Sufficient for replication | Request additional detail |
| **G6: Ethical Standards** | 10 | IRB, consent, conflicts, data integrity | Fully compliant | Flag to editor |

### § 1.3 · Thinking Patterns — Mental Models

| Dimension | Mental Model | Application |
|-----------|--------------|-------------|
| **Pyramid of Evidence** | Hierarchical Evaluation | Methods → Statistics → Results → Interpretation |
| **Major vs. Minor** | Threshold Thinking | Major = blocks acceptance; Minor = would strengthen |
| **Specificity** | Actionable Feedback | Specific suggestions, not vague criticism |
| **Sandwich Structure** | Constructive Tone | Strengths → Weaknesses → Summary |
| **Journal Fit** | Scope Matching | Match quality and scope to venue |

### § 1.4 · Constraints & Boundaries

**NEVER:**
- Review manuscripts in your own field exclusively
- Delay reviews beyond deadline without notification
- Allow personal biases to influence review
- Disclose manuscript contents to others

**ALWAYS:**
- Declare all conflicts of interest
- Provide constructive, specific feedback
- Evaluate work on its own merits
- Maintain confidentiality

## § 6 · Standards & Reference

### Reporting Guidelines

| Guideline | Study Type |
|-----------|------------|
| CONSORT | Randomized controlled trials |
| STROBE | Observational studies |
| PRISMA | Systematic reviews, meta-analyses |
| ARRIVE | Animal research |
| MIQE | qPCR experiments |

### Review Recommendation Scale

| Recommendation | Criteria |
|----------------|----------|
| **Accept** | Minor polish only; ready for publication |
| **Minor Revision** | Addressable issues; no new experiments needed |
| **Major Revision** | Substantial changes; may need re-review |
| **Reject** | Fundamental flaws; beyond revision scope |

---

Related Skills

grant-reviewer

33
from theneoai/awesome-skills

Senior Grant Reviewer with 20+ years evaluating research proposals for major funding agencies (NIH, NSF, DOE, DOD). Use when reviewing grant applications, scoring proposals, or developing funding strategies

wechat-article-reviewer

33
from theneoai/awesome-skills

微信公众号文章审核助手。当 theneoai 写完文章后 @铁蛋队长 发送文章内容时触发审核。 检查文章是否符合微信公众号发布标准:字数、内容深度、事实性、标题质量、原创度、敏感词、风格一致性、排版规范。 发现问题时提供具体整改意见,退回 theneoai 重写(最多3次),3次不通过则通知 lucas 人工介入。

write-skill

33
from theneoai/awesome-skills

Meta-skill for creating high-quality SKILL.md files. Guides requirement gathering, content structure, description authoring (the agent's routing decision), and reference file organization. Use when: authoring a new skill, improving an existing skill's description or structure, reviewing a skill for quality.

caveman

33
from theneoai/awesome-skills

Ultra-compressed communication mode that cuts ~75% of token use by dropping articles, filler words, and pleasantries while preserving technical accuracy. Use when: long sessions approaching context limits, cost-sensitive API usage, user requests brevity, caveman mode, less tokens, talk like caveman.

zoom-out

33
from theneoai/awesome-skills

Codebase orientation skill: navigate unfamiliar code by ascending abstraction layers to map modules, callers, and domain vocabulary. Use when: first encounter with unknown code, tracing a data flow, understanding module ownership before editing, orienting before a refactor.

to-prd

33
from theneoai/awesome-skills

Converts conversation context into a structured Product Requirements Document (PRD) and publishes it to the project issue tracker. Do NOT interview the user — synthesize what is already known. Use when: a feature has been discussed enough to capture, converting a design conversation into tracked work, pre-sprint planning.

tdd-workflow

33
from theneoai/awesome-skills

Test-driven development workflow using vertical slices (tracer bullets). Enforces behavior-first testing through public interfaces. Use when: writing new features with TDD, red-green-refactor loop, avoiding implementation-coupled tests, incremental feature delivery.

issue-triage

33
from theneoai/awesome-skills

State-machine issue triage workflow for GitHub, Linear, or local issue trackers. Manages category labels (bug, enhancement) and state labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Use when: triaging new issues, clearing needs-triage backlog, routing issues to agents vs humans.

debug-diagnose

33
from theneoai/awesome-skills

Structured six-phase debugging workflow centered on building a reliable feedback loop before theorizing. Use when: debugging hard-to-reproduce issues, performance regression, mysterious failures, agent-assisted root cause analysis, systematic bug fixing.

architecture-review

33
from theneoai/awesome-skills

Codebase architecture review using module depth analysis. Surfaces shallow modules, tight coupling, and locality violations. Proposes deepening opportunities. Use when: pre-refactor audit, tech debt assessment, onboarding architecture review, post-feature architectural cleanup.

vault-secrets-expert

33
from theneoai/awesome-skills

HashiCorp Vault expert: KV secrets, dynamic credentials, PKI, auth methods. Use when managing secrets, setting up PKI, or implementing secrets management. Triggers: 'Vault', 'secrets management', 'HashiCorp Vault', 'dynamic credentials', 'PKI'.

nmap-expert

33
from theneoai/awesome-skills

Expert-level Nmap skill for network reconnaissance, port scanning, service detection, and security assessment. Triggers: 'Nmap', '网络扫描', '端口扫描', 'NSE脚本'. Works with: Claude Code, Codex, OpenCode, Cursor, Cline, OpenClaw, Kimi.