Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
Agent skill
Colt Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses 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…
MITAuto-check passed
Install Colt Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colt-artifact-evaluation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/COLT-Skills/skills/colt-artifact-evaluation .claude/skills/colt-artifact-evaluation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "colt-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluation into .claude/skills/colt-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colt-artifact-evaluation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colt-artifact-evaluation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/COLT-Skills/skills/colt-artifact-evaluation .agents/skills/colt-artifact-evaluation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "colt-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluation into .agents/skills/colt-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colt-artifact-evaluation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colt-artifact-evaluation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/COLT-Skills/skills/colt-artifact-evaluation .cursor/skills/colt-artifact-evaluation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "colt-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluation into .cursor/skills/colt-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colt-artifact-evaluation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path COLT-Skills/skills/colt-artifact-evaluation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colt-artifact-evaluation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/COLT-Skills/skills/colt-artifact-evaluation .gemini/skills/colt-artifact-evaluation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "colt-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluation into .gemini/skills/colt-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colt-artifact-evaluation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colt-artifact-evaluationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/COLT-Skills/skills/colt-artifact-evaluation .github/skills/colt-artifact-evaluation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "colt-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluation into .github/skills/colt-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colt-artifact-evaluation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colt-artifact-evaluation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/COLT-Skills/skills/colt-artifact-evaluation .opencode/skills/colt-artifact-evaluation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "colt-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLT-Skills/skills/colt-artifact-evaluation into .opencode/skills/colt-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colt-artifact-evaluation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
colt-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 790 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Deciding what evidence package a COLT (Conference on Learning Theory) paper needs
- SKILL.md covers What replaces the artifact track, The proof appendix as artifact, A verification ledger you can… and When code exists anyway, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Given that COLT runs no artifact-evaluation track
What it does
Colt Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Deciding what evidence package a COLT (Conference on Learning Theory) paper needs
- Given that COLT runs no artifact-evaluation track
- Badges — the proof appendix is the artifact
Example prompts
- “/colt-artifact-evaluation”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Colt Artifact Evaluation loads about 1.7k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 790 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 790 words, ~1,670 tokens.
Download SKILL.mdSave it as
.claude/skills/colt-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- colt-artifact-evaluation
- description
- 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.
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 appendix as artifact
A COLT artifact plan is a verification plan:
- Map every theorem to its full proof location and confirm no step says "similarly" or "standard" where the step is neither.
- Track constants explicitly through the proof chain; a constant that changes value between Lemma 4 and Theorem 1 is the theory equivalent of a failing test.
- List every external result invoked (concentration inequalities, minimax theorems, reductions) with a precise citation including theorem number, and check that your setting satisfies that result's hypotheses — the most common hidden bug.
- Have a coauthor who did not write a proof verify it cold, logging time-to-verify. Sections that take a fresh expert more than an hour per page need restructuring before a time-pressed referee sees them.
A verification ledger you can actually run
Keep a machine-checkable inventory next to the LaTeX source:
# proof-ledger.txt — one line per claim, updated at every freeze
THM1 full proof App.B | deps: LEM3, LEM4, [BLM13 Thm 6.2] | verified: RG 2026-01-12
THM2 full proof App.C | deps: THM1, LEM5 | verified: none <-- BLOCKER
LEM3 full proof App.B.1| deps: none | verified: SW 2026-01-08
LEM4 sketch only | deps: [SSBD14 Lemma 26.8] | verified: n/a <-- expand
COR1 two lines in body | deps: THM2 | verified: with THM2The rule: no submission while any load-bearing line reads verified: none. This
ledger, not a badge, is COLT-grade artifact discipline.
When code exists anyway
Many COLT papers include small numerical illustrations, and some results come with reference implementations. Norms for those:
- The 2026 CFP imposed no code-upload mechanism; if you want reviewers to see code, it must be referenced in the PDF via an anonymized link or included as appendix pseudocode. Anonymize repository history and hosting if you link during review.
- Keep illustration scripts tiny and dependency-light: one file that regenerates the figure from a fixed seed is worth more than a framework.
- Formal-verification companions (Lean or Coq mechanizations of a key lemma) are an emerging but optional credibility signal in the theory community — mention one if it exists, never fake partial formalization as full.
- After acceptance, publish scripts in a citable repository and link them from the arXiv version, since the PMLR PDF is fixed at camera-ready.
Show full SKILL.md (329 more words)Show less
Worked vignette: packaging a bandit paper's evidence
A hypothetical submission proves a $O(\sqrt{TK})$ regret upper bound and a matching lower bound, and includes one figure simulating both on the lower-bound instance. Its artifact plan under COLT rules:
- The upper-bound proof (App. B) and lower-bound construction (App. C) are the artifacts; both enter the ledger with named verifiers and dates.
- The external-results audit lists the two concentration inequalities used, each with source theorem number and a one-line check that boundedness hypotheses hold.
- The figure's generating script (40 lines, numpy only) is described procedurally in App. D — instance parameters, seed, 100 replications — because no upload channel exists; the script itself is queued for a public repository at acceptance.
- Nothing else ships. No environment files, no hardware table, no checklist — those belong to venues that ask for them.
Post-acceptance release checklist
When code or mechanization exists, release it once anonymity ends:
| Item | Standard | Why it matters at COLT |
|---|---|---|
| Repository | Public, licensed, tagged at camera-ready state | The PMLR PDF is frozen; the repo carries updates |
| Link placement | arXiv version + PMLR "code" field if offered | Theory readers find papers via arXiv first |
| Script scope | Regenerates each figure from a fixed seed | Matches the illustration claims exactly |
| Mechanized proofs | State coverage precisely (which lemmas, which axioms) | Partial formalization overstated reads as spin |
What not to do
- Do not pad a COLT submission with an "artifact appendix" of configs and hardware tables for a paper whose claims are theorems; reviewers read it as misunderstanding the venue.
- Do not promise a code release as a substitute for a complete proof — no reviewer here will trade executable evidence for a gap.
- Do not cite artifact badges from other venues as evidence of correctness.
Cycle-volatility warnings
- If a future COLT cycle introduces any code or artifact mechanism, the CFP will say so explicitly; absence in 2026 does not bind later years (待核实 each cycle).
- Anonymous-linking rules during review follow the current anonymity policy, which is re-issued yearly.
Output format
[Artifact reality check] proofs are the artifact / paper also ships numerics
[Verification ledger] complete / gaps at <claims>
[External results audit] <result -> hypotheses checked?>
[Code companion] none needed / anonymized link / post-acceptance release
[Blocking item] <the one unverified load-bearing claim>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in COLT-Skills/skills/colt-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Colt Artifact Evaluation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Colt Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 | |
| LLM Evaluationdavila7/claude-code-templates | 33k | 12 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Agent Evaluationsickn33/agentic-awesome-skills | 47k | 1 repos | ~2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Artifacts Builder
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
LLM Evaluation
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
- Official
Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Agent Evaluation
sickn33/agentic-awesome-skills
Evaluate agent behavior with versioned cases and explicit verifiers.
Ccs Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging ACM CCS artifacts for the artifact-evaluation committee and the ACM badges — Artifacts Available, Artifacts Evaluated Functional, Artifacts Evaluated Reusable…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Colt Artifact Evaluation
What does Colt Artifact Evaluation do?
A skill your agent uses 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…. Colt Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Colt Artifact Evaluation?
Colt Artifact Evaluation fits situations like: deciding what evidence package a COLT (Conference on Learning Theory) paper needs; given that COLT runs no artifact-evaluation track; badges — the proof appendix is the artifact.
How do I install Colt Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a claude-code`. Or copy the skill folder (COLT-Skills/skills/colt-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colt-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Colt Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a codex`. Or copy the skill folder (COLT-Skills/skills/colt-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colt-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Colt Artifact Evaluation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colt-artifact-evaluation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/colt-artifact-evaluation, .gemini/skills/colt-artifact-evaluation, .github/skills/colt-artifact-evaluation and .opencode/skills/colt-artifact-evaluation in your project.
What does Colt Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Colt Artifact Evaluation is instructions for the agent only.
Does Colt Artifact Evaluation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Colt Artifact Evaluation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Colt Artifact Evaluation use?
Colt Artifact Evaluation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Colt Artifact Evaluation use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Colt Artifact Evaluation?
Skills that share tags, products or a category with Colt Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Artifacts Builder (nexu-io/open-design, 100k stars), LLM Evaluation (davila7/claude-code-templates, 33k stars) and Web Artifacts Builder (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Colt Artifact Evaluation?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.