Agent skill · Data & Analytics

wp-transparency-and-data-policy

Use when preparing replication / transparency materials for a World Politics manuscript. World Politics requires authors who rely on quantitative data to deposit replication materials in the World Politics Dataverse after acceptance and before publication, with an explanatory file that lets others replicate the exact numerical results; embargoes up to two years may be approved by the editorial committee. Prepares the package; it does not waive requirements.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wp-transparency-and-data-policy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: World-Politics-Skills/skills/wp-transparency-and-data-policy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Transparency & Data Policy (wp-transparency-and-data-policy) World Politics has a **Dataverse archive**, and **authors who rely on quantitative data must deposit** their materials there **after a piece is accepted but prior to publication**. The deposited file must let others **replicate the exact numerical results**. Build the package as you go so acceptance does not stall. ## When to trigger - Building the replication package for a quantitative or mixed-method paper - A manuscript has been **accepted** and you must deposit before publication - Original/proprietary data require an **embargo** and you need the approval path - Documenting qualitative/comparative-historical sources for transparency ## What World Politics requires (verify current wording on the policy page) 1. **Deposit to the World Politics Dataverse.** After acceptance and **before publication**, authors relying on quantitative data place materials in this trusted digital repository — not a personal site or generic cloud link. 2. **What to include.** The original data; specialized computer programs; lists of program recodes; extracts of existing data files; and — most importantly — an **explanatory file (README)**

What's inside
Steps it walks through
  1. When to trigger
  2. What World Politics requires (verify current wording on the policy page)
  3. Qualitative & comparative-historical transparency
  4. Build-as-you-go checklist
  5. Anti-patterns
  6. Replication-objection patterns and the venue-specific fix
  7. Worked micro-example (illustrative)
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the wp-transparency-and-data-policy skill do?

Use when preparing replication / transparency materials for a World Politics manuscript. World Politics requires authors who rely on quantitative data to deposit replication materials in the World Politics Dataverse after acceptance and before publication, with an explanatory file that lets others replicate the exact numerical results; embargoes up to two years may be approved by the editorial committee. Prepares the package; it does not waive requirements.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wp-transparency-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.

Keep going