Individual skill

pods-reproducibility

Use when strengthening the verifiability of an ACM PODS paper — a complete claim-to-proof map, self-contained proofs in the at-submission appendix (no external appendices), correctly stated assumptions, honest scope and open cases, the full-version-on-arXiv norm, and consistency between what the paper claims and what the proofs actually establish.

PODS-Skills/skills/pods-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,409
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# PODS Reproducibility

Use this before submission and again before camera-ready. For a theory venue, "reproducibility" means
**verifiability**: a competent reader can follow every proof and confirm every stated theorem. PODS
makes this concrete by requiring the proof **appendix to be incorporated at submission** — there are
**no online/external appendices** — so the reviewers can check the mathematics now, not on trust.

## Claim-to-proof map

- Map each theorem, lemma, corollary, and reported bound to a **complete proof location** — the body
  or the appendix. No stated result may lack a full proof somewhere in the submitted PDF.
- For each proof, state its assumptions, cite the exact prior lemma or theorem it uses, and do not
  defer a key step to "the full version" or "a routine argument" when the argument is not routine.
- For constructions and algorithms, give enough that a reader could re-derive them: the invariant, the
Back to top