Individual skill

sigmetrics-experiments

Use when designing or auditing ACM SIGMETRICS evaluations, covering theorem-plus-validation rigor, stating and testing modeling assumptions, analysis-vs-simulation agreement, real workloads and traces, fairly tuned baselines, statistics and confidence intervals for stochastic systems, learning guarantees, measurement provenance, and matching evidence to the shape of each performance claim.

SIGMETRICS-Skills/skills/sigmetrics-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
No
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,400
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 Experiments

Use this before submission when the evidence is not yet locked. SIGMETRICS reviewers are
performance-evaluation specialists; the evaluation is where a good model or measurement is won or
lost. The organizing principle is **evidence proportional to the claim** — an analytic claim needs a
proof *and* validation, a measurement claim needs a methodology a skeptic accepts, and a learning
claim needs a guarantee, not only a benchmark score.

## Evaluation audit

- **Match evidence to the claim shape.** A claim about a **bound** needs a proof plus a simulation
  that shows the analytic curve is right; a claim about a **real system** needs measured data and a
  documented methodology; a claim about a **learner** needs a regret/convergence guarantee; a claim
  about **tail** behavior needs tail metrics (p99), not means.
Back to top