colt-artifact-evaluation
Use when deciding what evidence package a COLT (Conference on Learning Theory) paper needs, given that COLT runs no artifact-evaluation track or badges — the proof appendix is the artifact. Covers proof-verification passes, optional code companions for numerics, formalization aids, and post-acceptance release of scripts.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-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.
# COLT Artifact Evaluation First, the honest framing: **COLT has no artifact-evaluation track, no artifact badges, and no code-submission requirement.** Nothing of the kind appears in the COLT 2026 Call for Papers or conference pages (checked 2026-07-08). Do not import NeurIPS/ICML-style artifact checklists into a COLT plan; they answer questions this venue does not ask. What replaces artifact review at COLT is the referee's line-by-line reading of your proofs — so this skill treats the proof appendix as the artifact and tells you how to make it verifiable. ## What replaces the artifact track | At an artifact-track venue | The COLT counterpart | Who "evaluates" it | |---|---|---| | Code repository with run scripts | Complete proofs in the same PDF | Reviewers, line by line | | Reproducibility checklist form | Explicit assumption and constant bookkeeping | Reviewers and the AC | | Artifact badge | Community trust that the argument closes | Readers citing the bound | | Dockerized environment | Self-contained lemma dependencies | Anyone re-deriving the result | | Benchmark seeds and configs | Scripts for illustrative numerics, if any | Discretionary reader interest | ## The proof appe
- What replaces the artifact track
- The proof appendix as artifact
- A verification ledger you can actually run
- When code exists anyway
- Worked vignette: packaging a bandit paper's evidence
- Post-acceptance release checklist
- What not to do
- Cycle-volatility warnings
- Output format
What does the colt-artifact-evaluation skill do?
Use when deciding what evidence package a COLT (Conference on Learning Theory) paper needs, given that COLT runs no artifact-evaluation track or badges — the proof appendix is the artifact. Covers proof-verification passes, optional code companions for numerics, formalization aids, and post-acceptance release of scripts.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-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.