Agent skill · Documentation

atc-artifact-evaluation

Use when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available, Artifacts Functional, and Results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline, with evaluator-proof documentation and a turnkey path to the paper's numbers.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-artifact-evaluation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: ATC-Skills/skills/atc-artifact-evaluation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# ATC Artifact Evaluation Use this for the artifact track. ATC follows the shared **USENIX/SIGOPS** artifact-evaluation scheme: an **Artifact Evaluation Committee (AEC)** runs a **separate, post-acceptance** process through HotCRP and awards up to three badges — **Artifacts Available**, **Artifacts Functional**, and **Results Reproduced**. Two things to internalize: badges are earned by evaluators **actually using** your package, and the review artifact (anonymized, for the paper's reviewers) is not the same deliverable as the badge artifact (de-anonymized, permanently archived). ATC's artifact culture is strong and high-participation — for USENIX ATC '25, most evaluated artifacts earned Functional and a large majority earned Reproduced. ## The three badges (verify the current set and names) | Badge | What it certifies | What earns it | |---|---|---| | Artifacts Available | The artifact is permanently, publicly retrievable | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) | | Artifacts Functional | It is documented, complete, and exercisable — it runs and does what the paper says | Clean-machine install, a demo, scripts + data to run the experiments | | Resul

What's inside
Steps it walks through
  1. The three badges (verify the current set and names)
  2. What AEC evaluators open first
  3. Packaging plan
  4. Anonymized review artifact vs. badge artifact
  5. Worked vignette: a storage-cache policy + measurement
  6. Calibration
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the atc-artifact-evaluation skill do?

Use when packaging an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) artifact for the USENIX-lineage evaluation scheme — earning the Artifacts Available, Artifacts Functional, and Results Reproduced badges from the Artifact Evaluation Committee on its separate post-acceptance deadline, with evaluator-proof documentation and a turnkey path to the paper's numbers.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-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.

Keep going