itcs-reproducibility
Use to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.
# ITCS Reproducibility "Reproducibility" at a pure-theory venue means one thing: **a competent, skeptical reader can verify every central claim from the paper alone.** There is no code to rerun and no dataset to re-mine — the analogue of a reproducibility package is a **complete, self-contained, correctly attributed proof**. ITCS makes this concrete in its call: submissions must include **complete proofs of all central claims** (in an appendix if needed). This skill is the discipline that makes the mathematics checkable, which — since ITCS has **no rebuttal** — is also your only defense against a reviewer who gets stuck. ## Completeness: every central claim is fully proved - **No "proof omitted," no "proof is standard," no "see the full version"** for anything a reviewer must check to believe the result. Deferring a *routine* calculation to an appendix is fine; deferring the *load-bearing* lemma is a reproducibility failure and, at ITCS, a likely reject. - **Distinguish proved from assumed.** Every step is either proved here or cited to a precise prior result. A theorem that quietly relies on an unproved claim is the theory analogue of a package that silently calls a missing depend
- Completeness: every central claim is fully proved
- Self-containment: definitions and notation
- Dependency provenance: pin what you borrow
- The full version as the durable record
- The checkability passes (run before upload)
- Common failure modes
- Output format
What does the itcs-reproducibility skill do?
Use to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.