Agent skill

eurosys-artifact-evaluation

Use when preparing a EuroSys artifact for the sysartifacts-run evaluation — choosing among the Available, Functional, and Reproduced badges, timing the post-notification artifact submission, building for an evaluator on foreign hardware, and aiming at the Gilles Muller Best Artifact Award rather than a minimal pass.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eurosys-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: 6 KB
Bundled scripts: none
Path: EuroSys-Skills/skills/eurosys-artifact-evaluation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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

# EuroSys Artifact Evaluation Use this when an accepted (or optimistically, submitted) EuroSys paper has code, data, or hardware behind its claims. EuroSys artifact evaluation is organized with the **sysartifacts** community (`sysartifacts.github.io/eurosys2026/`, rendered 2026-07-08); it is optional, happens **after acceptance notification**, and awards up to three badges that appear on the published paper. The EuroSys 2027 call for artifacts was not yet verifiable on 2026-07-08 — 待核实 before committing to dates or badge criteria. ## The three-badge menu Authors declare which badges they want; the AEC grants zero to three. | Badge | EuroSys 2026 criterion (rendered) | Typical blocker | |---|---|---| | Available | Artifact retrievable from a public, DOI-backed archive | "It's on our GitHub" — mutable, not archival | | Functional | Complete, documented, exercisable as described | Undocumented cluster assumptions; missing inputs | | Reproduced | Paper's main claims independently re-obtained | Experiments needing hardware the AEC cannot access | Sensible combinations tracked by the process: all three for ordinary software artifacts; Available + Functional for datasets or custom-environ

What's inside
Steps it walks through
  1. The three-badge menu
  2. Design for the evaluator you will actually get
  3. Archival step for the Available badge
  4. Why aim above the minimum
  5. Timeline coupling with the paper lanes
  6. Documentation pyramid
  7. Failure patterns the AEC reports
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the eurosys-artifact-evaluation skill do?

Use when preparing a EuroSys artifact for the sysartifacts-run evaluation — choosing among the Available, Functional, and Reproduced badges, timing the post-notification artifact submission, building for an evaluator on foreign hardware, and aiming at the Gilles Muller Best Artifact Award rather than a minimal pass.

How do I install it?

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

Keep going