Menu

Individual skill

io-transparency-and-data-policy

0upvotes

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.

International-Organization-Skills/skills/io-transparency-and-data-policy/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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**
Back to top