colm-related-work
Use when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-related-work --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.
# COLM Related Work The LM literature moves faster than any archival process: the work you must position against is substantially on arXiv, some of it appeared after your experiments finished, and some "well-known results" are blog posts. A COLM related-work section is therefore an exercise in *versioned honesty* — saying precisely what existed, where, and when, without pretending the field is tidier than it is. ## Triage the literature into lanes Cover each lane that touches your claim; reviewers at this venue are typically active in two or three of them and will notice a missing lane immediately: | Lane | What to position against | Typical miss | |---|---|---| | Method lineage | The 2-4 papers your technique descends from | Citing a survey instead of the source | | Phenomenon reports | Prior observations of the effect you study, incl. analysis papers | Ignoring negative or contradictory reports | | Evaluation infrastructure | The benchmarks/harnesses you use or compete with | Treating a benchmark as neutral ground rather than citable, criticizable work | | Model artifacts | The model families your claims are scoped to | Citing a company blog when a technical report exists (or vic
- Triage the literature into lanes
- arXiv status honesty
- Concurrent work: the protocol
- Positioning moves that work here
- A positioning micro-example
- Double-blind self-citation
- Pre-submission citation audit
- Output format
What does the colm-related-work skill do?
Use when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-related-work --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.