Agent skill · Data & Analytics

jleo-replication-package

Use when assembling the data and code replication package for a Journal of Law, Economics, and Organization (JLEO) manuscript — building reproducible paths from institutional/organizational/political data sources (court records, contracts, legislative data, firm-boundary data) to every exhibit. Builds the package; it does not run new analysis.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jleo-replication-package --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: Journal-of-Law-Economics-and-Organization-Skills/skills/jleo-replication-package/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

# Replication Package (jleo-replication-package) ## When to trigger - A coauthor or referee needs to reproduce every table and figure from raw institutional data - The paper relies on hand-collected institutional data (court records, contracts, legislative votes, agency rulings) whose construction is undocumented - Some institutional data are proprietary or confidential (firm contracts, sealed court records) and access terms must be stated - The code runs on one machine but the path from raw source to final exhibit is not reproducible - You need a Data Availability Statement and a README before submitting or at the revision stage ## Reproducibility for institutional data JLEO is an OUP economics journal; OUP and COPE expect transparency, and the field increasingly expects a working replication package even where OUP does not run a dedicated data-editor check (verify the current JLEO data-and-code policy on the official OUP page — 待核实). The distinctive challenge at JLEO is that the data are often **institutional artifacts** — court dockets, procurement contracts, committee assignments, constitutional provisions — that require careful, documented construction from primary sources. Bu

What's inside
Steps it walks through
  1. When to trigger
  2. Reproducibility for institutional data
  3. Build the package
  4. Checklist
  5. Anti-patterns
  6. Worked vignette (illustrative)
  7. Referee / editor concern mapped to the package fix
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jleo-replication-package skill do?

Use when assembling the data and code replication package for a Journal of Law, Economics, and Organization (JLEO) manuscript — building reproducible paths from institutional/organizational/political data sources (court records, contracts, legislative data, firm-boundary data) to every exhibit. Builds the package; it does not run new analysis.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jleo-replication-package --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