Menu

Individual skill

govern-transparency-and-data

0upvotes

Use when preparing the Data Availability Statement and replication materials for a Governance: An International Journal of Policy, Administration, and Institutions manuscript. Governance requires the statement (mandatory) and encourages sharing data/code in a DOI-citable repository, but does not run a verified pre-publication reproduction check like APSR. Builds the statement and materials; it does not waive requirements.

Governance-Journal-Skills/skills/govern-transparency-and-data/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
No
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,400
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 (govern-transparency-and-data)

*Governance* requires a **Data Availability Statement** with the manuscript — a statement of whether
replication materials (data, code) exist and how a reader can access them. Be clear-eyed about the bar:
the **statement is mandatory**, and sharing in a DOI-citable repository is recommended and increasingly
expected, but *Governance* does **not** run a verified, editor-checked pre-publication reproduction gate
the way APSR's Dataverse workflow does. That makes the statement an honesty-and-access commitment, not a
reproduction certificate — so write it precisely and build the materials as you go.

## When to trigger

- Writing the **Data Availability Statement** for submission (it is required at submission)
- Building the replication package (data, code, documentation) to back that statement
- Data cannot be fully shared (privacy, ethics, legal/provider restrictions) and you need the
Back to top