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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-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.
# 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: - **What exists**: code, datasets, configurations, analysis notebooks, hardware designs — enumerated, not gestured at. - **Where**: resolvable locations (anonymized mirrors at submission; permanent, ideally DOI-backed archives in the final paper). - **What is withheld and why**: the policy accepts justified omission, and security work legitimately generates a lot of it. ```latex \section*{Open Science} All scanner source code, the analysis pipeline, and the aggregated measurement tables (Sections 4--6) are available at \url{<anonymized-archive>}
- The Open Science appendix is a contract, not a caption
- Withholding decisions that hold up
- Determinism engineering for security experiments
- Paper-side reporting that reviewers check
- Reverify each cycle
- Output format
Capture the environment fingerprint alongside every experiment run sha256sum targets.txt config.yaml; pip freeze | sort; } > runs/$(date +%s).env
What does the usenixsec-reproducibility skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-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 909 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.