io-transparency-and-data-policy
Use when preparing the replication/transparency materials for an International Organization (IO) manuscript. IO's signature requirement is verification BEFORE final acceptance — the editorial staff request data and code at conditional acceptance, IO staff re-run quantitative results and check proofs of formal models, and editors withhold final acceptance until all reported results are confirmed; materials then deposit to the IO Dataverse with a DOI and a Data Availability Statement. Prepares the package; it does not waive requirements.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill io-transparency-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.
# Transparency & Data Policy (io-transparency-and-data-policy) IO does not just ask for data — its **editorial staff re-run your quantitative results and verify the proofs of your formal models, and editors will not issue final acceptance until all reported analyses are confirmed.** This pre-publication verification is IO's signature. Build the package as you analyze so conditional acceptance does not stall. ## When to trigger - Building the reproducibility/replication package (start during analysis, not at acceptance) - A manuscript reached **conditional acceptance** and the editorial staff requested data and code - You have a **formal model** whose proofs IO staff will verify - Data cannot be fully shared (privacy, ethics, legal/provider restrictions) and you need the path - Writing the **Data Availability Statement** ## What IO requires (verify current wording on the policy page — 待核实 on verbatim text) 1. **No data at initial submission.** Authors **do not** provide data or command files when first submitting (consistent with double-blind review). 2. **Data requested at conditional acceptance.** The editorial staff **request the data and command files at the time of conditional
- When to trigger
- When data cannot be shared (exemption path)
- Build-as-you-go checklist
- Anti-patterns
- Output format
- Supplementary resources
What does the io-transparency-and-data-policy skill do?
Use when preparing the replication/transparency materials for an International Organization (IO) manuscript. IO's signature requirement is verification BEFORE final acceptance — the editorial staff request data and code at conditional acceptance, IO staff re-run quantitative results and check proofs of formal models, and editors withhold final acceptance until all reported results are confirmed; materials then deposit to the IO Dataverse with a DOI and a Data Availability Statement. Prepares the package; it does not waive requirements.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill io-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.