Individual skill
itcs-artifact-evaluation
Use to adapt the idea of an "artifact" to a pure-theory venue — at ITCS there is no artifact-evaluation track, no code, and no badges; the analogue is making every claim independently verifiable through complete proofs in the submitted PDF and a matching public full version, plus checkable finite objects for any computational content.
ITCS-Skills/skills/itcs-artifact-evaluation/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- 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,410
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,033 bytes
Read excerpt
# ITCS Artifact Evaluation
**ITCS has no artifact-evaluation track.** There are no ACM/IEEE artifact badges, no
Available/Functional/Reusable/Reproduced tiers, no code submission, and no evaluation committee
inspecting a package. It is a **pure-theory** venue: the thing that must be independently
verifiable is the **mathematics**. This skill exists because authors arriving from empirical CS
(where "artifact evaluation" is a real post-acceptance track) need to know what plays that role at
ITCS — and what does *not* apply.
## The ITCS "artifact" is the proof
The artifact that a reviewer inspects is the **argument itself**. Making it "evaluatable" means:
- **Complete proofs of every central claim, inside the submitted PDF** (body sketch + appendix