Career-Ops Job Search Center
career-ops-hq/career-ops
Routes job-search requests to modes for evaluating offers, scanning portals, generating tailored CVs, tracking applications and drafting outreach, starting from a pasted job URL or description.
A skill your agent uses when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5…
Install Fcr Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-submission --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/Field-Crops-Research-Skills/skills/fcr-submission .claude/skills/fcr-submission && 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 "fcr-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-submission into .claude/skills/fcr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-submission", 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/Field-Crops-Research-Skills/skills/fcr-submissionType 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 fcr-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-submission --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/Field-Crops-Research-Skills/skills/fcr-submission .agents/skills/fcr-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fcr-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-submission into .agents/skills/fcr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-submission", 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 fcr-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-submission --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/Field-Crops-Research-Skills/skills/fcr-submission .cursor/skills/fcr-submission && 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 "fcr-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-submission into .cursor/skills/fcr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-submission", 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 Field-Crops-Research-Skills/skills/fcr-submission--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 fcr-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-submission --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/Field-Crops-Research-Skills/skills/fcr-submission .gemini/skills/fcr-submission && 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 "fcr-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-submission into .gemini/skills/fcr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-submission", 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 fcr-submissionInstalls 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 fcr-submission -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/Field-Crops-Research-Skills/skills/fcr-submission .github/skills/fcr-submission && 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 "fcr-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-submission into .github/skills/fcr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-submission", 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 fcr-submission -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 fcr-submission --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/Field-Crops-Research-Skills/skills/fcr-submission .opencode/skills/fcr-submission && 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 "fcr-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-submission into .opencode/skills/fcr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-submission", 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
fcr-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 635 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5…
- Running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection
- SKILL.md covers When to trigger, Process facts, Preflight checklist and Highlights bench-test…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Abstract (<=400 words) and highlights (3-5 bullets of <=85 characters)
What it does
Fcr Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter. Final checks; 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.
It sits in Business, Finance & HR, covering Resume and CV writing. 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
- Running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection
- Abstract (<=400 words) and highlights (3-5 bullets of <=85 characters)
- Complete agronomic reporting
- Data-availability statement
Example prompts
- “/fcr-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
Fcr Submission loads about 1.6k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 635 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). 635 words, ~1,617 tokens.
Download SKILL.mdSave it as
.claude/skills/fcr-submission/SKILL.md (or your agent's skills folder).- name
- fcr-submission
- description
- Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter. Final checks; it does not draft content.
Submission Preflight (fcr-submission)
The last check before pressing submit on Editorial Manager at submit.elsevier.com/FIELD. FCR's
most common avoidable failures are scope mismatch and incomplete reporting / declarations. Check
upload-week specifics on the official Elsevier guide before relying on editor names, prices, file
prompts, or article-type menus (see ../../resources/official-source-map.md).
When to trigger
- "Submitting tomorrow" — last pass before upload
- Unsure which files/metadata Editorial Manager expects
- Confirming scope fit, format, and declarations are complete
Process facts
- Publisher: Elsevier (ISSN 0378-4290).
- Portal: Editorial Manager at
submit.elsevier.com/FIELD. - Review model: single anonymized — typically ≥ 2 reviewers.
- Article types: Original Research Paper · Short Communication · Review (usually invited) · Opinion Paper · Loomis Review (invited).
- Abstract: ≤ 400 words.
- Highlights: 3–5 bullets, each ≤ 85 characters including spaces.
- Multi-environment rule: field experiments should span ≥ 2 seasons and/or multiple environments (unless exceptional circumstances are justified).
- Data availability: must be stated at submission.
- Generative AI: declare any use in manuscript preparation.
Preflight checklist
Scope & type
- Field-based, multi-season/-environment, a field crop, generally significant (see
fcr-topic-selection) - Article type chosen; Review/Opinion proposal cleared with editors if required
Manuscript & format
- Abstract ≤ 400 words; states purpose, environments, quantitative result, conclusion
- 3–5 highlights, each ≤ 85 characters, findings not topics
- Structure: focused intro → complete methods → concise results → interpretive discussion
- SI units; consistent Elsevier/FCR reference style; grammatically sound English
- Figures/tables self-contained with units and SED/LSD/CI (see
fcr-figures-and-tables)
Reporting completeness
- Crop/cultivar, sites/seasons, soil, weather vs. phenology, management, design, statistics
- Yield data included/linked to biophysical process where relevant
Declarations & files
- Data-availability statement drafted (shared + repository/ID, or restricted + reason)
- Generative-AI use declared; CRediT roles, funding, competing interests
- Cover letter establishing scope fit + contribution (see
fcr-cover-letter) - Co-submission to Data in Brief / MethodsX considered if relevant
Highlights bench-test (illustrative)
Highlights are findings, not topics, and the ≤85-character limit counts spaces. Bench-test each bullet.
| Draft highlight | Chars | Verdict |
|---|---|---|
| "Effects of nitrogen on wheat yield and quality" | 47 | reject — a topic, not a finding |
| "New cultivar raised yield 0.9 t/ha in high-N environments only" | 62 | keep — quantified |
| "G×E explained 38% of yield variance across 8 site-years" | 56 | keep — names the result |
Worked preflight vignette (illustrative)
Illustrative dry-run. A maize MET manuscript reaches the final pass: 2 seasons × 4 sites, abstract at 410 words, 6 highlights, a plot-level dataset, but no weather-vs-phenology figure. The preflight catches four blockers: trim the abstract under the 400-word cap; cut highlights to 5 and rewrite topic-style bullets as findings; add the weather-vs-phenology panel so the G×E is interpretable; and draft the data-availability statement to the Mendeley Data DOI. Scope and statistics pass, so once fixed the package is ready for Editorial Manager.
Show full SKILL.md (219 more words)Show less
Anti-patterns
- Submitting controlled-environment-only or single-site/single-season work
- Abstract over length; highlights that are topics or exceed 85 characters
- Methods missing soil/weather-vs-phenology/management (not reproducible)
- Blank data-availability statement; missing generative-AI declaration
- A discussion that repeats results; means with no error term
Operating pass for Field Crops Research
Treat this skill as an executable review pass, not a prose hint. First lock the crop system, environment structure, GxE logic, and yield or physiology endpoint; then judge whether the current manuscript answers the venue's real reader: agronomy reviewers who expect field-based, multi-environment evidence and crop-level general significance.
- Do the pass: Return a claim-evidence-risk ledger rather than a prose-only diagnosis; every recommendation must point to a manuscript location or missing artifact.
- Return a ledger: give
claim / evidence / risk / manuscript locationrows, so the next agent can edit rather than rediscover the issue. - Sibling guard: compare against Agricultural Systems for whole-system modeling, European Journal of Agronomy for agronomic breadth, Crop Science for cultivar or breeding emphasis; if a sibling owns the contribution, recommend re-routing before polishing format.
- Submission-ready gate: do not give final advice until the pack's
resources/official-source-map.mdhas been checked for upload-week rules and the manuscript has one concrete fix for the largest venue-specific risk.
Output format
【Scope & type】field-based + ≥2 seasons/envs + field crop + general; type chosen? [Y/N]
【Abstract & highlights】≤400 words; 3-5 bullets ≤85 chars? [Y/N]
【Reporting complete】cultivar/site/soil/weather-vs-phenology/management/design/stats? [Y/N]
【Declarations】data availability + generative-AI + CRediT/funding? [Y/N]
【Cover letter】scope fit + contribution stated? [Y/N]
【Next】await decision → fcr-revision-and-rebuttal on a revise verdictSupplementary resources
../../resources/external_tools.md— reference managers and Elsevier typesetting/templates../../resources/official-source-map.md— official FCR 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 Field-Crops-Research-Skills/skills/fcr-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fcr Submission 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 |
|---|---|---|---|---|---|---|
| Fcr Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Career-Ops Job Search Centercareer-ops-hq/career-ops | 74k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Reactive Resume Builderreactive-resume/reactive-resume | 44k | — | ~2k | Automated safety check: Pass | MIT | |
| Internship Project Preparation ToolLiuMengxuan04/shushu-internship-tool | 2.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Resume Tailoringvarunr89/resume-tailoring-skill | 769 | 1 repos | ~8.9k | Automated safety check: Pass | MIT | |
| Offer Negotiationreactive-resume/reactive-resume | 44k | — | ~10k | Automated safety check: Pass | MIT |
Similar skills
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.
Internship Project Preparation Tool
LiuMengxuan04/shushu-internship-tool
Turns a target internship job description into a resume-ready, interview-ready project by finding and auditing GitHub projects and drafting resume bullets and interview Q&A.
Resume Tailoring
varunr89/resume-tailoring-skill
A skill your agent uses when creating tailored resumes for job applications - researches company/role, creates optimized templates, conducts branching experience discovery to surface undocumented…
Offer Negotiation
reactive-resume/reactive-resume
Evaluates and negotiates job offers. An agent skill from reactive-resume/reactive-resume.
Good Story
Rimagination/good-story
A skill your agent uses when the user asks to find, sharpen, evaluate, rewrite, or explain the story in scientific or scholarly materials across disciplines, including manuscripts, grants, paper…
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 Fcr Submission
What does Fcr Submission do?
A skill your agent uses when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5…. Fcr Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter.
When should I use Fcr Submission?
Fcr Submission fits situations like: running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection; abstract (<=400 words) and highlights (3-5 bullets of <=85 characters); complete agronomic reporting; data-availability statement.
How do I install Fcr Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-submission -a claude-code`. Or copy the skill folder (Field-Crops-Research-Skills/skills/fcr-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fcr-submission in your project. Claude Code loads it when a task matches its description.
How do I install Fcr Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-submission -a codex`. Or copy the skill folder (Field-Crops-Research-Skills/skills/fcr-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fcr-submission in your project. Codex loads it when a task matches its description.
Can I use Fcr Submission 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 fcr-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fcr-submission, .gemini/skills/fcr-submission, .github/skills/fcr-submission and .opencode/skills/fcr-submission in your project.
What does Fcr Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Fcr Submission is instructions for the agent only.
Does Fcr Submission 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 Fcr Submission 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 Fcr Submission use?
Fcr Submission 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 Fcr Submission use?
About 1.6k tokens (SKILL.md is roughly 6.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 Fcr Submission?
Skills that share tags, products or a category with Fcr Submission: Career-Ops Job Search Center (career-ops-hq/career-ops, 74k stars), Reactive Resume Builder (reactive-resume/reactive-resume, 44k stars), Internship Project Preparation Tool (LiuMengxuan04/shushu-internship-tool, 2.1k stars) and Resume Tailoring (varunr89/resume-tailoring-skill, 769 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fcr Submission?
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.