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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.
# 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 full proof). This is the single most important "artifact" obligation and it is enforced at submission, not post-acceptance (see [`itcs-submission`](../itcs-submission/SKILL.md) and [`itcs-reproducibility`](../itcs-reproducibility/SKILL.md)). - **Self-contained definitions** so the claims can be verified without your other papers open. - **Pinned dependencies** — every borrowed theorem cited to a precise statement, so a reviewer can audit wha
- The ITCS "artifact" is the proof
- The public full version as the durable, verifiable record
- When a paper does have computational content
- What does NOT transfer from empirical-CS artifact tracks
- Verifiability checklist (the ITCS "artifact" pass)
- Output format
What does the itcs-artifact-evaluation skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.