Menu

Individual skill

sigmetrics-reproducibility

0upvotes

Use when strengthening ACM SIGMETRICS reproducibility, covering proofs and their assumptions as reproducible artifacts, seeded simulators whose figures regenerate and match the analysis, measurement/trace provenance, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between what the paper proves/measures and what the artifact contains.

SIGMETRICS-Skills/skills/sigmetrics-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
Yes
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,411
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

# SIGMETRICS Reproducibility

Use this before submission and again before the POMACS camera-ready. SIGMETRICS reproducibility has
a distinctive shape: the "artifact" is often a **proof plus a simulator plus a trace**, not only
running code. The goal is that a competent reader could re-derive your bound, re-run your simulation
to the same curves, and re-analyze your measurement to the same conclusions.

## Evidence map

- Map each theorem, bound, and reported number to a **verifiable location** — a proof in an
  appendix, a figure regenerated from a seeded simulation, or a script that turns the trace into the
  table.
- For analytic results, give the **full derivation and every assumption**; a reader should be able
  to check the proof and see which assumptions each step uses.
Back to top