stata-replication · git:20261106.a8c8716 · 2026-11-06 · sha256 8f9535597b069b3f
stata-replication git:20261106.a8c8716A
Immutable. This exact content never changes and is served at /api/v1/blob/8f9535597b069b3f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_e4a3ieam5a6ruvfg/8f9535597b069b3ffa24ab8f37b0255f46dfa97a5a83d1cff4c989fb0bdfcaab.json
Then /plugin install stata-replication@markdownregistry-e4a3ieam5a6ruvfg 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: stata-replication description: End-to-end Stata replication pipeline — scaffolds numbered `.do` files in `scripts/stata/`, executes them via the `stata-mcp` MCP server, captures logs and outputs to `output/`, and produces publication-ready tables (esttab) and figures (graph export). Mirrors `/data-analysis` for R-first projects. Use when user says "stata replication", "set up Stata pipeline", "scaffold the .do files", "run Stata analysis", "AEA replication package in Stata", or when a project's analysis language is Stata not R. --- <!-- Generated by scripts/sync-agent-skills.py from .claude/skills/stata-replication/SKILL.md. Do not edit: change the source and re-run the script. --> # stata-replication This skill's instructions live in [`.claude/skills/stata-replication/SKILL.md`](../../../.claude/skills/stata-replication/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.