jop-replication-and-data-policy
Use when preparing the replication / data-access materials for a The Journal of Politics (JOP) manuscript. JOP makes acceptance contingent on replicability — a JOP replication analyst assigned at conditional acceptance assesses the package you deposit in the JOP Dataverse (Harvard Dataverse), and non-replicable manuscripts are rejected. Prepares the package; it does not waive the requirement.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jop-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 (jop-replication-and-data-policy) This is JOP's signature skill. JOP does not merely request a deposit — **acceptance is contingent on replicability**. A **JOP replication analyst**, assigned at **conditional acceptance**, assesses your materials before publication, and **manuscripts that are not replicable are rejected**. Build the package **as you analyze**, not at acceptance. ## When to trigger - Building the replication / data-access package (start during analysis) - A manuscript reached **conditional acceptance** and a replication analyst was assigned - Data cannot be fully shared (privacy, ethics, legal/provider restrictions) and you need the path - Any empirical, simulation-based, or formal-theoretical paper headed for JOP ## What JOP requires (verify current wording on the policy page) 1. **Replicability-contingent acceptance.** It is JOP policy to publish a paper only if the data are **accessible**, the analyses **fully documented**, and the empirical findings **reproducible**. The conditional accept is *conditional* on passing this check. 2. **The JOP replication analyst.** At conditional acceptance, a JOP analyst is assigned and **initially as
- When to trigger
- What JOP requires (verify current wording on the policy page)
- When data cannot be shared (access path)
- Build-as-you-go checklist
- Anti-patterns
- What the analyst checks (failure-mode table)
- Worked micro-example (illustrative)
- Analyst pushback patterns and the JOP fix
- Output format
- Supplementary resources
What does the jop-replication-and-data-policy skill do?
Use when preparing the replication / data-access materials for a The Journal of Politics (JOP) manuscript. JOP makes acceptance contingent on replicability — a JOP replication analyst assigned at conditional acceptance assesses the package you deposit in the JOP Dataverse (Harvard Dataverse), and non-replicable manuscripts are rejected. Prepares the package; it does not waive the requirement.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jop-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.