icsme-artifact-evaluation
Use when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed" badges, what evaluators check first, DOI-issuing archives, evaluator-proof documentation, the shared track with SCAM and VISSOFT, and the separate post-acceptance deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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.
# ICSME Artifact Evaluation Use this for the artifact track. ICSME evaluates artifacts in the **Joint Artifact Evaluation Track and ROSE Festival** (ROSE = Recognizing and rewarding Open Science in software Engineering), shared with its co-located siblings **SCAM** and **VISSOFT**, and it awards the **IEEE** badge scheme — not ACM's four badges. Two things to internalize: the badges are earned by evaluators actually retrieving and 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 IEEE badges (verify the current set and names) | Badge | What it certifies | What earns it | |---|---|---| | Open Research Object | The artifact is permanently, publicly retrievable and open | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) with an open license | | Research Object Reviewed | The artifact was examined and is exercisable, well-structured, and documented | Evaluators can run/inspect it and confirm it supports the paper's claims | A package can earn **both** badges if it is open *and* exercisable, well-structured, and documented for reuse and
- The IEEE badges (verify the current set and names)
- What ROSE evaluators open first
- Packaging plan
- Anonymized review artifact vs. badge artifact
- Worked vignette: packaging a debt-detection tool + mining study
- Calibration
- Output format
What does the icsme-artifact-evaluation skill do?
Use when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed" badges, what evaluators check first, DOI-issuing archives, evaluator-proof documentation, the shared track with SCAM and VISSOFT, and the separate post-acceptance deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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.