red-replication-and-data-policy
Use when building the Review of Economic Dynamics (RED) data-and-code archive to the journal's actual "Availability of Data and Computer Code for Published Papers" policy and Elsevier Option C data instructions — covering computational and empirical papers, the specific readme.txt requirements, .zip/.gz/.gzip submission to the RED code editor, posting on the RED site, RePEc Computer Codes indexing, repository/data-statement metadata, and the proprietary-data exemption.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill red-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/Code Policy for RED (red-replication-and-data-policy) ## When to trigger - Preparing the materials that must be in place **before final acceptance** - A computational paper unsure whether code-only (no data) still triggers the policy (it does) - Handling proprietary/confidential data and the exemption process ## RED's policy (verified) RED enforces an **Availability of Data and Computer Code for Published Papers** policy. Before final acceptance, authors must provide data and code sufficient for others to replicate the results. RED's culture is **code-first** — the policy covers **computational as well as empirical** papers, and archives are first-class, citable objects. The Elsevier Guide also applies **Option C** research-data instructions: deposit research data in a relevant repository and cite/link it in the article when possible, or provide a data-availability statement explaining why sharing is not possible. - **Empirical papers**: final datasets **plus** the code that manipulates them and, if applicable, how the final dataset was derived from original sources. - **Computational / theoretical papers**: the **final programs** that generate the results. - *
- When to trigger
- RED's policy (verified)
- Checklist
- Anti-patterns
- Archive manifest
- Archive layout that satisfies the policy
- Failure modes the code editor's check catches
- Output format
- Supplementary resources
What does the red-replication-and-data-policy skill do?
Use when building the Review of Economic Dynamics (RED) data-and-code archive to the journal's actual "Availability of Data and Computer Code for Published Papers" policy and Elsevier Option C data instructions — covering computational and empirical papers, the specific readme.txt requirements, .zip/.gz/.gzip submission to the RED code editor, posting on the RED site, RePEc Computer Codes indexing, repository/data-statement metadata, and the proprietary-data exemption.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill red-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.