ieeesp-artifact-evaluation
Use when preparing an IEEE S&P (Oakland) artifact-evaluation submission after acceptance, including choosing among the Available, Functional, and Results Reproduced badges, DOI-backed deposits, packaging exploits and malware-adjacent code responsibly, and scoping what evaluators can actually re-run.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-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.
# IEEE S&P Artifact Evaluation Use this once a paper is accepted and the team is deciding whether and how to enter artifact evaluation. At S&P, AE is a **post-acceptance opt-in** run by a separate committee against three badges (sp2026.ieee-security.org /cfartifacts.html, checked 2026-07-08); the 2027 schedule and any badge changes were unpublished at check time — 待核实 on the current AE pages. ## The three badges are three different projects | Badge | What it certifies | The actual work | |---|---|---| | **Available** | Artifact permanently deposited with a DOI (Zenodo, FigShare, Dryad — not a lab webpage or GitHub alone) | Deposit hygiene: license, README, versioned snapshot | | **Functional** | Evaluators exercised the artifact per your instructions | Environment capture + scripted entry points that run elsewhere | | **Results Reproduced** | Evaluators regenerated the paper's key results | Claim-to-command map with tolerances and runtimes | Pick badges by what an outsider can genuinely re-run. A measurement study of live infrastructure can honestly target Available (data + analysis code) even when Reproduced is impossible; overclaiming a badge wastes the committee's goodwill and y
- The three badges are three different projects
- Security artifacts have handling constraints others do not
- Packaging for a stranger with a deadline
- Process notes
- Failure modes specific to this venue
- Output format
What does the ieeesp-artifact-evaluation skill do?
Use when preparing an IEEE S&P (Oakland) artifact-evaluation submission after acceptance, including choosing among the Available, Functional, and Results Reproduced badges, DOI-backed deposits, packaging exploits and malware-adjacent code responsibly, and scoping what evaluators can actually re-run.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-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 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.