Editorial Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…
A skill your agent uses when working with the Journal of Economic Perspectives (JEP) editorial team — the managing-editor-led model and the symposium structure — on scope, length, framing, and the…
MITAuto-check passed
Install Jep Editor Strategy
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-editor-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy .claude/skills/jep-editor-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jep-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy into .claude/skills/jep-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-editor-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-editor-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy .agents/skills/jep-editor-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jep-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy into .agents/skills/jep-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-editor-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-editor-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy .cursor/skills/jep-editor-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jep-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy into .cursor/skills/jep-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-editor-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-editor-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy .gemini/skills/jep-editor-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jep-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy into .gemini/skills/jep-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-editor-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-editor-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy .github/skills/jep-editor-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jep-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy into .github/skills/jep-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-editor-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-editor-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy .opencode/skills/jep-editor-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jep-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy into .opencode/skills/jep-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-editor-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jep-editor-strategy- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 720 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when working with the Journal of Economic Perspectives (JEP) editorial team — the managing-editor-led model and the symposium structure — on scope, length, framing, and the…
- The invited/commissioned process
- SKILL.md covers When to trigger, The JEP editorial model, Working with the team and Scope & length negotiation, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jep Editor Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when working with the Journal of Economic Perspectives (JEP) editorial team — the managing-editor-led model and the symposium structure — on scope, length, framing, and the invited/commissioned process. Handles editor interaction strategy; defer the final submission preflight to jep-submission and post-decision edits to jep-revision.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- The invited/commissioned process
Example prompts
- “/jep-editor-strategy”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jep Editor Strategy loads about 1.5k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 720 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 720 words, ~1,477 tokens.
Download SKILL.mdSave it as
.claude/skills/jep-editor-strategy/SKILL.md (or your agent's skills folder).- name
- jep-editor-strategy
- description
- Use when working with the Journal of Economic Perspectives (JEP) editorial team — the managing-editor-led model and the symposium structure — on scope, length, framing, and the invited/commissioned process. Handles editor interaction strategy; defer the final submission preflight to jep-submission and post-decision edits to jep-revision.
Editor Strategy (jep-editor-strategy)
When to trigger
- An editor invited you and you need to understand the working relationship
- Your article is part of a symposium and you must fit a shared frame and length
- Scope or length is in tension with what the editors want
- You are unsure how JEP's editor-driven, hands-on process differs from a refereed journal
The JEP editorial model
JEP is run by an editorial team led by editors and a long-serving managing editor, and is largely invited / commissioned (检索于 2026-06；以官网为准). As of 2026 (editor roster re-verified 2026-06-22 against the AEA "Editors of the Journal of Economic Perspectives" page) the Editor is Heidi Williams (Dartmouth); coeditors include Jeffrey Kling and Jonathan Parker (MIT); the Managing Editor is Timothy Taylor (long-tenured), with an assistant managing editor — re-confirm the roster on the official editors page before relying on names. Unlike a refereed research journal, JEP review is editor-driven and hands-on: the editors actively shape framing, accessibility, and length, often across several rounds, rather than dispatching to anonymous referees. Expect direct, substantive editorial guidance and a strong house preference for readability.
Working with the team
- Treat the proposal as the contract. The invited scope, angle, and length agreed at the proposal stage (
jep-proposal-and-symposium) define the assignment; large drifts need editor sign-off. - Expect accessibility-first edits. The managing editor and editors push hard on plain language and structure; arrive having already done
jep-accessibility-and-translationandjep-narrative-arc. - Negotiate scope early, not late. If the topic needs more or less room, raise it before drafting, not after. Editors would rather reshape a proposal than a finished draft.
- Respect the symposium frame. In a symposium, the editors set the unifying question and your assigned angle; stay in your lane and gesture to companion pieces rather than re-covering them.
- Use the managing editor as your accessibility coach. Timothy Taylor's long-running role is, in effect, the guardian of readability; treat marked-up plain-language edits as the house standard, not as personal style preference.
- Be responsive and concise in correspondence. A hands-on editorial team values authors who turn edits quickly and don't re-litigate settled accessibility calls.
Scope & length negotiation
- JEP has no hard public word limit, but the house norm is a focused, accessible essay — shorter and tighter than a JEL survey (检索于 2026-06；以官网为准). Argue scope in terms of what the broad reader needs, not what the literature contains.
- If asked to cut, cut coverage (exhaustiveness) before clarity (the through-line, examples, exhibits that carry the argument).
- If asked to broaden, add reach and stakes for non-specialists, not more specialist detail.
- Defer to editorial judgment on framing for the broad audience: the editors read JEP's readership daily and know what lands. Bring your expertise on the substance; trust them on the translation and on placement within an issue or symposium.
Show full SKILL.md (261 more words)Show less
Checklist
- Understood the invited scope/angle/length as the working contract
- Confirmed current editor/managing-editor roster on the official page
- Did accessibility + narrative work before sending the editors a draft
- Brought substance expertise; deferred to the team on broad-audience framing
- Raised any scope/length tension early
- In a symposium: stayed within the assigned angle; coordinated with the frame
- Prepared to turn editorial edits quickly and concisely
Worked vignette (illustrative)
An invited author drafts a piece that has grown to JEL length because they tried to cover every paper in the field. The managing editor writes back: "This is more comprehensive than our readers need — make it an argument, not a census." The fix is not to defend the coverage but to return to jep-narrative-arc, pick the through-line, cut the exhaustive sections to a sentence each with a pointer to further reading, and protect the examples and exhibits that carry the argument. The reply to the editor is short: which sections were compressed, which were cut, and how the through-line is now visible by page two.
Anti-patterns
- Treating a JEP editor like a referee — waiting passively instead of engaging the hands-on process
- Drifting far from the agreed proposal scope without sign-off
- Sending a still-technical draft and expecting the editors to do the translation
- Re-litigating accessibility edits the editors have settled
- In a symposium, expanding to cover ground assigned to a companion article
- Padding to JEL length when the editors want a tight, broad-audience essay
- Surfacing a major scope or framing change only after the full draft is written, when it is hardest to absorb
Output format
【Process】invited/commissioned; editor-driven, hands-on (not anonymous referees)
【Editor / managing editor】confirmed on official page? [Y/N] (Williams / Taylor as of 2026-06)
【Working contract】scope / angle / length agreed: [...]
【Symposium frame (if any)】assigned angle: [...]
【Scope/length plan】cut coverage before clarity / add reach not detail
【Open tensions raised early?】scope / framing flagged before full draft? [Y/N]
【Readiness】accessibility + narrative done before editor sees draft? [Y/N]
【Next step】jep-submission© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jep Editor Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jep Editor Strategy this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Editorial Policythedaviddias/Front-End-Checklist | 74k | — | ~763 | Automated safety check: Pass | MIT | |
| Economic Perspectivesfranklee16/academic-research-skills | 223 | 1 repos | ~543 | Automated safety check: Pass | None | |
| Editorial Designsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Journal Of Economic Perspectivesfranklee16/academic-research-skills | 223 | 1 repos | ~1.5k | Automated safety check: Pass | None | |
| After Hours Editorial Templatenexu-io/open-design | 100k | — | ~607 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Economic Perspectives
franklee16/academic-research-skills
A skill your agent uses when targeting 《经济学动态》(Economic Perspectives — 中国社会科学院主管、经济研究所主办的理论经济学月刊, 1960 年创刊, CSSCI) or deciding whether a Chinese econ manuscript fits this venue.
Editorial Design
sickn33/agentic-awesome-skills
Web and App implementation guide for Editorial Design. An agent skill from sickn33/agentic-awesome-skills.
Journal Of Economic Perspectives
franklee16/academic-research-skills
A skill your agent uses when targeting Journal of Economic Perspectives (JEP) or deciding whether an accessible symposium-style article fits this venue.
After Hours Editorial Template
nexu-io/open-design
Luxury dark-editorial HyperFrames template for three-page cinematic storyboards, inspired by haute couture title cards and magazine chapter spreads.
Editorial
bergside/awesome-design-skills
Magazine-inspired editorial layout with refined serif typography, structured grids, and elegant reading experiences.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Jep Editor Strategy
What does Jep Editor Strategy do?
A skill your agent uses when working with the Journal of Economic Perspectives (JEP) editorial team — the managing-editor-led model and the symposium structure — on scope, length, framing, and the…. Jep Editor Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when working with the Journal of Economic Perspectives (JEP) editorial team — the managing-editor-led model and the symposium structure — on scope, length, framing, and the invited/commissioned process.
When should I use Jep Editor Strategy?
Jep Editor Strategy fits situations like: the invited/commissioned process.
How do I install Jep Editor Strategy in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a claude-code`. Or copy the skill folder (Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jep-editor-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Jep Editor Strategy in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a codex`. Or copy the skill folder (Journal-of-Economic-Perspectives-Skills/skills/jep-editor-strategy in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jep-editor-strategy in your project. Codex loads it when a task matches its description.
Can I use Jep Editor Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-editor-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jep-editor-strategy, .gemini/skills/jep-editor-strategy, .github/skills/jep-editor-strategy and .opencode/skills/jep-editor-strategy in your project.
What does Jep Editor Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Jep Editor Strategy is instructions for the agent only.
Does Jep Editor Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Jep Editor Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jep Editor Strategy use?
Jep Editor Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Jep Editor Strategy use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jep Editor Strategy?
Skills that share tags, products or a category with Jep Editor Strategy: Editorial Policy (thedaviddias/Front-End-Checklist, 74k stars), Economic Perspectives (franklee16/academic-research-skills, 223 stars), Editorial Design (sickn33/agentic-awesome-skills, 47k stars) and Journal Of Economic Perspectives (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jep Editor Strategy?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.