Agent skill

stoc-artifact-evaluation

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.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-artifact-evaluation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: STOC-Skills/skills/stoc-artifact-evaluation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# STOC Artifact Evaluation STOC has no artifact-evaluation committee, no badges, and no code-upload channel: nothing of that kind appears in the STOC 2026 Call for Papers (checked 2026-07-08). Importing an ML-conference artifact checklist would answer questions this venue never asks. But STOC is not artifact-free either — the 2026 CFP *expects* accepted authors to place the full paper, with all proofs, on arXiv or ECCC by camera-ready. So the venue's real artifact policy is: **the extended abstract advertises; the public full version is the object of record.** Plan your evidence around that split. ## The STOC evidence stack | Evidence object | Lives where | Consumed by | Binding? | |---|---|---|---| | Theorem statements + overview | First 12 pages of the submission | The whole PC, guaranteed | Yes — the reading contract | | Complete proofs | Appendix of the submission; later the arXiv/ECCC full version | Assigned reviewers; posterity | Yes — correctness rests here | | Certificates for computer-assisted steps | Appendix description + released checker | Any skeptic with a laptop | Yes, if a proof step depends on them | | Illustration code (plots, small searches) | Public repository l

What's inside
Steps it walks through
  1. The STOC evidence stack
  2. When computation is inside the proof
  3. The full version as the artifact of record
  4. Worked vignette: a construction found by search
  5. Optional strengtheners, priced honestly
  6. Quick decision rubric
  7. Output format
Commands it runs
arXiv ancillary files ride inside the source tarball under anc/
mkdir -p anc
cp verify_certificate.py certificate.drat anc/
tar czf stoc-full.tar.gz full-version.tex macros.tex refs.bib anc/
arXiv lists anc/* as downloadable ancillary files next to the paper
More from Awesome-Journal-Skills
All skills →
About this skill
What does the stoc-artifact-evaluation skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-artifact-evaluation --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.

Keep going