Individual skill

icdt-artifact-evaluation

Use when preparing the "artifact" of an ICDT (International Conference on Database Theory) paper, which at a pure-theory venue is the complete-proofs full version rather than a code package — covering why ICDT has no ACM-style artifact-badging or code-artifact track, what the marked appendix and the archived arXiv full version must contain, and (only for the rare algorithmic paper) how any code should be handled.

ICDT-Skills/skills/icdt-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
Yes
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,404
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

# ICDT Artifact Evaluation

Read this to set expectations correctly: **ICDT is a pure database-theory venue with no code-artifact
track and no ACM-style artifact badges.** The role an artifact plays at a systems or empirical venue
— letting an evaluator re-run your result — is played at ICDT by the **complete, checkable proof**:
the marked appendix that a referee reads, and the **archived full version** that carries every proof
for readers after publication. This skill is about making that proof-artifact airtight, not about
Docker images.

> If you arrived expecting the ACM "Available / Functional / Reusable / Reproduced" badges, note that
> those belong to venues like the co-located **EDBT** (systems) or SIGMOD/PODS's ACM track. ICDT
> publishes in **LIPIcs** and evaluates *proofs*. Whether a given EDBT/ICDT edition offers any
> optional artifact/reproducibility recognition for ICDT papers is **待核实** — check the current
> call; the default is none.
Back to top