Agent skill · Data & Analytics

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.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
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.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Governance-Journal-Skills/skills/govern-transparency-and-data/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 (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

What's inside
Steps it walks through
  1. When to trigger
  2. The Data Availability Statement (mandatory)
  3. Checklist (build the replication materials as you go)
  4. Qualitative & comparative-historical transparency
  5. Restricted data (exemption / access path)
  6. Pre-analysis plan
  7. Anti-patterns
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
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.

Keep going