Agent skill · Data & Analytics

colm-artifact-evaluation

Use when packaging the artifacts of a COLM paper — model weights, training data, prompts, evaluation sets, and cached model outputs — for anonymous review and public post-acceptance release, navigating licenses, API terms-of-service limits, and the absence of a formal COLM artifact track.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-artifact-evaluation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: COLM-Skills/skills/colm-artifact-evaluation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# COLM Artifact Evaluation COLM had no formal artifact-evaluation track verifiable for the 2026 cycle (checked 2026-07-08; 待核实 each edition). That absence does not lower the bar — it moves the audit into ordinary review, where artifact quality influences scores without a rubric to appeal to. Package as if a skeptical reviewer will spend ten minutes with your materials, because at this venue one usually will. ## The COLM artifact taxonomy LM papers produce artifact types with very different release mechanics; inventory yours before deciding anything: | Artifact | Review-time form | Release-time form | Blocking question | |---|---|---|---| | Code (training/eval) | Anonymized repo or supplement ZIP | Public repo, tagged release | Does one command reproduce one table? | | Prompts | Verbatim appendix + files in package | Same, public | Exact strings, incl. system prompts? | | Fine-tuned weights | Usually described, not uploaded (size) | Model hub upload with model card | Does the *base* model's license permit derivative release? | | Training/eval data you built | Anonymized sample + datasheet | Full release with license | Any personal data, scraped ToS conflicts, or annotator-privacy is

What's inside
Steps it walks through
  1. The COLM artifact taxonomy
  2. One-command reproduction
  3. Anonymous review packaging
  4. Datasheets for anything you release
  5. Post-acceptance release sequence
  6. The ten-minute reviewer walkthrough
  7. Longevity: the two-year test
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the colm-artifact-evaluation skill do?

Use when packaging the artifacts of a COLM paper — model weights, training data, prompts, evaluation sets, and cached model outputs — for anonymous review and public post-acceptance release, navigating licenses, API terms-of-service limits, and the absence of a formal COLM artifact track.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-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.

Keep going