Agent skill · Design & Presentation

jep-accessibility-and-translation

Use when translating technical results, models, and methods into plain language for a Journal of Economic Perspectives (JEP) article — minimizing jargon and notation without dumbing down. Handles language and translation of ideas; defer evidence/number presentation to jep-evidence-without-equations and exhibits to jep-exhibits-for-general-readers.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-accessibility-and-translation --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-Economic-Perspectives-Skills/skills/jep-accessibility-and-translation/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

# Accessibility & Translation (jep-accessibility-and-translation) ## When to trigger - The draft reads like a working paper with the proofs deleted - A labor or macro economist who doesn't work on the topic gets lost - Sentences carry notation, estimator names, or subfield jargon a generalist won't know - You worry that simplifying will make the piece sound shallow ## The JEP accessibility bar JEP articles should be readable by **90 percent or more of the AEA membership** and useful to economists **not conversant with the author's subspecialty**; the journal is "scholarly without relying too heavily on mathematical notation," explaining ideas through **economic intuition** rather than derivations (检索于 2026-06;以官网为准). Translation is **not** simplification of the *ideas* — it is removing the *barriers* (notation, jargon, insider shorthand) that hide the ideas from a smart non-specialist. ## Translation moves (technical → JEP) | Technical draft | JEP move | |-----------------|----------| | An estimating equation in the body | State what the equation *says* in words; the design goes to a note or appendix if at all | | "We instrument X with Z" | "We exploit [the natural experiment] so t

What's inside
Steps it walks through
  1. When to trigger
  2. The JEP accessibility bar
  3. Translation moves (technical → JEP)
  4. Principles
  5. Calibrating depth (not dumbing down)
  6. Checklist
  7. Worked vignette (illustrative)
  8. Anti-patterns
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jep-accessibility-and-translation skill do?

Use when translating technical results, models, and methods into plain language for a Journal of Economic Perspectives (JEP) article — minimizing jargon and notation without dumbing down. Handles language and translation of ideas; defer evidence/number presentation to jep-evidence-without-equations and exhibits to jep-exhibits-for-general-readers.

How do I install it?

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