How do I install the Rt Replication Package skill?

Run npx skillmds@latest add brycewang-stanford/rt-replication-package in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rt Replication Package safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rt Replication Package?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rt Replication Package free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rt Replication Package?

brycewang-stanford (@brycewang-stanford) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rt Replication Package by brycewang-stanford

Name: Rt Replication Package
Rating: 4.2 (5 reviews)
Author: brycewang-stanford

Rt Replication Package

Use before final submission or on acceptance to assemble and validate the Data-Editor replication package against the target venue's data-and-code policy — master script, pinned environment, README/roadmap, restricted-data plan, and a script-to-exhibit output map, with a checklist that catches the numbers a Data Editor would fail to reproduce. Reads the venue policy live from the pack's source-map.

brycewang-stanford Updated Sep 8, 2026 1k repo stars

File contents

Replication Package (rt-replication-package)

The step that now blocks acceptance at the top (AEA / JF / Management Science Data Editors re-run your code and check every number). Full manifest + validation checklist: shared-resources/empirical-methods/replication-package.md.

When to trigger

Approaching final submission, or a conditional accept with a data-and-code requirement.
A Data Editor / verification service needs the package.

What it does

Read the venue policy from the target pack's resources/official-source-map.md (code at submission vs. acceptance? Data Editor? AsCollected page? restricted-data rule? hosting?). Match it exactly.
Assemble the manifest: master script (raw → all exhibits), ordered steps (clean → construct → estimate → robustness → tables), pinned environment, README/roadmap, data (or pseudo/synthetic data for restricted access + access instructions), the script→exhibit output map, and the disclosure statement.
Validate with the checklist: runs clean end-to-end on a fresh machine; every reported number reproduced (body + appendix); seeded/deterministic; restricted-data plan; output map complete; venue policy satisfied.

Hard rules

Every reported number traces to a script step (body and appendix).
Deterministic — pin versions, seed RNGs.
Restricted data → pseudo/synthetic data + access instructions, never confidential data committed.
Match the venue's exact policy from the source-map; re-verify before submission.
Keep it in sync with the execution bridge — when a revision re-runs an estimate, regenerate the affected outputs.

Output format

【Venue policy】(code timing, Data Editor, restricted-data rule, hosting)
【Manifest】master · steps · env · README · data · output-map · disclosure — status each
【Validation】end-to-end ✓/✗ · all numbers reproduced ✓/✗ · seeded ✓/✗ · restricted-data plan ✓/✗
【Blocking gaps】what would fail a Data-Editor check, ranked
【Ready?】GO / NOT-YET — deciding items

Anti-patterns

"Works on my machine" (absolute paths, unpinned versions, manual steps); reported numbers the script doesn't reproduce; committing confidential data; leaving assembly to post-accept crunch.

---name: rt-replication-packagedescription: Use before final submission or on acceptance to assemble and validate the Data-Editor replication package against the target venue's data-and-code policy — master script, pinned environment, README/roadmap, restricted-data plan, and a script-to-exhibit output map, with a checklist that catches the numbers a Data Editor would fail to reproduce. Reads the venue policy live from the pack's source-map.---# Replication Package (rt-replication-package)The step that now blocks acceptance at the top (AEA / JF / Management Science Data Editorsre-run your code and check every number). Full manifest + validation checklist:[`shared-resources/empirical-methods/replication-package.md`](../../../shared-resources/empirical-methods/replication-package.md).## When to trigger- Approaching final submission, or a conditional accept with a data-and-code requirement.- A Data Editor / verification service needs the package.## What it does1. **Read the venue policy** from the target pack's `resources/official-source-map.md` (code at submission vs. acceptance? Data Editor? AsCollected page? restricted-data rule? hosting?). **Match it exactly.**2. **Assemble the manifest**: master script (raw → all exhibits), ordered steps (clean → construct → estimate → robustness → tables), pinned environment, README/roadmap, data (or pseudo/synthetic data for restricted access + access instructions), the script→exhibit output map, and the disclosure statement.3. **Validate** with the checklist: runs clean end-to-end on a fresh machine; every reported number reproduced (body + appendix); seeded/deterministic; restricted-data plan; output map complete; venue policy satisfied.## Hard rules1. **Every reported number traces to a script step** (body and appendix).2. **Deterministic** — pin versions, seed RNGs.3. **Restricted data → pseudo/synthetic data + access instructions**, never confidential data committed.4. **Match the venue's exact policy** from the source-map; re-verify before submission.5. **Keep it in sync with the execution bridge** — when a revision re-runs an estimate, regenerate the affected outputs.## Output format```【Venue policy】(code timing, Data Editor, restricted-data rule, hosting)【Manifest】master · steps · env · README · data · output-map · disclosure — status each【Validation】end-to-end ✓/✗ · all numbers reproduced ✓/✗ · seeded ✓/✗ · restricted-data plan ✓/✗【Blocking gaps】what would fail a Data-Editor check, ranked【Ready?】GO / NOT-YET — deciding items```## Anti-patterns- "Works on my machine" (absolute paths, unpinned versions, manual steps); reported numbers the script doesn't reproduce; committing confidential data; leaving assembly to post-accept crunch.

Frequently asked questions