popl-experiments
Use when designing the empirical component of a POPL paper — deciding whether evidence should be a mechanization, a prototype, case studies, or benchmarks; reporting proof effort and case-study coverage honestly; and keeping performance numbers in a supporting role so the formal claim stays the paper's center of gravity.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-experiments --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 Experiments and Empirical Evidence POPL welcomes experimental papers, but the evaluation's job differs from a systems venue: at POPL, evidence **demonstrates that the formal idea is realizable and relevant**, it does not substitute for the theorem. Calibrate the empirical section to the claim it supports, and no further. (Venue facts referenced here were checked 2026-07-08; see `resources/official-source-map.md`.) ## Match evidence to claim | Claim in the paper | Right evidence | Wrong evidence | |---|---|---| | "The type system is sound" | Proof (mechanized or on-paper, `popl-reproducibility`) | A test suite that found no counterexample | | "The analysis is precise enough to be useful" | Case studies on real programs with found/missed counts | One toy example | | "The logic scales to real proofs" | Proof effort data: LOC, person-time, lemma reuse across case studies | Adjectives ("lightweight," "practical") | | "Checking is fast enough for interaction" | Timings on stated hardware with input sizes | Asymptotic claims dressed as measurements | | "The translation preserves behavior" | The theorem, plus differential testing as a sanity layer | Testing alone | ## Proof effort i
- Match evidence to claim
- Proof effort is data at this venue
- Case-study discipline
- Performance numbers, when present
- Output format
Rocq/Coq development: spec vs proof line counts per file coqwc theories/*.v | tail -5 Lean 4: declaration counts as a proxy for library size grep -rcE '^(theorem|lemma|def) ' Src/ | sort -t: -k2 -nr | head Case-study table skeleton: program, LOC, proved property, person-days, reused lemmas
What does the popl-experiments skill do?
Use when designing the empirical component of a POPL paper — deciding whether evidence should be a mechanization, a prototype, case studies, or benchmarks; reporting proof effort and case-study coverage honestly; and keeping performance numbers in a supporting role so the formal claim stays the paper's center of gravity.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-experiments --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.