Individual skill

sosp-experiments

Use when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks with end-to-end and failure runs, reporting tails and overheads honestly, and isolating the mechanism the design credits.

SOSP-Skills/skills/sosp-experiments/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 3, 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,389
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

# SOSP Experiments

Use this while the evaluation is being designed — it determines whether the paper is
writable at all. SOSP reviews concentrate their negative weight on evaluation
soundness, and the venue's response phase forbids new experiments (CFP, 2026 cycle,
checked 2026-07-08), so a hole discovered in review stays a hole. The evaluation's
job is to make each claim's evidence findable, fair, and attributable to the
mechanism the paper credits.

## Claims first, experiments second

Write the claim list before designing runs; every evaluation subsection should open
by naming the claim it discharges.