Agent skill · Data & Analytics

epsl-reporting-and-reproducibility

Use when assembling the supplementary material, data-availability statement, and FAIR data deposit for an Earth and Planetary Science Letters (EPSL) manuscript. EPSL follows Elsevier's research-data policies and the community expects deposition in discipline repositories — EarthChem, PANGAEA, IRIS/EarthScope, MagIC, NASA PDS, Zenodo. It guides reporting and deposit; it does not generate the data.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-reporting-and-reproducibility --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Earth-and-Planetary-Science-Letters-Skills/skills/epsl-reporting-and-reproducibility/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

# Reporting & Reproducibility (epsl-reporting-and-reproducibility) The letters format pushes almost everything load-bearing but non-narrative — full analytical tables, method details, standards data, model configurations — into the supplement and the repositories. That makes the supplement and deposit *part of the reviewed science*, not an afterthought. EPSL sits inside Elsevier's research-data framework (data statements, repository linking), and its communities run mature FAIR infrastructure; reviewers know the canonical archive for each data type and notice absences. Re-check the current mandate wording on the official Guide for Authors. ## When to trigger - Assembling supplementary text, tables, and figures - Writing the data-availability statement and choosing repositories - Depositing geochemical tables, waveforms, paleomagnetic data, model code, or mission-derived products - Making sure a reader could re-derive every figure and headline number ## What to build 1. **A methods supplement that stands alone.** Instrumentation, chemistry/procedures, standards with measured-vs-accepted values, blank records, correction sequence, and reduction software with versions — enough that a

What's inside
Steps it walks through
  1. When to trigger
  2. What to build
  3. Deposition routing: data type → community repository
  4. Referee-pushback patterns and the venue-specific fix
  5. Anti-patterns
  6. Output format
  7. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the epsl-reporting-and-reproducibility skill do?

Use when assembling the supplementary material, data-availability statement, and FAIR data deposit for an Earth and Planetary Science Letters (EPSL) manuscript. EPSL follows Elsevier's research-data policies and the community expects deposition in discipline repositories — EarthChem, PANGAEA, IRIS/EarthScope, MagIC, NASA PDS, Zenodo. It guides reporting and deposit; it does not generate the data.

How do I install it?

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