jpube-replication-and-data-policy
Use when assembling data and code for a Journal of Public Economics (JPubE) manuscript under Elsevier's Option C research-data framework — data-availability statements, repository deposit/citation/linking, restricted administrative data, and a reproducible package. It does not run the analysis.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-replication-and-data-policy --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 & Data Policy (jpube-replication-and-data-policy) ## When to trigger - You are preparing a data-availability statement or research-data declaration - Your results rest on restricted tax/health/register data and you must document access - You want a reproducible package that pre-empts referee replication requests - You need to choose between repository deposit and a restricted-data access statement ## JPubE / Elsevier requirement JPubE's Guide for Authors applies Elsevier **Option C** research-data instructions: deposit research data in a relevant repository, cite and link the dataset in the article, or provide a statement explaining why research data cannot be shared. For public-economics work using restricted tax, health, or register microdata, the practical route is usually a data statement plus a code package and exact access path rather than public release of protected rows. ## Build the package around Option C Public-economics referees frequently ask to see the elasticity/bunching/RD pipeline, so build a clean package around the data route: - **Data-availability statement** matching reality: open data -> link the repository; restricted tax/health/register data ->
- When to trigger
- JPubE / Elsevier requirement
- Build the package around Option C
- Checklist
- Anti-patterns
- Data-availability routing by source
- Worked vignette: a register-DID package referees can trust
- Calibration anchors
- Output format
What does the jpube-replication-and-data-policy skill do?
Use when assembling data and code for a Journal of Public Economics (JPubE) manuscript under Elsevier's Option C research-data framework — data-availability statements, repository deposit/citation/linking, restricted administrative data, and a reproducible package. It does not run the analysis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-replication-and-data-policy --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.