stoc-submission
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-submission --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 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 guarante
- The reading contract, not a page limit
- Format floor (2026 wording)
- Anonymity, new to the house tradition
- SIGACT prior/simultaneous-publication policy
- Desk-risk and damage triage
- Deadline-week sequence
- What the portal itself will ask
- Habits from other venues that break here
- Output format
What does the stoc-submission skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-submission --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.