govern-transparency-and-data
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.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill govern-transparency-and-data --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 (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 exemption/access path - A qualitative or comparative-historical paper needs a transparency plan for sources and process tracing - Referencing a preregistration / pre-analysis plan (it may be supplied as supplementary material) ## The Data Availability S
- When to trigger
- The Data Availability Statement (mandatory)
- Checklist (build the replication materials as you go)
- Qualitative & comparative-historical transparency
- Restricted data (exemption / access path)
- Pre-analysis plan
- Anti-patterns
- Output format
- Supplementary resources
What does the govern-transparency-and-data skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill govern-transparency-and-data --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.