Agent skill

popl-artifact-evaluation

Use when packaging a POPL artifact — above all a mechanized proof development in Rocq/Coq, Lean, Agda, or Isabelle — for the post-conditional-acceptance evaluation, satisfying the no-admit/no-sorry completeness rule, mapping paper theorems to proof files, pinning toolchains, and earning the Functional, Reusable, and Available badges.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-artifact-evaluation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: POPL-Skills/skills/popl-artifact-evaluation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# POPL Artifact Evaluation POPL invites authors of conditionally accepted papers to submit supporting materials to artifact evaluation, and its AE tracks treat **proof developments as the canonical artifact**: Coq and Isabelle proof libraries are the track's own examples of reusable artifacts (POPL 2025/2026 AE pages, read 2026-07-08). A verification tool or evaluation harness can ride along, but at this venue the evaluator's core question is usually "does this mechanization actually prove what the paper claims?" ## The badge criteria, proof-flavored | Badge | Criterion (2025/2026 wording) | For a proof artifact this means | |---|---|---| | Artifacts Evaluated - Functional | Supports the paper's claims, documented well enough to run and validate | The development compiles from scratch and each paper theorem is checkable | | Artifacts Evaluated - Reusable | Additionally packaged for reuse: docs, installation, portability, new examples, open licensing / issue tracker | Definitions and lemmas usable by other projects — and **complete: no `admit` in Coq/Rocq, no `sorry` in Lean or Isabelle** | | Artifacts Available | Archived eternally on an archival repository (Zenodo, ACM DL) | A DOI

What's inside
Steps it walks through
  1. The badge criteria, proof-flavored
  2. The axiom audit
  3. Package for an evaluator with one week and one laptop
  4. Output format
Commands it runs
coqchk -silent -o MyDev.Main
echo "Print Assumptions main_soundness." | coqtop -l theories/Main.v
Lean 4: elaborate and show axioms
lake build && echo '#print axioms Main.soundness' >> Scratch.lean
grep -rn "postulate" src/ ; agda --safe src/Everything.agda
More from Awesome-Journal-Skills
All skills →
About this skill
What does the popl-artifact-evaluation skill do?

Use when packaging a POPL artifact — above all a mechanized proof development in Rocq/Coq, Lean, Agda, or Isabelle — for the post-conditional-acceptance evaluation, satisfying the no-admit/no-sorry completeness rule, mapping paper theorems to proof files, pinning toolchains, and earning the Functional, Reusable, and Available badges.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-artifact-evaluation --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.

Keep going