Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
A skill your agent uses when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July…
MITAuto-check passed
Install Colm Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-review-process --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-review-process .claude/skills/colm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-review-process into .claude/skills/colm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-review-process --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-review-process .agents/skills/colm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-review-process into .agents/skills/colm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-review-process --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-review-process .cursor/skills/colm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-review-process into .cursor/skills/colm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-review-process --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-review-process .gemini/skills/colm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-review-process into .gemini/skills/colm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/colm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-review-process into .github/skills/colm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/colm-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-review-process into .opencode/skills/colm-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-review-process", 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
colm-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 720 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July…
- Works in 4 steps: The reviews' summary and score fields —… → The rebuttal's opening lines per… → Whether reviewers reacted to the… → …
- Reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release
- SKILL.md covers The 2026 pipeline (verified…, Who reviews you, and why it…, Rules that govern the… and Reading a COLM review packet, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Colm Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July decisions, reciprocal-reviewing obligations, the LLM-use rules for reviewers, and how a three-edition-old venue's norms differ from mature conferences.
Its SKILL.md is about 1.6k 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
- Reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release
- The May-June rebuttal window
- Reciprocal-reviewing obligations
- The LLM-use rules for reviewers
Example prompts
- “/colm-review-process”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- The reviews' summary and score fields — first impressions form here.
- The rebuttal's opening lines per reviewer — which is why conclusion-first
- Whether reviewers reacted to the rebuttal — an unanswered strong response
- The paper itself, selectively, where reviewers disagree.
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
Colm Review Process loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 720 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). 720 words, ~1,585 tokens.
Download SKILL.mdSave it as
.claude/skills/colm-review-process/SKILL.md (or your agent's skills folder).- name
- colm-review-process
- description
- Use when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July decisions, reciprocal-reviewing obligations, the LLM-use rules for reviewers, and how a three-edition-old venue's norms differ from mature conferences.
COLM Review Process
COLM runs a compact, single-cycle-per-year pipeline on OpenReview, and — because the venue is three editions old — its reviewing culture is still visibly under construction. Understanding both the posted mechanics and the young-venue dynamics is what lets authors time their effort correctly.
The 2026 pipeline (verified 2026-07-08)
| Phase | 2026 dates | Author-side reality |
|---|---|---|
| Abstract deadline | March 26 | Drives bidding and reviewer matching |
| Full paper deadline | March 31 | Submission freezes |
| Review writing | April - mid-May | Silence; nothing actionable |
| Reviews released | May 22 | Read-only day one; no same-day replies |
| Rebuttal | May 22 - June 8 | The 18-day window where effort pays |
| AC discussion + decisions | June - July 8 | Decisions posted July 8 |
| Camera-ready | August 7 | Accepted papers finalize |
| Conference | October 6-9, San Francisco | Main program Oct 6-8, workshops Oct 9 |
On this pack's access date — July 8, 2026 — the pipeline is at its decision moment:
rebuttals are closed and notifications land today. If you are triaging an outcome,
go directly to colm-camera-ready (accept) or the resubmission logic below
(reject).
Who reviews you, and why it feels different
Three structural facts shape COLM reviews:
- A self-selected LM reviewer pool. Everyone opted into a language-modeling
venue, so you will rarely justify why LMs matter — but you will face specialists
on contamination, harness quirks, and prompt sensitivity (
colm-experimentslists exactly what they check). - Reciprocal reviewing feeds the pool. COLM has per-submission and per-reviewer requirements, and any author with 4+ submissions is drafted automatically. Your reviewers are substantially this year's authors — practically minded, current, and reading many similar papers in a short window.
- Young-venue variance. With only two prior editions of precedent, calibration across reviewers is wider than at older venues: score meanings, appendix-reading habits, and rebuttal responsiveness vary. The rational response is to make the paper robust to the strictest plausible reviewer rather than tuning to an imagined average.
Rules that govern the conversation
- Double-blind, both directions — reviewers and ACs cannot see author names; authors cannot see reviewer names. Anything that de-anonymizes you mid-process is a self-inflicted wound.
- Code of Ethics scope — it explicitly covers reviewing and paper discussion, and reviewers are encouraged to raise potential violations they see in papers.
- LLM use in reviewing must be disclosed, whatever its size — the 2026 policy draws the reviewer line stricter than the author line. As an author, this cuts two ways: a review may lawfully have LLM assistance behind it, and a review that looks LLM-generated without engagement is a legitimate thing to flag to the AC in the rebuttal, factually and without accusation theater.
Show full SKILL.md (303 more words)Show less
Reading a COLM review packet
Sort reviewer claims into four bins before writing anything:
bin A misreading -> point to the page/table; cheapest wins first
bin B evidence gap -> runnable inside the 18-day window? do it
(cache-based analyses are fastest: colm-artifact-evaluation)
bin C scope disagreement -> reviewer wants a different paper; answer once,
crisply, and let the AC arbitrate
bin D correct hit -> concede, state the fix, thank them brieflyThe AC synthesizing the discussion is your real audience (colm-author-response
handles execution). Between June 8 and July 8 the process belongs to reviewers and
ACs; there is no author-visible discussion phase to work.
What the AC actually reads
Area chairs at a compact venue synthesize under time pressure, and their reading order shapes what survives:
- The reviews' summary and score fields — first impressions form here.
- The rebuttal's opening lines per reviewer — which is why conclusion-first
responses matter (
colm-author-response). - Whether reviewers reacted to the rebuttal — an unanswered strong response still counts, but an acknowledged one counts double; polite nudge-questions to silent reviewers are legitimate inside the window.
- The paper itself, selectively, where reviewers disagree.
Score arithmetic is a poor predictor at a young venue: with wide reviewer calibration variance and no published acceptance rate (待核实), a 5-5-8 with an engaged champion routinely beats a flat 6-6-6. Optimize for giving one reviewer the material to argue your case in the discussion you cannot see, rather than for moving every score by one point.
If the decision is a reject
- Mine the reviews for the bin-D items; they transfer to any venue.
- The calendar is forgiving: a July 8 COLM decision precedes the autumn ICLR deadline and the following spring's NeurIPS cycle, and COLM 2027's expected late-March deadline (待核实) is a natural 8-month runway for a genuine revision.
- Re-run
colm-topic-selectionhonestly — a common COLM reject pattern is a paper whose contribution was a task result wearing LM-analysis framing.
Volatile every edition
- All dates above; the phase structure itself (COLM has already adjusted process details in each of its three editions).
- Reviewer-form contents, score scales, and any acceptance-rate figures (none officially published; 待核实).
- Reciprocal-reviewing thresholds and enforcement.
Output format
[Phase today] <where the current cycle actually is — verify against colmweb.org/dates.html>
[Packet triage] A: <n> misreadings / B: <n> evidence gaps / C: <n> scope fights / D: <n> hits
[AC-facing issue] <the one point the meta-review will turn on>
[Deadline math] <days left in the relevant window>
[Plan] <respond / experiment / concede / escalate-to-AC items, in order>© 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 COLM-Skills/skills/colm-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Colm Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| Ejentum Reasoning Harnesssickn33/agentic-awesome-skills | 47k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nowait Reasoning Optimizerdavila7/claude-code-templates | 32k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| ColmnanoAgentTeam/research-claw | 293 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Recall Reasoningparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~758 | Automated safety check: Pass | MIT |
Similar skills
Ejentum Reasoning Harness
sickn33/agentic-awesome-skills
MCP server exposing four cognitive harness modes (reasoning, code, anti-deception, memory).
Nowait Reasoning Optimizer
davila7/claude-code-templates
Implements the NOWAIT technique for efficient reasoning in R1-style LLMs.
Colm
nanoAgentTeam/research-claw
COLM (Conference on Language Modeling) paper formatting — activate when the user wants COLM template setup, migration, or formatting/compilation fixes.
Recall Reasoning
parcadei/Continuous-Claude-v3
Search past reasoning for relevant decisions and approaches. An agent skill from parcadei/Continuous-Claude-v3.
- Official
Nv Reason Cxr
NVIDIA/skills
Used for command-shape or live NV-Reason-CXR chest X-ray reasoning smoke tests.
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 Colm Review Process
What does Colm Review Process do?
A skill your agent uses when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July…. Colm Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July decisions, reciprocal-reviewing obligations, the LLM-use rules for reviewers, and how a three-edition-old venue's norms differ from mature conferences.
When should I use Colm Review Process?
Colm Review Process fits situations like: reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release; the May-June rebuttal window; reciprocal-reviewing obligations; the LLM-use rules for reviewers.
How do I install Colm Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-review-process -a claude-code`. Or copy the skill folder (COLM-Skills/skills/colm-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colm-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Colm Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-review-process -a codex`. Or copy the skill folder (COLM-Skills/skills/colm-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colm-review-process in your project. Codex loads it when a task matches its description.
Can I use Colm Review Process 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 colm-review-process -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-review-process, .gemini/skills/colm-review-process, .github/skills/colm-review-process and .opencode/skills/colm-review-process in your project.
What does Colm Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Colm Review Process is instructions for the agent only.
Does Colm Review Process 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 Colm Review Process 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 Colm Review Process use?
Colm Review Process 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 Colm Review Process use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Colm Review Process?
Skills that share tags, products or a category with Colm Review Process: Deepseek Reason (ruvnet/ruflo, 74k stars), Ejentum Reasoning Harness (sickn33/agentic-awesome-skills, 47k stars), Nowait Reasoning Optimizer (davila7/claude-code-templates, 32k 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.
Who maintains Colm Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.