Individual skill

focs-reproducibility

Use when hardening a FOCS (IEEE Symposium on Foundations of Computer Science) paper's checkability — the theory analogue of reproducibility — via hypothesis ledgers, single-source theorem statements that cannot drift between submission and arXiv versions, audits of imported theorems, and certificates for machine-checked steps.

FOCS-Skills/skills/focs-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,411
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# FOCS Reproducibility

FOCS has no reproducibility checklist and asks for no artifacts (2026 CFP,
checked 2026-07-08). At a proofs venue, "reproducing" a result means an
independent expert can re-derive it from the paper alone. That property —
checkability — is engineerable, and papers engineered for it survive both
refereeing and the decade of scrutiny that follows a FOCS acceptance. Four
practices below build it.

## 1. The hypothesis ledger

Every assumption a theorem consumes should be visible at the theorem, not
scattered across ambient conventions declared in Section 2. Keep a ledger
during writing:
Back to top