Agent skill · Code Review & Quality

jleo-referee-strategy

Use when anticipating the referee read on a Journal of Law, Economics, and Organization (JLEO) manuscript before submitting — modeling the institutional/organizational economist who will review it and pre-empting the objections that sink JLEO papers. Anticipates objections; it does not write the response to an actual report (jleo-rebuttal).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jleo-referee-strategy --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-referee-strategy/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

# Referee Strategy (jleo-referee-strategy) ## When to trigger - The paper is near submission and you want to see it through a JLEO referee's eyes first - You suspect a credibility gap (selection into governance, reform endogeneity, a decorative model) that a referee will find - The contribution is real but might read as "applied micro with institutional labels" to a TCE/PPE reviewer - You need to decide which weaknesses to fix now versus flag transparently in the cover letter - The paper sits near a sibling boundary and a referee might say "this belongs at JLE / Org Science" ## Who reviews at JLEO and what they look for JLEO referees are drawn from the institutional and organizational economics and PPE communities — people fluent in transaction-cost economics, contract theory, and the political economy of institutions. They are unusually attentive to two things generic economics referees are not: (1) whether the **institutional mechanism** is real and named, and (2) whether the empirical object — usually *chosen* by the agents — is credibly identified despite that choice. Model the reviewer, then pre-empt. ## The objections that recur at JLEO | Likely referee objection | Pre-empt b

What's inside
Steps it walks through
  1. When to trigger
  2. Who reviews at JLEO and what they look for
  3. The objections that recur at JLEO
  4. Strategy moves
  5. Checklist
  6. Anti-patterns
  7. Worked vignette (illustrative)
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jleo-referee-strategy skill do?

Use when anticipating the referee read on a Journal of Law, Economics, and Organization (JLEO) manuscript before submitting — modeling the institutional/organizational economist who will review it and pre-empting the objections that sink JLEO papers. Anticipates objections; it does not write the response to an actual report (jleo-rebuttal).

How do I install it?

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