返回技能列表

review-research

pjt222
更新于 2 days ago
8 次查看
17
2
17
在 GitHub 上查看
设计aidesign

关于

This skill enables structured peer review of research materials by evaluating methodology, statistical appropriateness, and reproducibility. Use it to assess manuscripts, preprints, research proposals, or thesis chapters for scientific rigor and bias. It provides constructive feedback by analyzing experimental design and evidence quality.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/review-research

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Review Research

Structured peer review of research, eval methodology, statistical choices, reproducibility, overall scientific rigour.

Use When

  • Review manuscript, preprint, internal research report
  • Eval research proposal or study protocol
  • Assess evidence quality behind claim/recommendation
  • Provide feedback on colleague's design before data collection
  • Review thesis chapter or dissertation section

In

  • Required: Research doc (manuscript, report, proposal, protocol)
  • Required: Field/discipline ctx (affects methodology stds)
  • Optional: Journal/venue guidelines (if reviewing for publication)
  • Optional: Supplementary materials (data, code, appendices)
  • Optional: Prior reviewer comments (if reviewing revision)

Do

Step 1: First Pass — Scope + Structure

Read entire doc once → understand:

  1. Research q: Clearly stated + specific?
  2. Contribution claim: What is novel?
  3. Overall structure: Follows expected format (IMRaD, venue-specific)?
  4. Scope match: Appropriate for target audience/venue?
## First Pass Assessment
- **Research question**: [Clear / Vague / Missing]
- **Novelty claim**: [Stated and supported / Overstated / Unclear]
- **Structure**: [Complete / Missing sections: ___]
- **Scope fit**: [Appropriate / Marginal / Not appropriate]
- **Recommendation after first pass**: [Continue review / Major concerns to flag early]

→ Clear understanding of paper's claims + contribution. If err: research q unclear after full read → note as major concern + proceed.

Step 2: Eval Methodology

Assess design vs std for field:

Quantitative Research

  • Study design appropriate for q (experimental, quasi-experimental, observational, survey)
  • Sample size justified (power analysis or practical rationale)
  • Sampling method described + appropriate (random, stratified, convenience)
  • Vars clearly defined (independent, dependent, control, confounding)
  • Measurement instruments validated + reliability reported
  • Data collection procedure reproducible from description
  • Ethical considerations addressed (IRB/ethics approval, consent)

Qualitative Research

  • Methodology explicit (grounded theory, phenomenology, case study, ethnography)
  • Participant selection criteria + saturation discussed
  • Data collection methods described (interviews, observations, documents)
  • Researcher positionality acknowledged
  • Trustworthiness strategies reported (triangulation, member checking, audit trail)
  • Ethical considerations addressed

Mixed Methods

  • Rationale for mixed design explained
  • Integration strategy described (convergent, explanatory sequential, exploratory sequential)
  • Both quant + qual components meet respective stds

→ Methodology checklist completed w/ specific obs each item. If err: critical methodology missing → flag major concern not assume.

Step 3: Statistical + Analytical Choices

  • Stats appropriate for data type + research q
  • Assumptions checked + reported (normality, homoscedasticity, independence)
  • Effect sizes reported alongside p-values
  • Confidence intervals provided where appropriate
  • Multi comparison corrections applied when needed (Bonferroni, FDR, etc.)
  • Missing data handling described + appropriate
  • Sensitivity analyses for key assumptions
  • Results interpretation consistent w/ analysis (no overstating)

Common stat red flags:

  • p-hacking indicators (many comparisons, selective reporting, "marginally significant")
  • Inappropriate tests (t-test on non-normal w/o justification, parametric on ordinal)
  • Confusing statistical significance w/ practical
  • No effect size reporting
  • Post-hoc hypotheses presented as a priori

→ Stat choices eval'd w/ specific concerns documented. If err: reviewer lacks expertise in specific method → ack + recommend specialist reviewer.

