MCP HubMCP Hub
스킬 목록으로 돌아가기

review-research

pjt222
업데이트됨 2 days ago
6 조회
17
2
17
GitHub에서 보기
디자인aidesign

정보

이 스킬은 연구 자료의 방법론, 통계적 적절성, 재현성을 평가하여 체계적인 동료 검토를 가능하게 합니다. 원고, 프리프린트, 연구 제안서 또는 학위 논문 장에 대한 과학적 엄밀성과 편향성을 평가하는 데 사용하세요. 실험 설계와 증거의 질을 분석하여 건설적인 피드백을 제공합니다.

빠른 설치

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

디자인

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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.

스킬 보기