Experiment Plan
appleweiping/WEIPING_WIKI
Rigorous experiment planning that produces a complete, auditable experiment plan with blocks, baselines, milestones, decision gates, and compute estimates.
A skill your agent uses when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year…
Install Stoc Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-workflow .claude/skills/stoc-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 "stoc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-workflow into .claude/skills/stoc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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/STOC-Skills/skills/stoc-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 stoc-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-workflow .agents/skills/stoc-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 "stoc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-workflow into .agents/skills/stoc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-workflow .cursor/skills/stoc-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 "stoc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-workflow into .cursor/skills/stoc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 STOC-Skills/skills/stoc-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 stoc-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-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/STOC-Skills/skills/stoc-workflow .gemini/skills/stoc-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 "stoc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-workflow into .gemini/skills/stoc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-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 stoc-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/STOC-Skills/skills/stoc-workflow .github/skills/stoc-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 "stoc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-workflow into .github/skills/stoc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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 stoc-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 stoc-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/STOC-Skills/skills/stoc-workflow .opencode/skills/stoc-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 "stoc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-workflow into .opencode/skills/stoc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-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
stoc-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 765 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year…
- Works in 4 steps: Triage the corrections file into… → Hit both March 31 deliverables: the ACM… → Prepare the TheoryFest talk: one… → …
- Planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline
- SKILL.md covers The two-beat theory year, Backward plan to a November…, Between submission and… and From acceptance to Salt Lake…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Stoc Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.
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 Product & Project Management, covering Project management. 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 a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline
- The STOC/FOCS alternating two-deadline year that theory groups schedule around
- Full-version and camera-ready milestones
- The June TheoryFest endpoint
Example prompts
- “/stoc-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Triage the corrections file into camera-ready fixes vs. full-version-only
- Hit both March 31 deliverables: the ACM proceedings version and the public
- Prepare the TheoryFest talk: one theorem, one technique, one open problem;
- Confirm registration and attendance obligations from the acceptance email
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
Stoc Workflow loads about 1.6k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 765 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). 765 words, ~1,629 tokens.
Download SKILL.mdSave it as
.claude/skills/stoc-workflow/SKILL.md (or your agent's skills folder).- name
- stoc-workflow
- description
- Use when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.
STOC Workflow
STOC is a conference with per-edition leadership, not a journal: SIGACT appoints
a fresh program committee and chair every year (STOC 2026: PC chair Artur
Czumaj; verified 2026-07-08 via the CFP), there is no standing editor, and
publication costs ride on conference registration rather than author fees.
Anchor timeline, 2026 cycle: submissions November 4, 2025 (4:59pm EST);
notification by February 1, 2026; camera-ready and public full version March 31,
2026 (AoE); conference June 22–26, 2026, Salt Lake City, inside a five/six-day
TheoryFest program. Every date below is that cycle's snapshot — reopen
acm-stoc.org for the live year before acting on any of them.
The two-beat theory year
The field's real planning unit is not one deadline but the STOC/FOCS pair: STOC submissions close in early November for a June conference; FOCS closes in early April for a fall conference (FOCS 2026: deadline April 1, 2026, 21:00 UTC; conference November 8–11, 2026, New York — verified 2026-07-08). The same community, largely overlapping reviewer pools, near-identical scope. Strategic consequences:
| Situation in late October | Sound play |
|---|---|
| Result complete, writing strong | Submit to STOC |
| Proof complete, writing weak | Submit only if the overview can be made honest in time; a rushed overview at a no-rebuttal venue is unrecoverable |
| One lemma still open | Hold for FOCS in April; five months closes lemmas |
| STOC rejection arrives Feb 1 | Two months to repair for FOCS — enough for presentation surgery, rarely enough for new mathematics |
| Result claimed by concurrent preprint | Post to arXiv immediately for priority, then decide venue calmly |
A result that misses both beats simply waits; nothing in theory culture penalizes a strong paper for arriving one cycle later, but plenty penalizes a broken proof for arriving on time.
Backward plan to a November deadline
- T−16 weeks: the mathematical result exists in believed-complete form. Everything after this is verification and writing; theorem-proving scheduled inside the writing window is the classic failure.
- T−12 weeks: full proofs written out (full-version draft), not just notes. Writing proofs is verification at this venue; gaps surface only under the discipline of complete prose.
- T−8 weeks: internal verification pass — each theorem checked by a
coauthor who did not draft its proof (
stoc-reproducibility's workflow). - T−6 weeks: extract the extended abstract from the full version: choose
the twelve-page story, write the technical overview (
stoc-writing-style). - T−3 weeks: hostile-read by a colleague outside the sub-area; their confusion map drives the final overview rewrite.
- T−1 week: literature re-sweep (arXiv/ECCC), objection-ledger check
(
stoc-author-response), anonymity sweep and HotCRP dry run (stoc-submission). If opting into a pre-submission feedback experiment (2026: full paper due ~3 days early), the paper must be done here. - T: upload with hours to spare; the deadline is a US-Eastern wall-clock time, not AoE, and this catches Europeans annually.
Show full SKILL.md (313 more words)Show less
Between submission and decision (Nov–Feb)
- Post or refresh the arXiv/ECCC version if the cycle's double-blind rules permit (待核实 — check the live CFP's stance on preprints during review).
- Keep a corrections file: any bug or improvement found post-submission goes in it, dated. If a chair-mediated query arrives, answers come from this file; if acceptance arrives, it becomes the camera-ready worklist.
- Do not silently rewrite the posted preprint mid-review in ways that diverge from the submitted PDF; reviewers may be reading both.
From acceptance to Salt Lake City (Feb–Jun)
- Triage the corrections file into camera-ready fixes vs. full-version-only
improvements (
stoc-camera-ready). - Hit both March 31 deliverables: the ACM proceedings version and the public full version with complete proofs — the CFP treats the second as an expectation of acceptance, not a courtesy.
- Prepare the TheoryFest talk: one theorem, one technique, one open problem; rehearse to the announced slot length. Poster/workshop add-ons follow the program announcement (待核实 per cycle).
- Confirm registration and attendance obligations from the acceptance email (待核实; not stated in the CFP excerpts verified for this pack).
The cycle at a glance (2026 snapshot)
2025-11-01 optional LLM-feedback upload (experiment; 3 days early)
2025-11-04 STOC deadline, 4:59pm EST
2026-02-01 decisions out (at the latest)
2026-02..03 accepted: corrections triage, ACM reformat, talk draft
rejected: repair memo -> FOCS decision point
2026-03-31 camera-ready (AoE) + full version live on arXiv/ECCC
2026-04-01 FOCS 2026 deadline, 21:00 UTC (the other beat)
2026-06-22 STOC / TheoryFest week opens, Salt Lake City
2026-11-08 FOCS 2026 conference, New YorkPrint the equivalent table for the live year from the current CFPs before using it; both venues move their dates by days-to-weeks between cycles.
Ownership map for multi-author teams
Name one owner each for: proof verification, the twelve-page story, the literature sweep, anonymity/format compliance, and the full-version release. The two that slip when shared are verification ("I thought you checked Lemma 5") and the full version ("the arXiv update can wait") — both are reputation-priced at this venue.
Cycle-volatility warnings
- Deadlines, the guaranteed-read window, double-blind details, and any feedback experiments are re-set annually in the CFP; the TheoryFest format itself evolves (待核实 whether future editions keep the expanded-week structure).
- FOCS mechanics are set independently by the IEEE TCMF side; never infer one venue's rules from the other's.
Output format
[Current stage] proving / verifying / writing / submitted / decided / camera-ready
[Beat decision] STOC <year> / FOCS <year> / hold one cycle
[Backward plan] <next two milestones with dates>
[Corrections file] empty / <n> entries pending
[Owner map] <verification, story, literature, compliance, full version>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Stoc 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 |
|---|---|---|---|---|---|---|
| Stoc Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Experiment Planappleweiping/WEIPING_WIKI | 119 | — | ~1k | Automated safety check: Pass | MIT | |
| Translational Study Blueprintaipoch/medical-research-skills | 2k | — | ~3.7k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.7k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Translational Study Blueprint
aipoch/medical-research-skills
Designs a translational blueprint for moving a biomedical finding toward diagnosis, prognosis, treatment response prediction, patient stratification, or therapeutic development, with explicit…
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
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
Questions about Stoc Workflow
What does Stoc Workflow do?
A skill your agent uses when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year…. Stoc Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.
When should I use Stoc Workflow?
Stoc Workflow fits situations like: planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline; the STOC/FOCS alternating two-deadline year that theory groups schedule around; full-version and camera-ready milestones; the June TheoryFest endpoint.
How do I install Stoc Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-workflow -a claude-code`. Or copy the skill folder (STOC-Skills/skills/stoc-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/stoc-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Stoc Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-workflow -a codex`. Or copy the skill folder (STOC-Skills/skills/stoc-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/stoc-workflow in your project. Codex loads it when a task matches its description.
Can I use Stoc 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 stoc-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/stoc-workflow, .gemini/skills/stoc-workflow, .github/skills/stoc-workflow and .opencode/skills/stoc-workflow in your project.
What does Stoc Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Stoc Workflow is instructions for the agent only.
Does Stoc 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 Stoc 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 Stoc Workflow use?
Stoc 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 Stoc Workflow 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 Workflow?
Skills that share tags, products or a category with Stoc Workflow: Experiment Plan (appleweiping/WEIPING_WIKI, 119 stars), Translational Study Blueprint (aipoch/medical-research-skills, 2k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Uv (astral-sh/claude-code-plugins, 313 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stoc Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.