icse-artifact-evaluation
Use when preparing an artifact for the ICSE Artifact Evaluation track after paper acceptance, covering the ACM badge system (Available, Reusable, Results Reproduced/Replicated), evaluator-proof packaging, archival requirements, open licensing, and the January-window timeline anchored to recent cycles.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-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.
# ICSE Artifact Evaluation ICSE's artifact track is a *post-acceptance, opt-in* evaluation: once the paper is in, you submit the artifact to a separate committee that awards ACM- standard badges printed on the published paper. It is the formal payoff of the verifiability work done at review time — if `icse-reproducibility` was followed, this skill is mostly packaging and paperwork. ## The badge system, as ICSE runs it Verified against the ICSE 2026 artifact-evaluation track (read 2026-07-08; ICSE follows the ACM artifact review and badging standard): | Badge | Who applies | What evaluators check | |---|---|---| | **Artifacts Available** | Authors of papers accepted to Research, SEIP, NIER, SEIS, Doctoral Symposium, Demonstrations | Artifact is permanently archived in a public, DOI-issuing repository — not a personal GitHub, which can be deleted or rewritten | | **Artifacts Reusable** (Evaluated) | Same tracks | Quality "significantly exceeds minimal functionality": careful documentation, structure that supports reuse and repurposing by others | | **Results Reproduced / Replicated** | Authors of *prior published* SE work | Independent obtainment of the paper's results, per the ACM d
- The badge system, as ICSE runs it
- Timeline anchor
- From review package to badge submission
- The evaluator-proof README
- Scoping what the artifact claims
- Failure modes that cost badges
- Reverify each cycle
- Output format
What does the icse-artifact-evaluation skill do?
Use when preparing an artifact for the ICSE Artifact Evaluation track after paper acceptance, covering the ACM badge system (Available, Reusable, Results Reproduced/Replicated), evaluator-proof packaging, archival requirements, open licensing, and the January-window timeline anchored to recent cycles.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-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.