popl-reproducibility
Use when making a POPL paper's results independently checkable — deciding which theorems to mechanize versus hand-prove, maintaining a paper-to-proof correspondence table from day one, keeping on-paper proofs auditable with explicit assumption tracking, and making any accompanying prototype's numbers regenerable.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-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.
# POPL Reproducibility At a theory venue "reproducible" does not mean rerunnable seeds; it means **an independent reader can re-establish your claims**. For POPL that decomposes by claim type, and the discipline pays twice: once with reviewers under full double-blind, and again with artifact evaluators after conditional acceptance, where reusable proof claims must be complete — no `admit`, no `sorry` (AE criteria read 2026-07-08). ## What each claim type owes the reader | Claim type | Its reproducibility obligation | |---|---| | Mechanized theorem | Development compiles; theorem checkable; axioms printed and declared | | On-paper theorem | Full proof in the appendix; every hypothesis stated where used, not discovered mid-proof | | Definitional adequacy ("our semantics models X") | Examples or an adequacy theorem connecting formalism to the informal system | | Prototype measurement | Scripted runs, versioned inputs, stated machine — see `popl-experiments` | ## Mechanize deliberately, not maximally Full mechanization is powerful but not free; partial mechanization is respectable at POPL **when scoped honestly**. Decide per theorem: - Mechanize the theorems whose proofs are long, synt
- What each claim type owes the reader
- Mechanize deliberately, not maximally
- The correspondence table
- Assumption hygiene for on-paper proofs
- Output format
What does the popl-reproducibility skill do?
Use when making a POPL paper's results independently checkable — deciding which theorems to mechanize versus hand-prove, maintaining a paper-to-proof correspondence table from day one, keeping on-paper proofs auditable with explicit assumption tracking, and making any accompanying prototype's numbers regenerable.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-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.