review-research
정보
`review-research` 스킬은 클로드가 연구 자료에 대해 구조화된 동료 검토를 수행하여 방법론, 통계적 적절성, 재현가능성을 평가할 수 있도록 합니다. 원고, 프리프린트, 연구 프로토콜 검토 또는 주장의 근거가 되는 증거 평가를 위해 설계되었습니다. 주요 기능으로는 편향 식별과 실험 설계 및 원고 품질에 대한 건설적인 피드백 제공이 포함됩니다.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/review-researchClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Review Research
Perform structured peer review of research work. Evaluate methodology, statistical choices, reproducibility, overall scientific rigour.
When Use
- Reviewing manuscript, preprint, or internal research report
- Evaluating research proposal or study protocol
- Assessing quality of evidence behind a claim or recommendation
- Providing feedback on colleague research design before data collection
- Reviewing thesis chapter or dissertation section
Inputs
- Required: Research document (manuscript, report, proposal, or protocol)
- Required: Field/discipline context (affects methodology standards)
- Optional: Journal or venue guidelines (if reviewing for publication)
- Optional: Supplementary materials (data, code, appendices)
- Optional: Prior reviewer comments (if reviewing a revision)
Steps
Step 1: First Pass — Scope and Structure
Read entire document once to understand:
- Research question: Clearly stated and specific?
- Contribution claim: What is novel or new?
- Overall structure: Does it follow expected format (IMRaD, or venue-specific)?
- Scope match: Work 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]
Got: Clear understanding of paper claims and contribution. If fail: Research question unclear after full read? Note this as major concern and proceed.
Step 2: Evaluate Methodology
Assess research design against standards for the field:
Quantitative Research
- Study design appropriate for research question (experimental, quasi-experimental, observational, survey)
- Sample size justified (power analysis or practical rationale)
- Sampling method described and appropriate (random, stratified, convenience)
- Variables clearly defined (independent, dependent, control, confounding)
- Measurement instruments validated and 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 and 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 quantitative and qualitative components meet their respective standards
Got: Methodology checklist completed with specific observations for each item. If fail: Critical methodology information missing? Flag as major concern rather than assume.
Step 3: Assess Statistical and Analytical Choices
- Statistical methods appropriate for data type and research question
- Assumptions of statistical tests checked and reported (normality, homoscedasticity, independence)
- Effect sizes reported alongside p-values
- Confidence intervals provided where appropriate
- Multiple comparison corrections applied when needed (Bonferroni, FDR, etc.)
- Missing data handling described and appropriate
- Sensitivity analyses conducted for key assumptions
- Results interpretation consistent with analysis (not overstating findings)
Common statistical red flags:
- p-hacking indicators (many comparisons, selective reporting, "marginally significant")
- Inappropriate tests (t-test on non-normal data without justification, parametric tests on ordinal data)
- Confusing statistical significance with practical significance
- No effect size reporting
- Post-hoc hypotheses presented as a priori
Got: Statistical choices evaluated with specific concerns documented. If fail: Reviewer lacks expertise in specific method? Acknowledge this and recommend specialist reviewer.
Step 4: Evaluate Reproducibility
- Data availability stated (open data, repository link, available on request)
- Analysis code availability stated
- Software versions and environments documented
- Random seeds or reproducibility mechanisms described
- Key parameters and hyperparameters reported
- Computational environment described (hardware, OS, dependencies)
Reproducibility tiers:
| Tier | Description | Evidence |
|---|---|---|
| Gold | Fully reproducible | Open data + open code + containerized environment |
| Silver | Substantially reproducible | Data available, analysis described in detail |
| Bronze | Potentially reproducible | Methods described but no data/code sharing |
| Opaque | Not reproducible | Insufficient method detail or proprietary data |
Got: Reproducibility tier assigned with justification. If fail: Data cannot be shared (privacy, proprietary)? Synthetic data or detailed pseudocode acceptable alternative — note whether this provided.
Step 5: Identify Potential Biases
- Selection bias: Were participants representative of target population?
- Measurement bias: Could measurement process have systematically distorted results?
- Reporting bias: Are all outcomes reported, including non-significant ones?
- Confirmation bias: Did authors only look for evidence supporting their hypothesis?
- Survivorship bias: Were dropouts, excluded data, or failed experiments accounted for?
- Funding bias: Is funding source disclosed and could it influence findings?
- Publication bias: Is this complete picture or might negative results be missing?
Got: Potential biases identified with specific examples from manuscript. If fail: Biases cannot be assessed from available information? Recommend authors address this explicit.
Step 6: Write the Review
Structure review constructively:
## 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]
Got: Review specific, constructive, references exact locations in manuscript. If fail: Review running long? Prioritize major concerns and note minor issues in summary list.
Checks
- Every major concern references specific section, figure, or claim
- Feedback constructive — problems paired with suggestions
- Positive aspects acknowledged alongside concerns
- Statistical assessment matches analysis methods used
- Reproducibility explicit evaluated
- Recommendation consistent with severity of concerns raised
- Tone professional, respectful, collegial
Pitfalls
- Vague criticism: "The methodology is weak" is unhelpful. Specify what is weak and why.
- Demand a different study: Review research that was done, not research you would have done.
- Ignore scope: Conference paper has different expectations than journal article.
- Ad hominem: Review the work, not the authors. Never reference author identity.
- Perfectionism: No study is perfect. Focus on concerns that would change conclusions.
See Also
review-data-analysis— deeper focus on data quality and model validationformat-apa-report— APA formatting standards for research reportsgenerate-statistical-tables— publication-ready statistical tablesvalidate-statistical-output— statistical output verification
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
