Menu

Individual skill

icalp-artifact-evaluation

0upvotes

Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete proofs, reproducible computational certificates, and optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate.

ICALP-Skills/skills/icalp-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,405
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

# ICALP Artifact Evaluation (there isn't one — and what replaces it)

Read this first if you are arriving from a venue with an artifact track. **ICALP has no artifact
evaluation, no artifact-evaluation committee, and no ACM/IEEE badges.** It is a **pure theoretical
computer science** venue: the contribution is a theorem, and the "artifact" a referee cares about is
the **proof**. Building a Docker image, a benchmark harness, or a reproducibility capsule for an ICALP
submission is effort spent on something no one will evaluate — and can even signal that the paper is
mis-routed.

## Why no artifact track

- ICALP results are **mathematical**: correctness is established by a proof a referee checks, not by
  running code on a machine.
- The community norm and the LIPIcs open-access model center the **published proof and the full
Back to top