Token导航 LogoToken导航

Agent Skill · 研究检索

peer-reviewer(同行评审员)

用于辅助数据整理、表格处理、CSV/Excel 分析、指标计算和图表准备。它适合让 Agent 清洗字段、汇总数据、发现异常、生成统计口径或把分析结果转成可读说明。使用时需要确认数据来源、字段含义和时间范围,避免把样本数据当全量事实;涉及敏感数据、导出文件或批量写回时,应先确认权限和脱敏边界。

peer-reviewer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 53,815。

总安装 523周安装 22GitHub Stars 50下载 183核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:peer-reviewer(同行评审员)
来源仓库:https://github.com/nealcaren/social-data-analysis
仓库路径:skills/peer-reviewer
安装命令:
npx skills add https://github.com/nealcaren/social-data-analysis --skill peer-reviewer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/nealcaren/social-data-analysis --skill peer-reviewer

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

peer-reviewer 用于辅助数据整理、表格处理和指标计算。适合让 Agent 清洗字段、汇总数据、发现异常并生成统计口径。使用时需确认数据来源、字段含义和时间范围,避免误用样本为全量事实。涉及敏感数据或批量写回时,应先确认权限和脱敏边界。

通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限和维护状态。

来源仓库内路径:skills/peer-reviewer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/nealcaren/social-data-analysis --skill peer-re…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

peer-reviewer 怎么安装?

在终端执行 npx skills add https://github.com/nealcaren/social-data-analysis --skill peer-reviewer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

peer-reviewer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

peer-reviewer 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

peer-reviewer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

peer-reviewer 用的人多吗?

公开数据是累计安装 523 次,近一周安装 22 次,下载 183 次,GitHub 50 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

peer-reviewer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
peer-reviewer

同行评审员 · 本页

52350调用外部服务未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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:

  1. Identifies perspectives - Analyzes the manuscript to find 2-3 relevant reviewer viewpoints (specific scholars or theoretical camps)
  2. Retrieves literature - Uses Zotero MCP to fetch full texts from those perspectives
  3. Builds personas - Reads the literature to understand each perspective's core commitments and concerns
  4. Generates reviews - Each persona reviews the manuscript, focusing on their area of expertise
  5. Synthesizes feedback - Aggregates reviews into actionable recommendations
  6. 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

  1. Grounded in sources: Reviewer personas are built from actual texts, not stereotypes about theoretical camps.
  2. Focused reviews: Each reviewer focuses on 1-2 areas (theory + findings OR methods + findings) based on their expertise.
  3. Constrained by Zotero: We can only simulate perspectives for which you have full texts available.
  4. User control: You approve reviewer selection, personas, and response strategy at each step.
  5. Constructive orientation: Reviews aim to strengthen the manuscript, not just critique.
  6. Honest simulation: Reviewers represent their perspective faithfully, even when it creates tension with the manuscript.

The Review Focus Matrix

Reviewer TypePrimary FocusSecondary Focus
TheoreticalTheory sectionFindings (theoretical implications)
MethodologicalMethods sectionFindings (analytic validity)
Empirical/SubstantiveFindingsTheory (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

PhaseModelRationale
Phase 0: IntakeOpusStrategic judgment about perspectives
Phase 1: RetrievalSonnetZotero queries, source organization
Phase 2: PersonaOpusDeep reading, profile construction
Phase 3: ReviewsOpusInhabiting perspectives, critical reading
Phase 4: SynthesisOpusPrioritization, strategy
Phase 5: RevisionOpusWriting support

Starting the Process

When the user is ready to begin:

  1. Ask about the manuscript: "Where is your manuscript? Is it a complete draft or specific sections?"
  2. 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?"
  3. Ask about Zotero: "Is your Zotero library connected? Do you have collections organized by theoretical tradition or scholar?"
  4. 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.

平台分布

Codex

35.67%
按下载量换算65

Claude

33.62%
按下载量换算62

Cursor

19.49%
按下载量换算36

Gemini CLI

9.19%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills