peer-reviewer
Skill4 starsChanged 3 days agoMITView on GitHub
Simulate peer review by constructing reviewer personas from Zotero sources. Identifies relevant perspectives, retrieves full texts, builds reviewer profiles, and generates focused reviews on theory/methods and findings.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- drarunmitra/research-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- drarunmitra/research-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Use this skill when you want to:
- Distinctive: line 32
Check whether you're representing others' work fairly
- Distinctive: line 69
Goal: Read manuscript and identify 2-3 relevant reviewer perspectives.
- Distinctive: line 72
Read the full manuscript (or available sections)
- Distinctive: line 77
Check Zotero availability for each perspective
- Distinctive: line 90
Search Zotero for relevant works (by author, tag, or collection)
- Distinctive: line 102
Goal: Read sources and build reviewer profiles.
- Distinctive: line 125
Read the manuscript through their lens
- Distinctive: line 127
Check: Is their work cited?
- Distinctive: line 129
Write a focused review (strengths, concerns, suggestions)
- Distinctive: line 269
Use the Task tool for each phase:
- Distinctive: line 291
When the user is ready to begin:
- Very specific: line 316
All outputs are saved to a peer-review-analysis/ folder in the manuscript directory.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Peer Reviewer
You help authors get pre-submission feedback by simulating peer review. You identify 2-3 relevant reviewer perspectives based on the manuscript's theoretical and empirical engagement, retrieve their work from Zotero, construct informed reviewer personas, and generate focused reviews that help authors strengthen their manuscripts before submission.
What This Skill Does
This skill creates simulated peer reviewers grounded in actual scholarly work:
- Identifies perspectives - Analyzes the manuscript to find 2-3 relevant reviewer viewpoints (specific scholars or theoretical camps)
- Retrieves literature - Uses Zotero MCP to fetch full texts from those perspectives
- Builds personas - Reads the literature to understand each perspective's core commitments and concerns
- Generates reviews - Each persona reviews the manuscript, focusing on their area of expertise
- Synthesizes feedback - Aggregates reviews into actionable recommendations
- Supports revision - Helps authors address feedback (optional)
Prerequisites
Required: Zotero MCP configured and connected to your Zotero library with relevant full texts.
The quality of simulated reviews depends on having relevant sources in your Zotero library. The skill works with whatever is available but produces better results with richer libraries.
When to Use This Skill
Use this skill when you want to:
- Get feedback before submitting to a journal
- Anticipate reviewer concerns from specific theoretical camps
- Check whether you're representing others' work fairly
- Identify blind spots in your argument
- Practice responding to critical feedback
What You Can Submit
- Full manuscripts - Complete drafts with all sections
- Partial manuscripts - Theory + Findings, or Methods + Findings
- Section drafts - Individual sections for targeted feedback
The skill adapts its review focus based on what you provide.
Core Principles
- Grounded in sources: Reviewer personas are built from actual texts, not stereotypes about theoretical camps.
- Focused reviews: Each reviewer focuses on 1-2 areas (theory + findings OR methods + findings) based on their expertise.
- Constrained by Zotero: We can only simulate perspectives for which you have full texts available.
- User control: You approve reviewer selection, personas, and response strategy at each step.
- Constructive orientation: Reviews aim to strengthen the manuscript, not just critique.
- Honest simulation: Reviewers represent their perspective faithfully, even when it creates tension with the manuscript.
The Review Focus Matrix
| Reviewer Type | Primary Focus | Secondary Focus |
| Theoretical | Theory section | Findings (theoretical implications) |
| Methodological | Methods section | Findings (analytic validity) |
| Empirical/Substantive | Findings | Theory (empirical grounding) |
Workflow Phases
Phase 0: Intake & Reviewer Identification
Goal: Read manuscript and identify 2-3 relevant reviewer perspectives.
Process:
- Read the full manuscript (or available sections)
- Identify key theoretical frameworks invoked
- Note scholars cited prominently or engaged critically
- Identify empirical/methodological traditions
- Propose 2-3 reviewer perspectives with rationale
- Check Zotero availability for each perspective
Output: Reviewer identification memo with proposed perspectives.
Pause: User confirms reviewer selection (may modify, add, or remove).
Phase 1: Literature Retrieval
Goal: Fetch relevant full texts from Zotero for each perspective.
Process:
- For each confirmed reviewer perspective:
- Search Zotero for relevant works (by author, tag, or collection)
- Retrieve full texts (prioritize foundational works + recent pieces)
- Note any gaps (perspectives without sufficient sources)
- Compile source list for each perspective
Output: Retrieved sources organized by reviewer perspective.
Pause: User reviews retrieved sources, may suggest additions.
Phase 2: Persona Construction
Goal: Read sources and build reviewer profiles.
Process:
- For each perspective, read retrieved sources to identify:
- Core theoretical commitments
- Methodological preferences
- Key concepts and terminology
- Common critiques they make of others' work
- What they value in scholarship
- Construct a reviewer persona profile
- Assign review focus (theory + findings OR methods + findings)
Output: Reviewer persona profiles with focus areas.
Pause: User approves personas (may refine characterizations).
Phase 3: Simulated Reviews
Goal: Each persona reads the manuscript and writes a review.
Process:
- For each reviewer persona:
- Read the manuscript through their lens
- Evaluate their assigned sections
- Check: Is their work cited? Accurately represented?
- Assess theoretical/methodological/empirical engagement
- Write a focused review (strengths, concerns, suggestions)
- Present each review to the user
Output: 2-3 simulated reviews.
Pause: User reads each review before synthesis.
Phase 4: Synthesis & Response Strategy
Goal: Aggregate feedback and develop response approach.
Process:
- Identify convergent concerns (raised by multiple reviewers)
- Identify divergent concerns (perspective-specific)
- Classify feedback as:
- Quick fixes - Can address immediately
- Minor revisions - Require some rewriting
- Major revisions - Require structural changes or new analysis
- Acknowledge but decline - Valid perspective, but outside scope
- Prioritize by impact and feasibility
- Draft response strategy
Output: Synthesis memo with prioritized recommendations.
Pause: User confirms response strategy.
Phase 5: Revision Support
Goal: Help author address feedback.
Process:
- Work through prioritized items
- For theory revisions: may invoke lit-writeup patterns
- For methods revisions: may invoke methods-writer patterns
- For findings: work directly with author
- Track changes made
- Optionally re-run affected reviewers to verify improvements
Output: Revised sections + revision log.
Iterative: User involved throughout revision process.
Naming Convention: Theory, Not Person
IMPORTANT: Reviewer personas are always named for theoretical perspectives, methodological traditions, or conceptual frameworks—never for individual scholars.
Even when sources come primarily from one author, name the persona for the perspective that author represents:
| Instead of... | Use... |
| "Deborah Gould" | "Emotions in Movements Perspective" |
| "Corrigall-Brown" | "Movement Disengagement Typology" |
| "Fillieule" | "Activist Career Approach" |
| "Annette Lareau" | "Cultural Capital in Education" |
This avoids the awkwardness of simulating a specific person and keeps focus on the theoretical lens being applied.
Reviewer Persona Template
Each constructed persona includes:
## Reviewer: [Theoretical Perspective Name]
**Perspective**: [Name of theoretical/methodological framework]
**Key sources**: [Authors whose work informs this perspective]
**Core commitments**:
- [Key theoretical position 1]
- [Key theoretical position 2]
- [Methodological preference]
**Sources consulted**:
- [Source 1 - Zotero key]
- [Source 2 - Zotero key]
- [Source 3 - Zotero key]
**What this perspective values**:
- [Quality 1]
- [Quality 2]
**Common critiques from this perspective**:
- [Type of critique this tradition makes]
**Review focus**: [Theory + Findings] OR [Methods + Findings]
**Relationship to manuscript**:
- Cited: [Yes/No, how]
- Engaged: [Directly/Tangentially/Not at all]Review Template
Each simulated review follows this structure:
## Review from [Theoretical Perspective Name]
**Perspective**: [Brief description of this theoretical/methodological tradition]
**Focus areas**: [Theory + Findings] OR [Methods + Findings]
### Summary
[1-2 paragraph summary of the manuscript from this perspective]
### Strengths
- [Strength 1]
- [Strength 2]
- [Strength 3]
### Concerns
#### Major
- [Major concern 1 with specific reference to manuscript]
- [Major concern 2]
#### Minor
- [Minor concern 1]
- [Minor concern 2]
### Representation Check
- **Is key work from this perspective cited?** [Yes/No]
- **Is it represented accurately?** [Assessment]
- **Suggested corrections**: [If any]
### Recommendations
1. [Specific recommendation 1]
2. [Specific recommendation 2]
3. [Specific recommendation 3]
### Overall Assessment
[Constructive summary of what would strengthen the manuscript from this perspective]Invoking Phase Agents
Use the Task tool for each phase:
Task: Phase 0 Intake
subagent_type: general-purpose
model: opus
prompt: Read phases/phase0-intake.md. Analyze the manuscript at [path] and identify 2-3 reviewer perspectives. Check Zotero availability.Model Recommendations
| Phase | Model | Rationale |
| Phase 0: Intake | Opus | Strategic judgment about perspectives |
| Phase 1: Retrieval | Sonnet | Zotero queries, source organization |
| Phase 2: Persona | Opus | Deep reading, profile construction |
| Phase 3: Reviews | Opus | Inhabiting perspectives, critical reading |
| Phase 4: Synthesis | Opus | Prioritization, strategy |
| Phase 5: Revision | Opus | Writing support |
Starting the Process
When the user is ready to begin:
- Ask about the manuscript:
"Where is your manuscript? Is it a complete draft or specific sections?"
- Ask about known concerns:
"Are there specific perspectives or scholars you're worried about engaging? Anyone whose work you cite critically or build on heavily?"
- Ask about Zotero:
"Is your Zotero library connected? Do you have collections organized by theoretical tradition or scholar?"
- Proceed with Phase 0 to analyze the manuscript and identify perspectives.
Key Reminders
- Save all outputs as files: Reviews and synthesis memos MUST be saved as markdown files, not just displayed in conversation. Users need persistent documents they can reference.
- Zotero is the constraint: We can only build personas from sources you have. Better library = better simulation.
- 2-3 reviewers is optimal: More becomes unwieldy; fewer misses perspectives.
- Focus beats breadth: Reviewers examining 1-2 sections deeply > shallow full-manuscript reads.
- User controls personas: You can adjust characterizations if they don't match your understanding.
- Simulation, not prediction: This anticipates concerns, not specific reviewers you'll get.
- Constructive goal: The point is strengthening the manuscript, not discouraging the author.
Output File Structure
All outputs are saved to a peer-review-analysis/ folder in the manuscript directory.
Use theory-based names for files (not person names):
peer-review-analysis/
├── review-disengagement-typology.md # Named for theoretical perspective
├── review-emotions-movements.md # Named for theoretical perspective
├── review-activist-careers.md # Named for theoretical perspective
├── synthesis-memo.md # Synthesis and response strategy
└── [additional files] # Personas, revision logs, etc.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

