pods-artifact-evaluation
Use for the PODS analogue of artifact evaluation — there is no systems artifact track at this theory symposium, so this skill covers formal-claims verification instead: a complete at-submission proof appendix, a claim-to-proof mapping reviewers can check, the full-version-on-arXiv norm, and, only when a paper claims practicality, an honest optional code artifact.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.
# PODS Artifact Evaluation Use this to prepare the PODS equivalent of an artifact. **PODS has no artifact-evaluation track in the systems sense and no ACM reproducibility badges** — it is a database-theory symposium. The deliverable that plays the role of an artifact is your **formal-claims package**: a complete, self-contained proof appendix that ships with the submission, a mapping from every stated result to its proof, and, at camera-ready, a **full version on arXiv**. Do not import a systems artifact process; adapt to proof verification. ## The PODS "badges" — what actually certifies a theory paper | Analogue | What it certifies | What earns it | |---|---|---| | Complete proofs (at submission) | Every stated theorem is proved and checkable now | The appendix incorporated in the submitted PDF, with no gap deferred off-paper | | Claim-to-proof mapping | A reviewer can locate the proof of each result quickly | Forward references from each body statement to its body/appendix proof | | Full version on arXiv (at camera-ready) | The community can read the complete development | A de-anonymized arXiv full version, DOI-linked to the PACMMOD paper | | Optional code (only if practicality
- The PODS "badges" — what actually certifies a theory paper
- What PODS reviewers check first
- Formal-claims packaging plan
- Anonymized submission package vs. public full version
- Worked vignette: packaging a dichotomy paper's claims
- Calibration
- Output format
What does the pods-artifact-evaluation skill do?
Use for the PODS analogue of artifact evaluation — there is no systems artifact track at this theory symposium, so this skill covers formal-claims verification instead: a complete at-submission proof appendix, a claim-to-proof mapping reviewers can check, the full-version-on-arXiv norm, and, only when a paper claims practicality, an honest optional code artifact.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.