Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column…
Install Stoc Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-submission .claude/skills/stoc-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 "stoc-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-submission into .claude/skills/stoc-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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/STOC-Skills/skills/stoc-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 stoc-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-submission .agents/skills/stoc-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 "stoc-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-submission into .agents/skills/stoc-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-submission .cursor/skills/stoc-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 "stoc-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-submission into .cursor/skills/stoc-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 STOC-Skills/skills/stoc-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 stoc-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-submission .gemini/skills/stoc-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 "stoc-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-submission into .gemini/skills/stoc-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-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 stoc-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/STOC-Skills/skills/stoc-submission .github/skills/stoc-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 "stoc-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-submission into .github/skills/stoc-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-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 stoc-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/STOC-Skills/skills/stoc-submission .opencode/skills/stoc-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 "stoc-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-submission into .opencode/skills/stoc-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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
stoc-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 799 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column…
- Works in 6 steps: Freeze all theorem statements and check… → Rebuild the table of contents so section… → Run the anonymity sweep: names,… → …
- Single-column 11-point format
- SKILL.md covers The reading contract, not a…, Format floor (2026 wording), Anonymity, new to the house… and SIGACT…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Stoc Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column 11-point format, double-blind hygiene, the SIGACT prior/simultaneous-publication policy, and deadline-week sequencing before the November cutoff.
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
- Single-column 11-point format
- Double-blind hygiene
- The SIGACT prior/simultaneous-publication policy
- Deadline-week sequencing before the November cutoff
Example prompts
- “/stoc-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze all theorem statements and check each appears within pages 1–12.
- Rebuild the table of contents so section titles narrate the proof strategy.
- Run the anonymity sweep: names, acknowledgements, self-references, metadata.
- Verify the abstract in HotCRP matches the PDF abstract exactly.
- If the cycle offers the opt-in automated pre-submission feedback experiment
- Upload a day ahead; the deadline is a US-Eastern clock time, not AoE.
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 (its code samples are latex).
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
Stoc Submission loads about 1.6k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 799 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). 799 words, ~1,625 tokens.
Download SKILL.mdSave it as
.claude/skills/stoc-submission/SKILL.md (or your agent's skills folder).- name
- stoc-submission
- description
- Use when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column 11-point format, double-blind hygiene, the SIGACT prior/simultaneous-publication policy, and deadline-week sequencing before the November cutoff.
STOC Submission
Run this audit before uploading to the STOC HotCRP site. Anchor cycle: STOC 2026
(58th ACM Symposium on Theory of Computing), whose CFP set the paper deadline at
Tuesday, November 4, 2025, 4:59pm EST, with no separate abstract-registration step
(checked 2026-07-08 at acm-stoc.org/stoc2026/stoc2026-cfp.html). Reopen the live
CFP for the cycle you are actually targeting before trusting any number below.
The reading contract, not a page limit
STOC does not cap submission length. Instead, the 2026 CFP guaranteed committee attention only to the abstract, the table of contents, and the first twelve pages; everything after that is read at the committee's discretion. That is a contract about where your persuasion must happen, and it has three consequences:
- Every theorem you want credit for must be stated inside the first twelve pages, even if its proof lives at page 40.
- The table of contents is a reviewed object. A submission without one, or with one that does not reveal the proof architecture, wastes a guaranteed-read surface.
- Proofs beyond page twelve are a courtesy to the diligent reviewer, not a substitute for a convincing overview inside the guaranteed pages.
Format floor (2026 wording)
Typeset in 11-point or larger font, single-column, single-spaced with generous spacing, 1-inch margins on letter-size paper. There is no mandatory class file in the STOC submission stage — this is looser than ACM camera-ready format, and authors coming from two-column ML venues routinely misjudge how few words twelve single-column pages hold. A minimal compliant preamble:
\documentclass[11pt,letterpaper]{article}
\usepackage[margin=1in]{geometry}
\usepackage{amsmath,amsthm,amssymb}
\usepackage[numbers]{natbib}
% Double-blind: no \author block, no acknowledgements, no grant numbers.
\title{Your Title}
\author{}
\date{}Anonymity, new to the house tradition
STOC 2026 used double-blind reviewing: the submission must not reveal author identity in any way. Because the venue only recently moved away from non-anonymous submissions (the exact first double-blind edition: 待核实), older lab templates and habits are the main leak source. Sweep for:
- self-citations phrased as "our earlier paper" instead of third person;
- the full version already on arXiv under your names — posting is generally compatible with theory double-blind norms, but confirm the current CFP's stance before citing your own preprint in a de-anonymizing way (待核实 per cycle);
- PDF metadata (
pdfinfo paper.pdf), acknowledgements, and grant lines.
SIGACT prior/simultaneous-publication policy
The 2026 CFP applied SIGACT's standing rule: work already published, or scheduled to appear before the conference (for STOC 2026: prior to July 2026), in another conference proceedings or a journal is ineligible, and simultaneous submission to such venues is barred. The stated exception is publication in Science or Nature. arXiv and ECCC preprints do not count as prior publication.
Desk-risk and damage triage
| Finding at upload time | Consequence at STOC | Can it be repaired after the deadline? |
|---|---|---|
| Main theorem stated only after page 12 | Committee may never register the result | No — the guaranteed-read window is fixed |
| Author-identifying text or metadata | Violates the double-blind instruction; chair action | No |
| Simultaneous submission to SODA/FOCS/a journal | Policy violation; rejection at both ends | No |
| Missing table of contents | Loses a guaranteed-read surface; sloppy signal | No |
| Font/margin shrinking to fake density | Read as circumventing the reading contract | No |
| Overloaded notation, no overview section | Survives, but converts reviewers to skeptics | Only before the deadline |
Show full SKILL.md (290 more words)Show less
Deadline-week sequence
- Freeze all theorem statements and check each appears within pages 1–12.
- Rebuild the table of contents so section titles narrate the proof strategy.
- Run the anonymity sweep: names, acknowledgements, self-references, metadata.
- Verify the abstract in HotCRP matches the PDF abstract exactly.
- If the cycle offers the opt-in automated pre-submission feedback experiment (STOC 2026 ran a Gemini-based rigor check, full paper due November 1, 5pm EST, output visible to authors only), decide deliberately — it needs the paper essentially done three days early.
- Upload a day ahead; the deadline is a US-Eastern clock time, not AoE.
What the portal itself will ask
Beyond the PDF, the HotCRP form has its own fields, and mismatches between form and PDF are chair-visible:
- Title and abstract entered on the form must match the PDF; the form abstract is what PC members read while bidding, so it does the first-impression work.
- Topic selections drive assignment — choose the sub-areas whose reviewers you actually want, not every box that vaguely applies.
- Conflicts of interest against PC members must be complete and honest; under-declaring is an integrity problem, over-declaring shrinks your qualified-reviewer pool.
- Author list and order are entered even though reviewers cannot see them; fix them now, since changing authorship post-acceptance needs chair approval.
Habits from other venues that break here
| Imported habit | Why it fails at STOC |
|---|---|
| Two-column conference template | Wrong format; the submission stage wants loose single-column 11-point |
| Deferring all proofs to a "supplementary file" | No such channel exists; one PDF carries everything |
| Waiting for the rebuttal to clarify | There is no rebuttal (stoc-author-response) |
| AoE mental arithmetic | The deadline is US-Eastern wall-clock time |
| "Abstract deadline first, paper later" | 2026 had a single deadline; no placeholder week |
Output format
[STOC readiness] Ready / Needs fixes / Not ready
[Guaranteed-read audit] <theorems or claims currently outside abstract/ToC/first 12 pages>
[Anonymity findings] <leaks discovered>
[Policy findings] <prior/simultaneous-publication conflicts>
[Fix order] <ordered actions before the November deadline>© 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 STOC-Skills/skills/stoc-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Stoc 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 |
|---|---|---|---|---|---|---|
| Stoc Submission 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 | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.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.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 Stoc Submission
What does Stoc Submission do?
A skill your agent uses when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column…. Stoc Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a STOC (ACM Symposium on Theory of Computing) submission for HotCRP readiness — the abstract + table-of-contents + first-12-pages reading rule, single-column 11-point format, double-blind hygiene, the SIGACT prior/simultaneous-publication policy, and deadline-week sequencing before the November cutoff.
When should I use Stoc Submission?
Stoc Submission fits situations like: single-column 11-point format; double-blind hygiene; the SIGACT prior/simultaneous-publication policy; deadline-week sequencing before the November cutoff.
How do I install Stoc Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-submission -a claude-code`. Or copy the skill folder (STOC-Skills/skills/stoc-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/stoc-submission in your project. Claude Code loads it when a task matches its description.
How do I install Stoc Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-submission -a codex`. Or copy the skill folder (STOC-Skills/skills/stoc-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/stoc-submission in your project. Codex loads it when a task matches its description.
Can I use Stoc 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 stoc-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/stoc-submission, .gemini/skills/stoc-submission, .github/skills/stoc-submission and .opencode/skills/stoc-submission in your project.
What does Stoc Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Stoc Submission is instructions for the agent only.
Does Stoc 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 Stoc 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 Stoc Submission use?
Stoc 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 Stoc 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 Stoc Submission?
Skills that share tags, products or a category with Stoc Submission: 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 Stoc 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.