Menu

Individual skill

pods-experiments

0upvotes

Use when designing or auditing the analytical "evidence" of an ACM PODS paper — worst-case and average-case analyses, matching upper and lower bounds, dichotomy completeness, correct complexity assumptions, and the occasional empirical validation when a theory paper claims practicality — matching the rigor to the shape of each theoretical claim.

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

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
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,405
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 Experiments

Use this before submission when the technical story is not yet locked. For PODS the "experiments" are
mostly **analyses and proofs**, because the reviewers are theoreticians and the evidence is a theorem,
not a benchmark. The organizing principle is **rigor proportional to the claim** — the analysis must
establish exactly what the paper asserts, in the model it names, with no hidden gap.

## Analysis audit

- **Match the analysis to the claim shape.** A claim of optimality needs a *matching lower bound*; a
  claim of a classification needs *completeness* (every case decided); a claim of efficiency needs an
  exact complexity in a stated measure (data vs. combined), not an asymptotic hand-wave.
- **Close the upper/lower-bound gap, or state it.** An upper bound without a lower bound is not
  optimality; if the gap is open, say so precisely rather than implying tightness.
Back to top