Agent skill

jep-revision

Use when responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility, balance, length, and framing — on an invited or accepted article. Plans the revision and the reply to the editorial team; it does not draft the original article or run the submission preflight.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-revision --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: Journal-of-Economic-Perspectives-Skills/skills/jep-revision/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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

# Revision (jep-revision) ## When to trigger - A JEP editor's letter arrived asking for changes (not an anonymous referee report) - The edits center on accessibility, balance, framing, or length — the JEP levers - The managing editor returned a heavily marked-up draft - You need to plan the revision and a concise reply to the editorial team ## How JEP revision differs JEP review is **editor-driven and hands-on**, so revision is a **conversation with the editors and managing editor**, not a rebuttal to hidden referees. The edits will almost always be about *how the piece communicates* — is it accessible enough, balanced enough, well-framed, and the right length — rather than new identification or robustness. The right posture is **responsive and collaborative**: the editors are protecting the broad-audience mission, and on accessibility calls they are usually right. ## Triaging the editor's letter | Editor concern | What it usually means | The fix (skill) | |----------------|-----------------------|-----------------| | "Still too technical / for specialists" | jargon/notation/assumed knowledge remains | `jep-accessibility-and-translation` | | "Reads as advocacy / one-sided" | compet

What's inside
Steps it walks through
  1. When to trigger
  2. How JEP revision differs
  3. Triaging the editor's letter
  4. Building the revision
  5. The reply letter (to the editorial team)
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jep-revision skill do?

Use when responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility, balance, length, and framing — on an invited or accepted article. Plans the revision and the reply to the editorial team; it does not draft the original article or run the submission preflight.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-revision --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 984 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