ieeesp-reproducibility
Use when hardening the reproducibility of an IEEE S&P (Oakland) paper's evidence before submission, including environment pinning for exploits and side channels, seed and trial reporting for probabilistic attacks, measurement snapshotting of live systems, and honest availability statements under ethical release limits.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-reproducibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# IEEE S&P Reproducibility Use this while the evidence is being produced — months before `ieeesp-artifact-evaluation` packages it. Security results decay in ways ML results do not: targets get patched, infrastructure changes, and an attack that "worked in March" can be unreproducible by review time. Reproducibility at S&P is first about **freezing the world you measured**. ## Freeze the target, not just the code | Evidence type | What must be pinned | Decay risk if not | |---|---|---| | Software exploit | Target version, build flags, distro, patch level | Silent fix ships mid-review | | Microarchitectural attack | CPU model + stepping, microcode, OS mitigations state | Microcode update changes timing | | Network measurement | Scan dates, vantage points, target-list snapshot | Internet moved; sample unrecoverable | | Web/API study | Crawl date, client fingerprint, geographic origin | Server-side behavior shifts | | ML attack/defense | Model weights hash, dataset version, threat-budget ε | "Same" model retrained differently | Record these in the paper, not only in lab notes — a reviewer asking "does this still work after <vendor>'s April update?" is a reproducibility question about t
- Freeze the target, not just the code
- Determinism ledger for probabilistic evidence
- When ethics limits release, say exactly what and why
- Cheap habits that pay at rebuttal time
- What this venue does not require
- Output format
What does the ieeesp-reproducibility skill do?
Use when hardening the reproducibility of an IEEE S&P (Oakland) paper's evidence before submission, including environment pinning for exploits and side channels, seed and trial reporting for probabilistic attacks, measurement snapshotting of live systems, and honest availability statements under ethical release limits.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-reproducibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.