Reactive Resume Builder
reactive-resume/reactive-resume
Builds resumes as valid JSON for the open-source Reactive Resume app by interviewing you, and can track job applications through its MCP tools.
A skill your agent uses when starting or resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point.
MITAuto-check passed
Install Epsl Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-workflow --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-workflow .claude/skills/epsl-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow into .claude/skills/epsl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-workflow --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-workflow .agents/skills/epsl-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow into .agents/skills/epsl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-workflow --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-workflow .cursor/skills/epsl-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow into .cursor/skills/epsl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills epsl-workflow --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-workflow .gemini/skills/epsl-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow into .gemini/skills/epsl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/epsl-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow into .github/skills/epsl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/epsl-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow into .opencode/skills/epsl-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "epsl-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 565 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when starting or resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point.
- Works in 5 steps: Frontier check → epsl-topic-selection:… → Positioning →… → Design/analysis loop → epsl-study-design… → …
- Resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point
- SKILL.md covers When to trigger, First question: is this a…, Routing map (stage → skill) and Default order, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Epsl Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when starting or resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point. Routes to the right EPSL sub-skill based on lifecycle stage and on whether the work matches the letters format (a concise, high-significance Letter; an invited Frontiers Paper; or a Comment/Reply). It dispatches; it does not draft content.
Its SKILL.md is about 1.6k 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
- Resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point
Example prompts
- “/epsl-workflow”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Frontier check → epsl-topic-selection: the claim generalizes (how water leaves slabs), so it
- Positioning → epsl-literature-positioning: the gap must engage geochemists and
- Design/analysis loop → epsl-study-design ↔ epsl-data-analysis: reference materials, blanks,
- Exhibits + deposit → epsl-figures-and-tables, epsl-reporting-and-reproducibility: one
- Write → pitch → submit → epsl-writing-style → epsl-cover-letter → epsl-submission.
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 Workflow loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 565 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). 565 words, ~1,597 tokens.
Download SKILL.mdSave it as
.claude/skills/epsl-workflow/SKILL.md (or your agent's skills folder).- name
- epsl-workflow
- description
- Use when starting or resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point. Routes to the right EPSL sub-skill based on lifecycle stage and on whether the work matches the letters format (a concise, high-significance Letter; an invited Frontiers Paper; or a Comment/Reply). It dispatches; it does not draft content.
EPSL Workflow Router (epsl-workflow)
The dispatcher for an EPSL submission. EPSL is Elsevier's flagship letters journal for solid-Earth and planetary science (founded 1966, ISSN 0012-821X): it wants a concise Letter carrying one decisive, process-level advance about the physical, chemical or mechanical workings of the Earth or another planet. The router's first job is therefore double: locate the stage, and confirm the result is a Letter — not a data report, not a regional case study, not two papers stapled together.
When to trigger
- Starting an EPSL manuscript and unsure where to begin
- Mid-project and unsure which skill applies next
- Unsure whether the work is letters-shaped or belongs at a specialist journal
- Returning with a decision letter (route to
epsl-revision-and-rebuttal)
First question: is this a Letter?
| Situation | Verdict | Route to |
|---|---|---|
| One decisive advance on a process of Earth/planetary interiors, surfaces, or atmospheres | Letter — proceed | pipeline below |
| Solid dataset, insight local to one region or one analyte | not yet letters-shaped | epsl-topic-selection to reframe or redirect |
| Two intertwined results needing two manuscripts | companion papers are discouraged at EPSL | merge to one Letter or split venues |
| Field-wide synthesis | Frontiers Paper — by editor invitation only | do not self-select; query first |
| Dispute with a published EPSL paper | Comment / Reply | epsl-review-process for etiquette |
Length is policed: the main text (introduction through conclusions) is capped near 6,500 words — re-check the exact figure on the official Guide for Authors before trusting it.
Routing map (stage → skill)
Does the idea clear the frontier bar? → epsl-topic-selection
Which literatures must the gap engage? → epsl-literature-positioning
Will the sampling/analytical plan hold? → epsl-study-design
Are uncertainties fully propagated? → epsl-data-analysis
Do the exhibits work for four sub-fields? → epsl-figures-and-tables
Data deposited FAIR, methods transparent? → epsl-reporting-and-reproducibility
Does it read like a Letter? → epsl-writing-style
Pitching the handling editor? → epsl-cover-letter
How will it be judged? → epsl-review-process
Ready for Editorial Manager? → epsl-submission
Decision letter arrived? → epsl-revision-and-rebuttalDefault order
topic-selection → literature-positioning → study-design → data-analysis → figures-and-tables → reporting-and-reproducibility → writing-style → cover-letter → review-process → submission → revision-and-rebuttal
Expect loops: geochronology and isotope work cycles design ↔ analysis until the uncertainty budget closes; modeling work cycles design ↔ figures until the resolution tests convince.
Symptom → skill quick-routing
| User says | Underlying EPSL risk | Route to |
|---|---|---|
| "Is this significant enough for EPSL?" | frontier-vs-incremental desk screen | epsl-topic-selection |
| "The editor called it a regional study" | no process-level takeaway | epsl-topic-selection, epsl-literature-positioning |
| "Reviewer wants the full error budget" | analytical-transparency gap | epsl-data-analysis |
| "Where do I put 400 zircon analyses?" | data table belongs in repository/supplement | epsl-reporting-and-reproducibility |
| "I'm 2,000 words over" | letters-format cap | epsl-writing-style |
| "Which repository counts as FAIR?" | data-availability mandate | epsl-reporting-and-reproducibility |
| "Got a major revision" | rebuttal strategy | epsl-revision-and-rebuttal |
Show full SKILL.md (216 more words)Show less
Worked micro-example (illustrative — routing a subduction-zone water paper)
A user arrives: "I have B isotopes and seismic velocities suggesting slab fluids reach the deep arc — where do I start?" The router's pass (illustrative):
- Frontier check →
epsl-topic-selection: the claim generalizes (how water leaves slabs), so it clears the process bar; confirm Letter shape, one advance. - Positioning →
epsl-literature-positioning: the gap must engage geochemists and seismologists, or one of the two reviewers will call it naive. - Design/analysis loop →
epsl-study-design↔epsl-data-analysis: reference materials, blanks, 2σ external reproducibility, and the velocity-model resolution test. - Exhibits + deposit →
epsl-figures-and-tables,epsl-reporting-and-reproducibility: one cross-section figure carrying the argument; data to EarthChem, waveform products via IRIS/EarthScope. - Write → pitch → submit →
epsl-writing-style→epsl-cover-letter→epsl-submission.
The router's standing job: surface the two gates the editors weigh first — process-level significance and analytical transparency — before any prose is written.
Anti-patterns
- Treating EPSL as a general geoscience outlet — a sound regional dataset with no process insight is the classic desk decline
- Planning companion papers; EPSL explicitly discourages them
- Self-selecting "Frontiers Paper" without an editor's invitation
- Discovering the ~6,500-word main-text cap after the draft is 9,000 words
- Leaving data deposition and the methods supplement until submission week
Output format
【Stage】idea / positioning / design / analysis / exhibits / reproducibility / writing / cover-letter / review / submit / revise
【Format check】Letter / invited Frontiers / Comment-Reply / not letters-shaped
【Route to】epsl-<skill>
【Why】one line
【Then】the next skill after thatSupplementary resources
../../resources/external_tools.md— geochemistry, geophysics, and geochronology tooling by sub-field../../resources/official-source-map.md— official Elsevier/EPSL URLs behind every fact in this pack
© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Epsl Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Reactive Resume Builderreactive-resume/reactive-resume | 44k | — | ~1.5k | Automated safety check: Pass | MIT | |
| StartDonchitos/Claude-Code-Game-Studios | 26k | — | ~6.5k | Automated safety check: Pass | MIT | |
| Resume Version Managerdavila7/claude-code-templates | 32k | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Resume Modernnexu-io/open-design | 100k | — | ~398 | Automated safety check: Pass | Apache-2.0 | |
| Tech Resume Optimizerdavila7/claude-code-templates | 32k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Start
Donchitos/Claude-Code-Game-Studios
First-time onboarding — asks where you are, then guides you to the right workflow.
Resume Version Manager
davila7/claude-code-templates
Track different resume versions, maintain a master resume, and manage tailored variants.
Resume Modern
nexu-io/open-design
Modern minimal resume, single A4 page, ready for print or PDF export.
Tech Resume Optimizer
davila7/claude-code-templates
Optimize resumes for software engineering, product management, and technical roles.
Resume Tailor
davila7/claude-code-templates
Customize resume for specific job postings while maintaining truthfulness.
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 Epsl Workflow
What does Epsl Workflow do?
A skill your agent uses when starting or resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point. Epsl Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when starting or resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point.
When should I use Epsl Workflow?
Epsl Workflow fits situations like: resuming any Earth and Planetary Science Letters (EPSL) manuscript and you need the entry point.
How do I install Epsl Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-workflow -a claude-code`. Or copy the skill folder (Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/epsl-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Epsl Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill epsl-workflow -a codex`. Or copy the skill folder (Earth-and-Planetary-Science-Letters-Skills/skills/epsl-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/epsl-workflow in your project. Codex loads it when a task matches its description.
Can I use Epsl Workflow 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-workflow -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-workflow, .gemini/skills/epsl-workflow, .github/skills/epsl-workflow and .opencode/skills/epsl-workflow in your project.
What does Epsl Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Epsl Workflow is instructions for the agent only.
Does Epsl Workflow 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 Workflow 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 Workflow use?
Epsl Workflow 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 Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Workflow?
Skills that share tags, products or a category with Epsl Workflow: Reactive Resume Builder (reactive-resume/reactive-resume, 44k stars), Start (Donchitos/Claude-Code-Game-Studios, 26k stars), Resume Version Manager (davila7/claude-code-templates, 32k stars) and Resume Modern (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Epsl Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.