Individual skill

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.

ICDE-Skills/skills/icde-artifact-evaluation/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,397
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top