Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
A skill your agent uses when deciding whether language-model research belongs at COLM or should route to ACL/EMNLP, ICLR, NeurIPS, ICML, or a workshop — applying the object-of-study test, matching…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-topic-selection --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/COLM-Skills/skills/colm-topic-selection .claude/skills/colm-topic-selection && 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 "colm-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-topic-selection into .claude/skills/colm-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-topic-selection", 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/COLM-Skills/skills/colm-topic-selectionType 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 colm-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-topic-selection --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/COLM-Skills/skills/colm-topic-selection .agents/skills/colm-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "colm-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-topic-selection into .agents/skills/colm-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-topic-selection", 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 colm-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-topic-selection --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/COLM-Skills/skills/colm-topic-selection .cursor/skills/colm-topic-selection && 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 "colm-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-topic-selection into .cursor/skills/colm-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-topic-selection", 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 COLM-Skills/skills/colm-topic-selection--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 colm-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-topic-selection --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/COLM-Skills/skills/colm-topic-selection .gemini/skills/colm-topic-selection && 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 "colm-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-topic-selection into .gemini/skills/colm-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-topic-selection", 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 colm-topic-selectionInstalls 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 colm-topic-selection -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/COLM-Skills/skills/colm-topic-selection .github/skills/colm-topic-selection && 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 "colm-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-topic-selection into .github/skills/colm-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-topic-selection", 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 colm-topic-selection -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 colm-topic-selection --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/COLM-Skills/skills/colm-topic-selection .opencode/skills/colm-topic-selection && 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 "colm-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-topic-selection into .opencode/skills/colm-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-topic-selection", 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.
colm-topic-selectionA skill your agent uses when deciding whether language-model research belongs at COLM or should route to ACL/EMNLP, ICLR, NeurIPS, ICML, or a workshop — applying the object-of-study test, matching…
Colm Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether language-model research belongs at COLM or should route to ACL/EMNLP, ICLR, NeurIPS, ICML, or a workshop — applying the object-of-study test, matching against COLM's CFP lanes (training, data, evaluation, inference, safety), and weighing the trade-offs of a young venue before writing begins.
Its SKILL.md is about 1.8k 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Colm Topic Selection loads about 1.8k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 816 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 816 words, ~1,775 tokens.
.claude/skills/colm-topic-selection/SKILL.md (or your agent's skills folder).Almost every LM paper could be sent to five venues; COLM exists because the authors of such papers kept finding that none of the five was actually about their question. This skill decides whether your project is one of those papers. Run it before the first draft — the March abstract deadline punishes late routing changes.
Ask one question: is the language model the thing being studied, or the tool doing the studying?
A useful second probe: delete the specific model names from your abstract. If the claims survive as statements about language modeling (a training dynamic, a data effect, an evaluation artifact, an inference trade-off), COLM fits. If what remains is a task result, it does not.
| Your project's center of gravity | Better home | Why not COLM |
|---|---|---|
| A training method, data effect, evaluation artifact, inference algorithm, or safety property of LMs | COLM | — |
| A linguistic phenomenon, an NLP task, an annotation resource, a multilingual application | ACL or EMNLP | The finding is about language or a task, not about the model class |
| A representation-learning idea tested beyond language (vision, RL, graphs) | ICLR | Generality is the point; the LM is one instance |
| A learning-theoretic result, an optimizer, a probabilistic method where LMs are one benchmark | NeurIPS or ICML | The LM is an experiment, not the subject |
| A serving/systems contribution (kernels, scheduling, memory) with modeling untouched | MLSys or a systems venue | Reviewers there can evaluate throughput claims properly |
| An early-stage probe, negative result, or position piece not ready for archival review | A COLM or *CL workshop | Archival COLM review will demand completeness the work does not have yet |
Boundary cases worth naming: multimodal models fit COLM when the language model is central to the question (a 2025 Outstanding Paper is a VLM-failure analysis); agents and tool use fit when the paper studies the LM's behavior in the loop rather than ships a product; benchmark papers fit when the benchmark comes with a validity argument, not just difficulty.
The CFP's non-exhaustive topics cluster into lanes; name yours before framing:
The award lineage (see resources/exemplars/library.md) tilts toward measurement,
analysis, and evaluation critique: five of the eight Outstanding Papers from the
first two editions study how we know what LMs do. A single leaderboard table is a
weak spine here.
Choosing a three-edition-old conference is itself a decision. Weigh it explicitly:
FOR COLM AGAINST (for this project)
- reviewer pool self-selected for LM - no long citation tail yet; some
work; less "why not test on vision?" committees still ask "is COLM top-tier?"
- award lineage rewards analysis and - norms shift per edition (policies,
measurement, not only SOTA dates, format have all moved 2024→2026)
- one cycle per year, October venue, - one cycle per year: a reject costs 12
proceedings free and open on months at this venue
OpenReviewThe single-cycle point cuts both ways: COLM's March-to-July pipeline sits neatly between the ICLR (autumn) and NeurIPS (spring) deadlines, which is why many groups now treat it as the natural resubmission target for strong-but-rejected LM papers — plan the fallback chain, not just the first shot.
A group builds a retrieval-augmented clinical-notes summarizer and observes that retrieved passages change the model's factuality unevenly across note types. Three papers hide in this project:
The exercise generalizes: the COLM-shaped paper inside a project is usually found by asking what you now know about language models that you did not know before the project — then testing whether that knowledge survives on models you did not build the system around.
colm-experiments).[Routing] COLM / ACL-EMNLP / ICLR / NeurIPS-ICML / systems venue / workshop first
[Object-of-study test] passes / fails — <what the LM is in this project>
[CFP lane] training / data / evaluation / inference / safety / interpretability
[Nearest COLM neighbors] <two accepted papers>
[Young-venue risk accepted] yes / no — <one-line reason>
[Next action] <framing fix, evidence fix, or venue switch>© 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
Just SKILL.md in COLM-Skills/skills/colm-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Colm Topic Selection 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 |
|---|---|---|---|---|---|---|
| Colm Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 576 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| ColmnanoAgentTeam/research-claw | 293 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None |
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
nanoAgentTeam/research-claw
COLM (Conference on Language Modeling) paper formatting — activate when the user wants COLM template setup, migration, or formatting/compilation fixes.
itwanger/toBeBetterJavaer
知识星球主题管理:搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论(楼中楼)、回答提问、删除主题;通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
aipoch/medical-research-skills
Generate ~5 actionable research topic recommendations by querying PubMed E-utilities; use when a user provides a research direction/constraints and needs evidence-backed topic ideas quickly.
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…
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…
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…
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…
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…
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…
A skill your agent uses when deciding whether language-model research belongs at COLM or should route to ACL/EMNLP, ICLR, NeurIPS, ICML, or a workshop — applying the object-of-study test, matching…. Colm Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether language-model research belongs at COLM or should route to ACL/EMNLP, ICLR, NeurIPS, ICML, or a workshop — applying the object-of-study test, matching against COLM's CFP lanes (training, data, evaluation, inference, safety), and weighing the trade-offs of a young venue before writing begins.
Colm Topic Selection fits situations like: deciding whether language-model research belongs at COLM; should route to ACL/EMNLP; A workshop — applying the object-of-study test; matching against COLMs CFP lanes (training.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-topic-selection -a claude-code`. Or copy the skill folder (COLM-Skills/skills/colm-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colm-topic-selection in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-topic-selection -a codex`. Or copy the skill folder (COLM-Skills/skills/colm-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colm-topic-selection in your project. Codex loads it when a task matches its description.
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 colm-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/colm-topic-selection, .gemini/skills/colm-topic-selection, .github/skills/colm-topic-selection and .opencode/skills/colm-topic-selection in your project.
SKILL.md names no scripts, command-line tools or credentials: Colm Topic Selection is instructions for the agent only.
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.
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.
Colm Topic Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Colm Topic Selection: Topics (ZimoLiao/scholaraio, 576 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Bestblogs Topic (ginobefun/BestBlogs, 4k stars) and Colm (nanoAgentTeam/research-claw, 293 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.