issta-artifact-evaluation
Use when packaging an ISSTA tool, benchmark, and results for the artifact-evaluation track, covering the ACM badges (Artifacts Available via Zenodo, Evaluated Functional and Reusable, Results Reproduced), the anonymous review-time copy, containerization, a runnable entry point, and what ISSTA artifact evaluators actually try first.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-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.
# ISSTA Artifact Evaluation Use this to package evidence for ISSTA's artifact-evaluation track. ISSTA has a genuinely strong artifact culture: a runnable tool and a shared benchmark are treated as normal, and the badges carry weight. Reopen the current artifact call before packaging — the badge set and the archival requirement are cycle-specific. ## The ACM badge targets | Badge | What it certifies | What you must ship | |---|---|---| | Artifacts Available | The artifact is publicly, permanently retrievable | A DOI-issuing deposit (Zenodo) — a GitHub link alone does not qualify | | Artifacts Evaluated — Functional | The artifact runs and does what the paper says | A working entry point, dependencies, and a documented expected output | | Artifacts Evaluated — Reusable | Others can inspect, adapt, and build on it | Clean structure, real documentation, and configurability beyond the paper's runs | | Results Reproduced | The paper's key results regenerate from the artifact | Scripts that produce the paper's tables/figures within stated tolerance | Available is about *archival*; Functional and Reusable are about *engineering quality*; Results Reproduced is about *matching the paper*. Th
- The ACM badge targets
- Artifact plan
- What ISSTA evaluators try first
- Handling long-running and non-deterministic tools
- Calibration anchors
- Output format
What does the issta-artifact-evaluation skill do?
Use when packaging an ISSTA tool, benchmark, and results for the artifact-evaluation track, covering the ACM badges (Artifacts Available via Zenodo, Evaluated Functional and Reusable, Results Reproduced), the anonymous review-time copy, containerization, a runnable entry point, and what ISSTA artifact evaluators actually try first.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-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.