Agent skill · Data & Analytics

jpart-transparency-and-data

Use when preparing the data and replication materials for a Journal of Public Administration Research and Theory (JPART) manuscript. JPART requires authors, where ethically possible, to publicly release all data and software code as a condition of publication, with a mandatory Data Availability Statement. Prepares the package; it does not waive requirements.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-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: 5 KB
Bundled scripts: none
Path: Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-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 Policy (jpart-transparency-and-data) JPART does not merely encourage sharing — it **requires** authors, *where ethically possible*, to **publicly release all data and software code underlying the published paper as a condition of publication**, and every paper must carry a **Data Availability Statement**. Build the package as you go so acceptance does not stall on materials. ## When to trigger - Building the reproducibility/replication package and the Data Availability Statement - A manuscript is heading toward acceptance and you need materials in shareable form - Data cannot be fully shared (privacy, ethics, legal/provider restrictions) and you need the exemption path - Preparing or linking a **preregistration / pre-analysis plan** (JPART accepts blinded pre-reg reports) ## What JPART requires (verify current wording on the policy page) 1. **Public release of data and code.** As a condition of publication, release the data and the software code that produced the results — in a trusted, citable public repository with a persistent identifier (e.g., a Dataverse or OSF deposit), not a personal website or transient cloud link. 2. **Data Availability Statement.** A

What's inside
Steps it walks through
  1. When to trigger
  2. What JPART requires (verify current wording on the policy page)
  3. When data cannot be shared (exemption path)
  4. Build-as-you-go checklist
  5. Anti-patterns
  6. Output format
  7. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpart-transparency-and-data skill do?

Use when preparing the data and replication materials for a Journal of Public Administration Research and Theory (JPART) manuscript. JPART requires authors, where ethically possible, to publicly release all data and software code as a condition of publication, with a mandatory 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 jpart-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