STOC Skills

A 12-skill depth pack for STOC (ACM Symposium on Theory of Computing) submissions: venue fit for broad-audience theory results, HotCRP submission checks under the abstract + table-of-contents + 12-page reading rule, double-blind hygiene, extended-abstract vs arXiv/ECCC full-version discipline, proof checkability, STOC/FOCS cycle planning, and ACM camera-ready. Grounded in the STOC 2026 CFP and SIG

by @brycewang-stanford 11 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/stoc-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 11 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-stoc-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 11
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Stoc Submission · brycewang-stanford
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.

1k repo stars
▌
Stoc Experiments · brycewang-stanford
Use when judging whether computation belongs in a STOC (ACM Symposium on Theory of Computing) paper at all — STOC accepts on theorems, with no empirical-evaluation expectation — and when it does, scoping it as certified proof computation, constructive search, or clearly labeled illustration rather than benchmarking.

1k repo stars
▌
Stoc Camera Ready · brycewang-stanford
Use when converting a STOC (ACM Symposium on Theory of Computing) acceptance into publishable form — the ACM proceedings version, de-anonymization, rights forms, the CFP-level expectation that the full paper with proofs goes public on arXiv or ECCC by the camera-ready deadline, and TheoryFest talk preparation.

1k repo stars
▌
Stoc Related Work · brycewang-stanford
Use when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint version pairs correctly, handling concurrent arXiv and ECCC work, and keeping self-citation double-blind-safe.

1k repo stars
▌
Stoc Supplementary · brycewang-stanford
Use when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table of contents, theorem-to-proof pointer discipline, and the division of labor between the submission appendix and the arXiv/ECCC full version.

1k repo stars
▌
Stoc Writing Style · brycewang-stanford
Use when drafting or revising a STOC (ACM Symposium on Theory of Computing) paper — the theorem-forward first page, informal/formal statement pairing, the technical-overview section that carries acceptance, notation economy for a cross-area committee, and prose that survives the twelve guaranteed pages.

1k repo stars
▌
Stoc Review Process · brycewang-stanford
Use when reasoning about how a STOC (ACM Symposium on Theory of Computing) submission is evaluated — the SIGACT program-committee model with external subreviewers, HotCRP mechanics, double-blind conflicts, the November-to-February decision arc, and what best-paper designation and rejection each actually mean.

1k repo stars
▌
Stoc Author Response · brycewang-stanford
Use when planning author-side communication for a STOC (ACM Symposium on Theory of Computing) submission, where no standing rebuttal phase exists — covering pre-emptive writing that answers objections in advance, chair-mediated technical clarifications if the PC asks, and the FOCS resubmission letter after a rejection.

1k repo stars
▌
Stoc Reproducibility · brycewang-stanford
Use when hardening a STOC (ACM Symposium on Theory of Computing) paper so its results can be independently checked — proof completeness across the extended-abstract/full-version split, single-source builds that prevent statement drift between the two documents, and determinism for any computation a claim relies on.

1k repo stars
▌
Stoc Topic Selection · brycewang-stanford
Use when deciding whether a result belongs at STOC (ACM Symposium on Theory of Computing) — testing for broad theory-of-computation significance versus routing to FOCS, SODA, CCC, ITCS, COLT, CRYPTO, PODC, SoCG, EC, or a journal like JACM/SICOMP when the fit is specialized, conceptual, or empirical.

1k repo stars
▌
Stoc Artifact Evaluation · brycewang-stanford
Use when deciding what evidence objects a STOC (ACM Symposium on Theory of Computing) paper must ship, given that STOC runs no artifact-evaluation track — the durable artifact is the public full version on arXiv/ECCC, plus verifiable certificates whenever a proof leans on computation, and optional mechanization.

1k repo stars