icalp-reproducibility
Use when making an ICALP (EATCS) theory result independently checkable — writing complete, self-contained proofs in the appendix and a full version (arXiv/ECCC/HAL), pinning any computational steps to reproducible certificates, and (optionally) formalizing key theorems in Coq/Lean/Isabelle, since ICALP has no runnable-artifact track and proof verifiability is the analogue of reproducibility.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-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.
# ICALP Reproducibility (proof verifiability and the full version) At a pure-theory venue, "reproducibility" means a referee — and later any reader — can **check the proof**. ICALP has **no artifact-evaluation track and no badges**; the deliverable that plays that role is the **full version** with complete proofs, plus, where relevant, reproducible computational certificates and optional machine formalization. This skill builds that checkability into the paper from the start, because a proof cannot be reconstructed after the fact any more than a lost dataset can. ## The full version is the reproducibility story - The 15-page body sketches; the **full version** (a clearly labelled appendix at submission, and an **arXiv/ECCC/HAL** posting at/after notification) contains **every proof in full**. This is what makes an ICALP result reproducible: an independent expert can verify it end to end. - Write proofs **self-contained**: state every lemma the argument uses, prove or cite each, and avoid "it is easy to see" for steps that are not. The test is whether a competent non-author can follow it without asking you. - Keep the **submission appendix and the eventual arXiv version consistent**
- The full version is the reproducibility story
- Self-contained proof checklist
- Reproducible computation, when a proof uses it
- Optional: machine-checked formalization
- What ICALP reproducibility is NOT
- Worked vignette: an intricate lower bound
- Output format
What does the icalp-reproducibility skill do?
Use when making an ICALP (EATCS) theory result independently checkable — writing complete, self-contained proofs in the appendix and a full version (arXiv/ECCC/HAL), pinning any computational steps to reproducible certificates, and (optionally) formalizing key theorems in Coq/Lean/Isabelle, since ICALP has no runnable-artifact track and proof verifiability is the analogue of reproducibility.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-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 909 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.