stoc-reproducibility
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-reproducibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# STOC Reproducibility For a proofs-only venue, "reproducible" means a third party can verify every claimed theorem without contacting the authors. STOC's structure makes this a **two-document problem** that pure-appendix venues do not have: the committee reads a 12-page guaranteed window, the community reads the arXiv/ECCC full version, and the paper is only as checkable as the *pair* is consistent. No checklist form enforces any of this — the STOC 2026 CFP contains none (checked 2026-07-08) — so the discipline below is self-imposed or absent. ## Statement drift: the STOC-specific failure Whenever the same theorem exists in two documents, the versions decay apart: a hypothesis strengthened during a proof repair gets updated in one file only; a constant improves in the full version while the abstract still advertises the old one; numbering shifts and cross-references silently point at the wrong lemma. Drift is not cosmetic — a reader who finds Theorem 2's statement differing between the proceedings and arXiv cannot tell which one is proved. The mechanical cure is a **single-source build**: one repository of statement files included by both documents, so a statement physically canno
- Statement drift: the STOC-specific failure
- Checkability audit before submission
- Computation that claims depend on
- Verification workflow for the author team
- Vignette: how drift actually happens
- Cycle-volatility warnings
- Output format
What does the stoc-reproducibility skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-reproducibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.