Skip to content
Agentmart
Submit a tool

write-protocol

Use when drafting an IRB or ethics research protocol.

Skill by Aperivue

IndexedMIT★ 349
Write a review

Chalk Labs

Need help deploying write-protocol?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/aperivue-write-protocol

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when drafting an IRB or ethics research protocol. Writes Background, Study Design, Sample Size and Statistical Plan in full prose and leaves institution-specific sections as TODO skeletons. Filling an institutional Word form is /fill-protocol.

Use cases: documents, design, writing, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/write-protocol

What's inside

Skill name
write-protocol
Description
Use when drafting an IRB or ethics research protocol. Writes Background, Study Design, Sample Size and Statistical Plan in full prose and leaves institution-specific sections as TODO skeletons. Filling an institutional Word form is /fill-protocol.
License
MIT
Metadata
triggers: write protocol, IRB protocol, ethics protocol, research protocol, IRB submission, ethics submission, protocol draft
Instructions
118 lines in SKILL.md · view on GitHub

Files (4)

  • SKILL.md
  • ethics_checklist.md · references/
  • protocol_template.md · references/
  • skill.yml

SKILL.md (first lines)

# Write-Protocol Skill

Draft the scientific core of an IRB/ethics protocol and leave institution-specific sections as
`[TODO]` skeletons. Read both reference files before generating a protocol draft:

- `${CLAUDE_SKILL_DIR}/references/protocol_template.md` -- the 10-section structure, per-section
  guidance, and the `[TODO]` blocks for Sections 5-9
- `${CLAUDE_SKILL_DIR}/references/ethics_checklist.md` -- jurisdiction-specific ethical requirements

## Inputs

Collect the required inputs before generating; ask for any that are missing.

- **Required**: research question / hypothesis (specific, testable); study type (retrospective
  cohort, prospective cohort, cross-sectional, RCT, diagnostic accuracy, case-control, case
  series); target population (who, where, when); primary outcome; secondary outcomes (if any).
- **Optional**: key references (DOIs or search terms); institution name (header and ethics
  guidance); regulatory context -- Korea (PIPA), US (HIPAA/Common Rule), EU (GDPR), other.

Use prior skill outputs directly when they exist; when they do not, ask the user or call the skill:

- **design-study**: design recommendations, analysis unit, comparator design, validation strategy.
- **calc-sample-size**: `protocol/sample_size_justification.md` (canonical IRB-ready prose) and
  `protocol/sample_size_calc.{R,py}` (reproducible code).
- **search-lit**: Background references with verified citations.
- **define-variables**: `variable_operationalization.md` -- literature-grounded definitions,
  cutoffs, DB-variable mappings for the Methods section. **Precondition**: if the study is
  observational and no operationalization artifact exists, call `/define-variables` before
  drafting Methods. Do not invent phenotype/cutoff definitions from the data dictionary inside
  this skill.

---

## Protocol Structure -- 10 Sections

### Core Sections (Fully Generated)

#### Section 1: Background and Rationale (400-600 words)

Full paragraphs, no bullet points, flowing from clinical context (disease burden, current
practice) through the knowledge gap and rationale (what this study adds) to the research question
or hypothesis. Call `/search-lit` if key references are not provided. Cite a reference only with a
`/search-lit`-confirmed DOI or PMID; otherwise mark it `[UNVERIFIED - NEEDS MANUAL CHECK]`.

#### Section 2: Study Design and Eligibility Criteria (300-500 words)

Prose covering the study design with its justification (why this design answers this question),
the setting (single-center vs multi-center, institution description) and the study period,
followed by numbered inclusion and numbered exclusion criteria. If design-study output is
available, incorporate its analysis unit (patient vs lesion vs exam), comparator design,
validation strategy, and leakage risks with mitigations. Mark any clinical definition, diagnostic
criterion or guideline recommendation you cannot confirm `[VERIFY]` and ask the user.

#### Section 3: Sample Size Justification (150-300 words)

- If `protocol/sample_size_justification.md` exists (calc-sample-size output): embed it VERBATIM.
  Do not rephrase numbers.
- If not available: prompt the user to run `/calc-sample-size` first; only fall back to a basic
  justification if the user explicitly declines.
- Must include: test type, expected effect size (with literature source), alpha level, power,
  attrition adjustment.
- Final statement: "We plan to enroll N participants."

#### Section 4: Statistical Analysis Plan (300-500 words)

Full prose covering: descriptive statistics (continuous as mean (SD) or median (IQR); categorical
as count (%)); the primary analysis (test, assumptions, handling of violations); pre-specified
secondary analyses; pre-specified subgroup analyses with interaction tests; missing-data handling
(complete case, multiple imputation, sensitivity analysis); software name and version (e.g.,
R 4.4.0, Python 3.12, SAS 9.4); two-sided alpha = 0.05 unless otherwise justified.

### Skeleton Sections (TODO Markers)

Sections 5-9 are the `[TODO]` blocks from `protocol_template.md`, copied as they are; never fill
them with invented institutional content.

- Section 5: Study Title and Registration
- Section 6: Data Collection and Management
- Section 7: Ethical Considerations -- also add the template's jurisdiction guidance for the
  regulatory context, and use `ethics_checklist.md` for the full checklist.
- Section 8: Timeline and Milestones
- Section 9: Budget

#### Section 10: References

A numbered list of the Section 1 citations, the Section 3 effect-size sources, and any references
in the calc-sample-size output. Every entry has a verified DOI or PMID or is marked
`[UNVERIFIED - NEEDS MANUAL CHECK]`.

---

## Output Format

Generate a single markdown file: `protocol_draft.md`

- All 10 sections with clear numbering (1. through 10.)
- Core sections (1-4) in full prose; the Section 2 eligibility criteria are the only lists
- Skeleton sections (5-9) with `[TODO]` markers clearly visible
- Word count targets noted in comments at the start of each core section
- Institution name in the header if provided

After generating, tell the user which sections are ready for review, which `[TODO]` items need
their input, and the next steps (e.g., "Fill in Section 5 title and registration, then adapt
Section 7 to your IRB form").

## Quality Checks

Before delivering the protocol:

1. **Citation integrity**: every reference has a DOI or PMID, or is marked
   `[UNVERIFIED - NEEDS MANUAL CHECK]`
2. **Internal consistency**: sample size in Section 3 matches the analysis plan in Section 4
3. **Design alignment**: study type in Section 2 matches the statistical approach in Section 4
4. **TODO completeness**: all institution-specific items have `[TODO]` markers
5. **Word counts**: core sections fall within target ranges
6. **No AI patterns**: avoid phrases like "it is worth noting", "comprehensive", "plays a crucial role"

From Aperivue/medsci-skills, MIT.

More from Aperivue/medsci-skills

Signals

Stars
349
Forks
83
Open issues
4
Last commit (this folder)
Sep 30, 2026 (1 month ago)
Last release
Oct 4, 2026 (27 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Aperivue

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get write-protocol running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying write-protocol?

CallGet help
Cite this page

write-protocol skill. Agent Mart. https://agentmart.dev/skills/aperivue-write-protocol (last updated 2026-10-24)