Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation…
Install Nsdi Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-workflow .claude/skills/nsdi-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 "nsdi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-workflow into .claude/skills/nsdi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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/NSDI-Skills/skills/nsdi-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 nsdi-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-workflow .agents/skills/nsdi-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 "nsdi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-workflow into .agents/skills/nsdi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-workflow .cursor/skills/nsdi-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 "nsdi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-workflow into .cursor/skills/nsdi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 NSDI-Skills/skills/nsdi-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 nsdi-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-workflow .gemini/skills/nsdi-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 "nsdi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-workflow into .gemini/skills/nsdi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-workflow .github/skills/nsdi-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 "nsdi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-workflow into .github/skills/nsdi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-workflow .opencode/skills/nsdi-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 "nsdi-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-workflow into .opencode/skills/nsdi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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
nsdi-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 764 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation…
- Works in 4 steps: Within a week: map every required issue… → Reserve infrastructure immediately for… → Maintain the change-highlighted PDF and… → …
- Planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates
- SKILL.md covers The '27 clock, One project, four legal paths…, Working backward from a gate and The waits, and what to do…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nsdi Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.
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 Research & Science. 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
- Planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates
- Notification waits
- One-shot revision windows
- Artifact evaluation
Example prompts
- “/nsdi-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Within a week: map every required issue to an owner and a cost (new experiment,
- Reserve infrastructure immediately for any issue needing measurements.
- Maintain the change-highlighted PDF and the change-summary memo as you go — both
- Freeze two weeks before the gate; a revision that misses its window or dodges an
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
Nsdi Workflow loads about 1.6k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 764 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). 764 words, ~1,585 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-workflow/SKILL.md (or your agent's skills folder).- name
- nsdi-workflow
- description
- Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.
NSDI Workflow
NSDI is a calendar problem disguised as a conference. One edition, two submission
gates, two decision cohorts, and a revision mechanism that spans deadlines — a team
that plans "for NSDI" without naming the gate usually discovers it planned for
neither. Dates below are the NSDI '27 cycle as rendered on 2026-07-08; treat them as
this cycle's snapshot and re-pull the HotCRP /deadlines pages before acting.
The '27 clock
| Gate | Date (11:59 pm US EDT) | Cohort |
|---|---|---|
| Spring abstracts | April 16, 2026 | spring |
| Spring full papers | April 23, 2026 | spring |
| Spring notification | July 23, 2026 | spring |
| Fall abstracts | September 10, 2026 | fall |
| Fall full papers | September 17, 2026 | fall |
| Fall notification | December 8, 2026 | fall |
| Symposium | May 11-13, 2027, Providence, RI | both |
Where "today" (2026-07-08) sits: spring authors are two weeks from notification; a fresh submission has nine weeks to the fall abstract gate. Camera-ready dates and the '27 artifact schedule were not yet rendered — 待核实, watch the conference page.
One project, four legal paths through the cycle
Path A fall '26 submit -> accept (Dec 8) -> final paper + AE -> present May '27
Path B fall '26 submit -> one-shot revision -> resubmit spring '27 (next edition)
Path C fall '26 submit -> reject -> BARRED from spring '27; rework for fall '27
Path D spring '26 one-shot revision (notif Jul 23) -> revise -> fall '26 resubmitPath C is the one teams forget: a plain rejection carries a one-deadline ban, so the cheapest-looking option — "just submit and see" — silently spends two deadlines, not one. Build the decision into the plan: submit only when the evidence would survive review, otherwise hold for the next gate and use the time on the testbed.
Working backward from a gate
A fall-2026 target, walked backward:
- T-9 to T-6 weeks: freeze the design; the evaluation plan (workloads, baselines,
scale points) written down and reviewed as if it were the paper
(
nsdi-experiments). Trace collection and testbed reservations start now — cluster time is the resource that cannot be compressed in deadline week. - T-6 to T-3: experiments run continuously with provenance capture
(
nsdi-reproducibility); the paper skeleton fills section by section (nsdi-writing-style); related-work sweep across both NSDI cohort lists of the current edition (nsdi-related-work). - T-2: full internal read against the 12-page budget; appendix triage
(
nsdi-supplementary). - T-1 week (Sept 10): abstract, authors, track, and conflicts registered on the fall HotCRP site. The abstract gate is a hard prerequisite, not a formality.
- T-0 (Sept 17): final PDF through the submission audit (
nsdi-submission), uploaded and marked complete with hours to spare.
The waits, and what to do inside them
NSDI's review silences are long (spring: April to late July; fall: September to early December). Productive uses that pay off regardless of outcome:
- Harden the artifact toward badge evaluation — the accept-case deliverable
(
nsdi-artifact-evaluation), and the Community Award requires public code/data by the final-papers deadline. - Keep the testbed alive and re-runnable; a one-shot revision letter often demands new experiments on a 3-4 month fuse, and a decommissioned cluster turns a feasible revision into a forfeit.
- Draft the extension or the next paper; do not submit the same work elsewhere — concurrent submission violates USENIX policy.
Show full SKILL.md (302 more words)Show less
Revision-window management (path B/D)
A one-shot revision arrives with a reviewer-authored list of required issues and a deadline implied by the next submission gate. Run it as a mini-project:
- Within a week: map every required issue to an owner and a cost (new experiment, new analysis, rewrite).
- Reserve infrastructure immediately for any issue needing measurements.
- Maintain the change-highlighted PDF and the change-summary memo as you go — both
are mandatory auxiliary material at resubmission (
nsdi-author-response). - Freeze two weeks before the gate; a revision that misses its window or dodges an issue is rejected with no further revision option.
Choosing between the gates when both are open
Early in a cycle, spring-vs-fall is a real decision, not a default:
- Spring favors projects whose evaluation is already running: an accept yields ten months of artifact and presentation runway, and even a one-shot revision recycles into the same edition's fall gate (path D) — the gentlest failure mode NSDI offers.
- Fall favors projects still building: five more months of testbed time, at the cost of a compressed post-accept pipeline and a revision that lands in the next edition.
- Never split one paper across both by submitting a weak spring version as a placeholder — the rejection ban (path C) converts that hedge into exclusion from the very fall gate the team was counting on.
Standing risks with named owners
- Gate confusion — someone plans for "the NSDI deadline" without saying which. Owner: project lead; fix: every milestone names spring/fall + year.
- Time-zone drift — '27 uses US EDT where '26 used PDT; a reused conversion table is an hour-scale landmine. Owner: submitter of record.
- Cap collisions — eight submissions per author per edition across both deadlines; large groups reconcile author lists before each abstract gate. Owner: most-senior common author.
- Infrastructure decay during waits. Owner: artifact lead.
Output format
[Target gate] spring / fall + year (papers due <date>)
[Today's position] weeks to next gate; cohort status of any pending submission
[Backward plan] milestone -> week -> owner
[Ban check] any cohort-ban or revision window constraining this plan?
[Wait-time tasks] artifact / testbed / next-paper assignments
[Top schedule risk] <one item + mitigation>© 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 NSDI-Skills/skills/nsdi-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi 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 |
|---|---|---|---|---|---|---|
| Nsdi Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Nsdi Workflow
What does Nsdi Workflow do?
A skill your agent uses when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation…. Nsdi Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.
When should I use Nsdi Workflow?
Nsdi Workflow fits situations like: planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates; notification waits; one-shot revision windows; artifact evaluation.
How do I install Nsdi Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-workflow -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-workflow -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-workflow in your project. Codex loads it when a task matches its description.
Can I use Nsdi 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 nsdi-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/nsdi-workflow, .gemini/skills/nsdi-workflow, .github/skills/nsdi-workflow and .opencode/skills/nsdi-workflow in your project.
What does Nsdi Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Nsdi Workflow is instructions for the agent only.
Does Nsdi 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 Nsdi 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 Nsdi Workflow use?
Nsdi 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 Nsdi Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Nsdi Workflow?
Skills that share tags, products or a category with Nsdi Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi 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.