fse-artifact-evaluation
Use when packaging an ESEC/FSE artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what SIGSOFT evaluators check first, DOI-issuing archives, evaluator-proof documentation, and the separate post-acceptance artifact deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-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.
# FSE Artifact Evaluation Use this for the artifact track. FSE follows the **ACM Artifact Review and Badging** scheme, and the artifact evaluation is a **separate, post-acceptance** process with its own deadline. 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). ## The ACM 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 Evaluated - Functional | The artifact runs and does what the paper says | A clean-machine install, a demo, and documented expected outputs | | Artifacts Evaluated - Reusable | Others can build on it | The Functional bar plus careful docs, structure, and licensing | | Results Reproduced | An evaluator reproduced the paper's key results | A turnkey path from the artifact to the headline numbers | Available is a low-cost, high-value badge (archive the package); Functiona
- The ACM badges (verify the current set and names)
- What SIGSOFT evaluators open first
- Packaging plan
- Anonymized review artifact vs. badge artifact
- Worked vignette: packaging a detection tool + study
- Calibration
- Output format
What does the fse-artifact-evaluation skill do?
Use when packaging an ESEC/FSE artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what SIGSOFT evaluators check first, DOI-issuing archives, evaluator-proof documentation, and the separate post-acceptance artifact deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-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.