Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
A skill your agent uses when responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility, balance, length, and framing — on an invited or accepted article.
Install Jep Revision
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-revision -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-revision --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-revision .claude/skills/jep-revision && 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-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-revision into .claude/skills/jep-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-revision", 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-revisionType 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-revision -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-revision --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-revision .agents/skills/jep-revision && 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-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-revision into .agents/skills/jep-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-revision", 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-revision -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-revision --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-revision .cursor/skills/jep-revision && 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-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-revision into .cursor/skills/jep-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-revision", 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-revision--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-revision -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-revision --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-revision .gemini/skills/jep-revision && 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-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-revision into .gemini/skills/jep-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-revision", 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-revisionInstalls 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-revision -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-revision .github/skills/jep-revision && 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-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-revision into .github/skills/jep-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-revision", 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-revision -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-revision --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-revision .opencode/skills/jep-revision && 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-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-revision into .opencode/skills/jep-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-revision", 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-revision- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 473 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility, balance, length, and framing — on an invited or accepted article.
- Responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility
- SKILL.md covers When to trigger, How JEP revision differs, Triaging the editor's letter and Building the revision, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Framing — on an invited
What it does
Jep Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Accessibility. 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
- Responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility
- Framing — on an invited
- Accepted article
Example prompts
- “/jep-revision”
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 Revision loads about 1.1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 473 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). 473 words, ~1,128 tokens.
Download SKILL.mdSave it as
.claude/skills/jep-revision/SKILL.md (or your agent's skills folder).- name
- jep-revision
- description
- 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.
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" | competing views or uncertainty underplayed | jep-balance-and-objectivity |
| "We lose the thread / what's the argument?" | structure is a survey, no through-line | jep-narrative-arc |
| "Too long / cut to length" | exhaustive coverage, not a focused essay | jep-editor-strategy (cut coverage, keep clarity) |
| "Tighten the prose / abstract" | voice dull; abstract has machinery | jep-writing-style |
| "Exhibits are dense" | research-paper figures/tables | jep-exhibits-for-general-readers |
Building the revision
- Take accessibility and balance notes as binding. These are JEP's core; argue only if a change would make the piece wrong, and then propose an accessible alternative, not a refusal.
- Cut coverage before clarity. When trimming length, remove exhaustiveness and tangents; protect the through-line, the load-bearing examples, and the few essential exhibits.
- Preserve honesty under pressure to simplify. If an edit risks overstating a finding, flag it and offer wording that stays accurate (cross-check
jep-balance-and-objectivityandjep-evidence-without-equations). - Keep the symposium frame if applicable — don't expand into a companion piece's territory while revising.
Show full SKILL.md (171 more words)Show less
The reply letter (to the editorial team)
- Short, point-by-point, and warm. Map each editorial comment to what you changed and where.
- Lead with agreement. Note the edits you simply made; reserve discussion for the few you handled differently, with a brief reason and an accessible alternative.
- No referee-style combativeness. This is a collaborative edit, not an adversarial rebuttal.
Checklist
- Each editor comment mapped to a concrete change and location
- Accessibility and balance edits treated as binding (alternatives, not refusals)
- Length cuts removed coverage, not the through-line or key exhibits
- No simplification silently overstated a result
- Symposium scope respected (if applicable)
- Reply letter is short, point-by-point, collaborative
Anti-patterns
- Replying to a hands-on editor as if rebutting an anonymous referee
- Resisting accessibility edits ("the experts need this") instead of finding an accessible version
- Cutting clarity (examples, the argument's spine) to hit a length target while keeping exhaustive coverage
- Letting a "make it punchier" edit push the claims past what the evidence supports
- A long, defensive reply letter that re-litigates settled calls
Output format
【Letter type】editor/managing-editor edits (not anonymous referees)
【Top concerns】accessibility / balance / framing / length / prose / exhibits
【Per-comment plan】comment → change → location
【Binding edits done】[accessibility + balance items]
【Length plan】cut coverage; protect through-line + key exhibits
【Honesty check】no edit overstated a finding? [Y/N]
【Reply letter】short, point-by-point, collaborative? [Y/N]
【Next step】return to jep-workflow if a new bottleneck surfaces© 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-revision of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jep Revision 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 Revision this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.6k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
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…
Related
Categories
Questions about Jep Revision
What does Jep Revision do?
A skill your agent uses when responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility, balance, length, and framing — on an invited or accepted article. Jep Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility, balance, length, and framing — on an invited or accepted article.
When should I use Jep Revision?
Jep Revision fits situations like: responding to Journal of Economic Perspectives (JEP) editor feedback — accessibility; framing — on an invited; accepted article.
How do I install Jep Revision in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-revision -a claude-code`. Or copy the skill folder (Journal-of-Economic-Perspectives-Skills/skills/jep-revision in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jep-revision in your project. Claude Code loads it when a task matches its description.
How do I install Jep Revision in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-revision -a codex`. Or copy the skill folder (Journal-of-Economic-Perspectives-Skills/skills/jep-revision in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jep-revision in your project. Codex loads it when a task matches its description.
Can I use Jep Revision 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-revision -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-revision, .gemini/skills/jep-revision, .github/skills/jep-revision and .opencode/skills/jep-revision in your project.
What does Jep Revision need to run?
SKILL.md names no scripts, command-line tools or credentials: Jep Revision is instructions for the agent only.
Does Jep Revision 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 Revision 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 Revision use?
Jep Revision 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 Revision use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Revision?
Skills that share tags, products or a category with Jep Revision: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jep Revision?
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.