Agent skill · Code Review & Quality

epsl-review-process

Use when you need to understand how Earth and Planetary Science Letters (EPSL) evaluates a manuscript — subject-editor desk screening against the frontier bar, expert review typically drawn from the sub-fields the paper joins, and editor-led decisions. It sets expectations and hardens the paper before submission; it does not contact editors.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-review-process --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: Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process/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

# Review Process (epsl-review-process) EPSL's review is run by working scientists: a team of editors, each handling manuscripts near their own specialty, screening first for whether the paper is a genuine Letter — concise, decisive, of broad Earth-and-planets interest — before sending it to expert referees. Knowing the two-gate structure (desk screen on significance and fit, then technical review on rigor) lets you harden the paper against each gate in advance. Volatile details (editor names, reviewer counts, timelines) drift; re-check them on the official site. ## When to trigger - Pre-submission stress test against the desk-screen and reviewer axes - Interpreting a decision letter and planning the response strategy - Anticipating which sub-fields the referees will come from - Considering a Comment on a published EPSL paper, or facing one ## How EPSL review works 1. **Subject-editor triage.** The handling editor — a researcher in the paper's area — judges frontier significance, letters fit, and scope. Regional case studies without process-level insight, method reports, and incremental additions to settled questions are declined here, without external review. 2. **Referees drawn fr

What's inside
Steps it walks through
  1. When to trigger
  2. How EPSL review works
  3. Desk-decline grounds and where they get fixed upstream
  4. What each referee audits
  5. Anti-patterns
  6. Output format
  7. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the epsl-review-process skill do?

Use when you need to understand how Earth and Planetary Science Letters (EPSL) evaluates a manuscript — subject-editor desk screening against the frontier bar, expert review typically drawn from the sub-fields the paper joins, and editor-led decisions. It sets expectations and hardens the paper before submission; it does not contact editors.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-review-process --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