Step 4: Reproducibility

  • Data availability stated (open data, repo link, on req)
  • Analysis code availability stated
  • Software vers + envs documented
  • Random seeds or reproducibility mechanisms described
  • Key params + hyperparameters reported
  • Computational env described (hardware, OS, deps)

Reproducibility tiers:

TierDescriptionEvidence
GoldFully reproducibleOpen data + open code + containerized environment
SilverSubstantially reproducibleData available, analysis described in detail
BronzePotentially reproducibleMethods described but no data/code sharing
OpaqueNot reproducibleInsufficient method detail or proprietary data

→ Reproducibility tier assigned w/ justification. If err: data can't be shared (privacy, proprietary) → synthetic data or detailed pseudocode acceptable alt — note if provided.

Step 5: Identify Biases

  • Selection bias: Participants representative of target pop?
  • Measurement bias: Could measurement systematically distort results?
  • Reporting bias: All outcomes reported, including non-significant?
  • Confirmation bias: Did authors only look for evidence supporting hypothesis?
  • Survivorship bias: Dropouts, excluded data, failed exps accounted for?
  • Funding bias: Funding source disclosed + could influence findings?
  • Publication bias: Complete picture or might negative results be missing?

→ Potential biases ID'd w/ specific examples from manuscript. If err: biases can't be assessed from available info → recommend authors address explicitly.

Step 6: Write Review

Structure constructive:

## Summary
[2-3 sentences summarizing the paper's contribution and your overall assessment]

## Major Concerns
[Issues that must be addressed before the work can be considered sound]

1. **[Concern title]**: [Specific description with reference to section/page/figure]
   - *Suggestion*: [How the authors might address this]

2. ...

## Minor Concerns
[Issues that improve quality but are not fundamental]

1. **[Concern title]**: [Specific description]
   - *Suggestion*: [Recommended change]

## Questions for the Authors
[Clarifications needed to complete the evaluation]

1. ...

## Positive Observations
[Specific strengths worth acknowledging]

1. ...

## Recommendation
[Accept / Minor revision / Major revision / Reject]
[Brief rationale for the recommendation]

→ Review specific, constructive, refs exact locations in manuscript. If err: review running long → prioritize major concerns + note minor in summary list.

Check

  • Every major concern refs specific section, figure, claim
  • Feedback constructive — problems paired w/ suggestions
  • Positive aspects ack'd alongside concerns
  • Stat assessment matches analysis methods used
  • Reproducibility explicitly eval'd
  • Recommendation consistent w/ severity of concerns raised
  • Tone professional, respectful, collegial

Traps

  • Vague criticism: "Methodology is weak" unhelpful. Specify what + why.
  • Demand diff study: Review research done, not research you would have done.
  • Ignore scope: Conference paper has diff expectations than journal article.
  • Ad hominem: Review work, not authors. Never ref author identity.
  • Perfectionism: No study perfect. Focus on concerns changing conclusions.

  • review-data-analysis — deeper focus on data quality + model validation
  • format-apa-report — APA formatting stds for research reports
  • generate-statistical-tables — publication-ready statistical tables
  • validate-statistical-output — statistical output verification

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-ultra/skills/review-research
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

executing-plans

设计

该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。

查看技能

requesting-code-review

设计

该Skill可在完成任务、实现主要功能或合并代码前自动调度代码审查子代理,确保实现符合需求和计划。它支持通过指定git SHA范围进行精准的代码变更审查,帮助开发者在关键节点及时发现潜在问题。核心原则是"早审查、勤审查",适用于开发流程的各个关键阶段。

查看技能

connect-mcp-server

设计

这个Skill指导开发者如何将MCP服务器连接到Claude Code,支持HTTP、stdio和SSE三种传输协议。它涵盖了从安装配置到认证安全的完整流程,适用于集成GitHub、Notion、数据库等外部服务。当开发者需要添加集成、配置外部工具或提及MCP相关功能时,这个Skill能提供实用的操作指南。

查看技能

web-cli-teleport

设计

该Skill帮助开发者根据任务特性选择Claude Code的Web或CLI界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。

查看技能