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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-replication-package --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`](../../../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 1. **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;
- When to trigger
- What it does
- Hard rules
- Output format
- Anti-patterns
What does the rt-replication-package skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rt-replication-package --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.