podc-artifact-evaluation
Use when an author expects an artifact-evaluation or badge track at ACM PODC and needs redirecting — PODC has NO artifact track and no ACM badges. This skill converts artifact-culture instincts into what PODC actually evaluates: proof-appendix completeness, model/assumption rigor, and the honest, optional role of any simulation.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-artifact-evaluation --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.
# PODC Artifact Evaluation (there isn't one — read this) If you arrived here expecting an Artifacts-Available / Functional / Reusable / Reproduced badge process, stop: **PODC has no artifact-evaluation track and no ACM badge program.** It is a proofs venue. The object that is "evaluated" is your **theorem and its proof**, and the honesty of your **model and assumptions**. This skill redirects artifact energy into the three things that actually decide a PODC paper's technical standing. ## Why PODC has no artifact track A PODC contribution is a **model, a theorem, and a proof**, not a running system or a dataset. There is nothing for evaluators to install and run to confirm the claim — the claim is confirmed by **reading the proof**. Importing a badge workflow here is a category error: it would evaluate an artifact that is, at most, an optional illustration. (Contrast this with software-engineering or systems venues, where the artifact *is* part of the evidence.) Any simulation you ship is a figure-generator, not proof of correctness (`podc-experiments`, `podc-reproducibility`). ## The three real "evaluations" at PODC ### 1. Proof-appendix completeness (the analogue of "Functional")
- Why PODC has no artifact track
- The three real "evaluations" at PODC
- 1. Proof-appendix completeness (the analogue of "Functional")
- 2. Model/assumption rigor (the analogue of "Reusable")
- 3. Optional-simulation transparency (the analogue of "Available")
- Mapping artifact instincts to PODC actions
- What NOT to do
- Output format
What does the podc-artifact-evaluation skill do?
Use when an author expects an artifact-evaluation or badge track at ACM PODC and needs redirecting — PODC has NO artifact track and no ACM badges. This skill converts artifact-culture instincts into what PODC actually evaluates: proof-appendix completeness, model/assumption rigor, and the honest, optional role of any simulation.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-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 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.