Individual skill
usenixsec-reproducibility
Use when strengthening reproducibility for a USENIX Security Symposium paper — writing the mandatory Open Science appendix, deciding what can and cannot be shared (exploit code, vulnerable-device data, human-subjects material), and making measurement, attack, and defense results independently regenerable.
USENIX-Security-Skills/skills/usenixsec-reproducibility/SKILL.md
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,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- writing Derived category
- data Derived category
- security Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# USENIX Security Reproducibility
Since the '26 cycle, USENIX Security has made openness a structural requirement:
every submission carries an **Open Science appendix** stating where the artifacts
behind the paper live, and acceptance is later conditioned on that availability
verifying (Phase-1 AE). This skill covers the appendix itself and the underlying
engineering that makes the statement true. Policy text is per-cycle — reread the
current CFP section before relying on wording.
## The Open Science appendix is a contract, not a caption
Reviewers read it during evaluation; the AEC enforces it after acceptance. It
should answer, concretely:
