preregister · git:20261106.a8c8716 · 2026-11-06 · sha256 c281dcc5e0e28b52

preregister git:20261106.a8c8716A

Immutable. This exact content never changes and is served at /api/v1/blob/c281dcc5e0e28b52.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_e7ljdyzb4bueqhdd/c281dcc5e0e28b52a55ad7fbfddd6e942392ee9dea9f1c7f51f61611e60cdf00.json

Then /plugin install preregister@markdownregistry-e7ljdyzb4bueqhdd in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: preregister
description: Draft a structured preregistration document (OSF, AsPredicted, or AEA RCT Registry style) from a research spec or free-form study description. Output is a Markdown file with hypotheses, design, sampling plan, analysis plan, exclusions, and inference criteria — annotated with MUST / SHOULD / MAY clarity flags. Use when user says "preregister", "draft a preregistration", "OSF preregistration", "AsPredicted", "AEA RCT registry", "PAP", "preanalysis plan", or before launching an experiment / data collection / analysis on data the analyst has not yet seen. NOT a registry submission tool — produces a document the user uploads to OSF / AsPredicted / AEA themselves.
---
<!-- Generated by scripts/sync-agent-skills.py from .claude/skills/preregister/SKILL.md. Do not edit: change the source and re-run the script. -->

# preregister

This skill's instructions live in [`.claude/skills/preregister/SKILL.md`](../../../.claude/skills/preregister/SKILL.md).
Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md)
first if you have not already.

It was written for Claude Code. Running it from Codex, Antigravity or another agent:

- **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for.
- **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the
  `Agent` or `Task` tool), do that step where it appears in the procedure: never later, and never
  skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it
  commits). Read the agent's file for what the step checks.
- **Fresh context.** If the step needs a context that has not seen your work, for example a claim
  verifier that must never see the draft, run it in a separate session or worker that has not
  seen the draft, if your tool can start one, and give it only what the step says to pass. If it
  cannot, do the step yourself, mark every result it produced *not independently verified*, and
  tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before
  relying on it.
- **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and
  `disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them.
- **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md`
  yourself; the git pre-commit gate and CI still apply to your commits.