icde-artifact-evaluation
Use when packaging IEEE ICDE code, data, workload generators, and logs as supplemental material whose availability reviewers score, and for any post-acceptance reproducibility or badge process the edition runs. Covers what a builder-heavy committee inspects first, making a data-systems benchmark turnkey, and single-blind packaging.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.
# ICDE Artifact Evaluation Use this for evidence packaging around ICDE. ICDE expects authors to submit supplemental material and **considers its availability in the evaluation**, so a strong artifact directly raises the paper's floor even where no separate badge process runs. Confirm whether the current edition also runs a post-acceptance reproducibility/badge track (待核实) before promising evaluators anything. ## Artifact plan - Decide what evidence a **builder** needs to believe the numbers: the system source, the workload generators, the baselines' configurations, the datasets or their construction scripts, seeds, and logs. - Keep decision-critical evidence in the **paper or its figures**; the artifact demonstrates reproducibility, it does not replace the argument. - Provide a **minimal reproduction map**: build steps, dependencies, hardware assumptions (especially the storage device), commands, expected outputs, runtime, and known nondeterminism sources. - For restricted or proprietary data, give enough provenance and construction detail for a credible re-run without violating data-use terms. - After acceptance, publish the **public, licensed, tagged** version whose commit produc
- Artifact plan
- What ICDE evidence reviewers open first
- Worked vignette: packaging a storage-engine benchmark
- Single-blind and logistics anchors
- Output format
What does the icde-artifact-evaluation skill do?
Use when packaging IEEE ICDE code, data, workload generators, and logs as supplemental material whose availability reviewers score, and for any post-acceptance reproducibility or badge process the edition runs. Covers what a builder-heavy committee inspects first, making a data-systems benchmark turnkey, and single-blind packaging.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.