Matplotlib
zLanqing/codex-claude-academic-skills
Low-level plotting library for full customization. An agent skill from zLanqing/codex-claude-academic-skills.
A skill your agent uses 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…
Install Epsl Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-review-process --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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process .claude/skills/epsl-review-process && 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 "epsl-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process into .claude/skills/epsl-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-review-process", 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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-processType 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 epsl-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-review-process --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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process .agents/skills/epsl-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "epsl-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process into .agents/skills/epsl-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-review-process", 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 epsl-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-review-process --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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process .cursor/skills/epsl-review-process && 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 "epsl-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process into .cursor/skills/epsl-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-review-process", 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 Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process--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 epsl-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-review-process --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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process .gemini/skills/epsl-review-process && 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 "epsl-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process into .gemini/skills/epsl-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-review-process", 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 epsl-review-processInstalls 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 epsl-review-process -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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process .github/skills/epsl-review-process && 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 "epsl-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process into .github/skills/epsl-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-review-process", 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 epsl-review-process -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 epsl-review-process --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/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process .opencode/skills/epsl-review-process && 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 "epsl-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process into .opencode/skills/epsl-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-review-process", 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
epsl-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 582 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Works in 5 steps: Subject-editor triage. The handling… → Referees drawn from the paper's… → Editor-led decisions. The handling… → …
- Expert review typically drawn from the sub-fields the paper joins
- SKILL.md covers When to trigger, How EPSL review works, Desk-decline grounds and where… and What each referee audits, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Epsl Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.4k 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 Data & Analytics. 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
- Expert review typically drawn from the sub-fields the paper joins
- Editor-led decisions
Example prompts
- “/epsl-review-process”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Subject-editor triage. The handling editor — a researcher in the paper's area — judges frontier
- Referees drawn from the paper's intersection. A manuscript joining geochemistry and
- Editor-led decisions. The handling editor weighs the reviews and decides — reject, major or
- Comments and Replies. EPSL carries formal Comment/Reply exchanges on published papers; they are
- Integrity screening. Plagiarism checks, authorship and competing-interest declarations, and
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
Epsl Review Process loads about 1.4k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 582 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). 582 words, ~1,397 tokens.
Download SKILL.mdSave it as
.claude/skills/epsl-review-process/SKILL.md (or your agent's skills folder).- name
- epsl-review-process
- description
- 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.
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
- 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.
- Referees drawn from the paper's intersection. A manuscript joining geochemistry and geodynamics is typically reviewed by at least one specialist from each side; each referee audits their own layer (traceability and statistics vs physical plausibility and resolution).
- Editor-led decisions. The handling editor weighs the reviews and decides — reject, major or minor revision, or acceptance; reviews advise, the editor adjudicates.
- Comments and Replies. EPSL carries formal Comment/Reply exchanges on published papers; they are held to the same evidence standard as Letters and are not a venue for tone.
- Integrity screening. Plagiarism checks, authorship and competing-interest declarations, and Elsevier's publishing-ethics framework apply at submission.
Desk-decline grounds and where they get fixed upstream
| Desk-decline ground | What the editor read | Fix it in |
|---|---|---|
| Regional study, no process takeaway | place-name title, local conclusions | epsl-topic-selection |
| Incremental / does not move the frontier | gap framed as "more data needed" | epsl-literature-positioning |
| Not letters-shaped | sprawling scope, companion manuscript | epsl-workflow, epsl-writing-style |
| Better suited to a specialist journal | method-community audience only | epsl-topic-selection |
| Over length / format non-compliant | cap exceeded, missing statements | epsl-submission |
Show full SKILL.md (244 more words)Show less
What each referee audits
| Referee | Reads first | Rejects on |
|---|---|---|
| The analyst (geochem/geochron) | standards, blanks, σ-definitions, MSWD | untraceable numbers |
| The physicist (geophys/geodyn) | resolution tests, force balance, scaling | interpreting artifacts |
| The recorder (strat/paleo) | age control, correlation logic | rates without anchors |
| The planetary scientist | data provenance (mission/archive), assumed parameters | overreach beyond sensitivity |
Worked micro-example (illustrative — forecasting the decision on the slab-fluid paper)
Stress-testing the B-isotope + tomography Letter before submission (illustrative reasoning):
- Desk axes: process-level (how slabs lose water) — passes; letters-shaped (one claim, 6,100 words) — passes; portability argued in the abstract — passes.
- Geochemist referee: will probe the δ11B external reproducibility and crustal-assimilation screen — both pre-empted in the supplement.
- Seismologist referee: will ask whether the conduit survives the resolution test — the inset in Figure 1c exists precisely for this.
- Realistic outcome: major revision asking for an alternative-fluid-pathway discussion and one more sensitivity case. Budget for it; "major revision" at a high-bar venue is an invitation to convince, not a near-accept.
The discipline: walk the desk axes and both referees' audits yourself, in writing, before the editor does.
Anti-patterns
- Submitting a locally-framed paper and hoping the editor generalizes it for you
- Preparing for one referee's specialty when the paper straddles two
- Reading "major revision" as acceptance-with-chores
- Responding to a Comment with rhetoric instead of data
- Assuming timelines, reviewer counts, or editor assignments that the official page does not state
Output format
【Desk screen】process-level? letters-shaped? portable? [Y/N each]
【Predicted referees】sub-fields + what each will audit
【Pre-empted objections】list, with manuscript location
【Weakest layer】named honestly + mitigation
【Realistic outcome】reject / major / minor
【Next】epsl-submission (or epsl-revision-and-rebuttal on a decision)Supplementary resources
../../resources/official-source-map.md— editorial structure and policy links (re-check volatile items)../../resources/exemplars/library.md— papers that survived this gauntlet, by sub-field
© 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 Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Epsl Review Process 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 |
|---|---|---|---|---|---|---|
| Epsl Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| MatplotlibzLanqing/codex-claude-academic-skills | 4.7k | 17 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Exploratory Data Analysisspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Scikit LearnzLanqing/codex-claude-academic-skills | 4.7k | 16 repos | ~3.9k | Automated safety check: Pass | BSD-3-Clause | |
| Chart Visualizationbytedance/deer-flow | 84k | 1 repos | ~840 | Automated safety check: Pass | MIT | |
| TimesFM Forecastinggoogle-research/timesfm | 34k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Exploratory Data Analysis
spacering-net/codeg
Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.
Scikit Learn
zLanqing/codex-claude-academic-skills
Machine learning in Python with scikit-learn. An agent skill from zLanqing/codex-claude-academic-skills.
Chart Visualization
bytedance/deer-flow
Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.
TimesFM Forecasting
google-research/timesfm
Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.
- Official
Sandbox Bench
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
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 Epsl Review Process
What does Epsl Review Process do?
A skill your agent uses 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…. Epsl Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Epsl Review Process?
Epsl Review Process fits situations like: expert review typically drawn from the sub-fields the paper joins; editor-led decisions.
How do I install Epsl Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-review-process -a claude-code`. Or copy the skill folder (Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/epsl-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Epsl Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-review-process -a codex`. Or copy the skill folder (Earth-and-Planetary-Science-Letters-Skills/skills/epsl-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/epsl-review-process in your project. Codex loads it when a task matches its description.
Can I use Epsl Review Process 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 epsl-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/epsl-review-process, .gemini/skills/epsl-review-process, .github/skills/epsl-review-process and .opencode/skills/epsl-review-process in your project.
What does Epsl Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Epsl Review Process is instructions for the agent only.
Does Epsl Review Process 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 Epsl Review Process 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 Epsl Review Process use?
Epsl Review Process 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 Epsl Review Process use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Epsl Review Process?
Skills that share tags, products or a category with Epsl Review Process: Matplotlib (zLanqing/codex-claude-academic-skills, 4.7k stars), Exploratory Data Analysis (spacering-net/codeg, 3.9k stars), Scikit Learn (zLanqing/codex-claude-academic-skills, 4.7k stars) and Chart Visualization (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Epsl Review Process?
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.