usenixsec-artifact-evaluation
Use when packaging artifacts for USENIX Security Symposium evaluation — the mandatory Phase-1 availability check that acceptance is conditional on, the optional Phase-2 push for Artifacts Functional and Results Reproduced badges, and building security artifacts (exploits, scanners, datasets) that evaluators can run safely.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-artifact-evaluation --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 Artifact Evaluation USENIX Security '26 split artifact evaluation into two phases with different stakes: **Phase-1 (availability) is mandatory and paper acceptance is conditional on it**, running between acceptance and the final-paper deadline; **Phase-2 (functionality and reproducibility) is optional**, running after finals are due. The community process and submission mechanics live at `secartifacts.github.io/usenixsec2026/`; the venue framing is on the usenix.org Call for Artifacts page (both checked 2026-07-08, via search renderings since usenix.org direct fetch returned 403). ## The three badges | Badge | What the AEC verifies | Phase | |---|---|---| | Artifacts Available | The artifacts named in the Open Science appendix exist at the stated location and are retrievable | Phase-1, required of all accepted papers (or a justified omission) | | Artifacts Functional | Core functionality works as documented: installs, runs, produces sane output | Phase-2, opt-in | | Results Reproduced | The paper's reported results were regenerated by the AEC | Phase-2, opt-in | Badges are issued independently — Reproduced does not require re-litigating Available. The strategic re
- The three badges
- Phase-1: make "available" mean available
- Phase-2: security artifacts have special failure modes
- Working the process
- Reverify each cycle
- Output format
What does the usenixsec-artifact-evaluation skill do?
Use when packaging artifacts for USENIX Security Symposium evaluation — the mandatory Phase-1 availability check that acceptance is conditional on, the optional Phase-2 push for Artifacts Functional and Results Reproduced badges, and building security artifacts (exploits, scanners, datasets) that evaluators can run safely.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-artifact-evaluation --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.