Review Triage Phase
prisma/orm
Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.
A skill your agent uses when writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May, running cache-based follow-up experiments inside the roughly…
MITAuto-check passed
Install Colm Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-author-response --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-author-response .claude/skills/colm-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-author-response into .claude/skills/colm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-author-response --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-author-response .agents/skills/colm-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-author-response into .agents/skills/colm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-author-response --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-author-response .cursor/skills/colm-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-author-response into .cursor/skills/colm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-author-response --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-author-response .gemini/skills/colm-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-author-response into .gemini/skills/colm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/colm-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-author-response into .github/skills/colm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/colm-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-author-response into .opencode/skills/colm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 651 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May, running cache-based follow-up experiments inside the roughly…
- Writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May
- SKILL.md covers Budget the eighteen days, The objections COLM reviewers…, Writing mechanics and Handling the difficult cases, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Running cache-based follow-up experiments inside the roughly two-and-a-half-week window
What it does
Colm Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May, running cache-based follow-up experiments inside the roughly two-and-a-half-week window, answering contamination and baseline-fairness objections with evidence, and writing for the area chair who decides in July.
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
- Writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May
- Running cache-based follow-up experiments inside the roughly two-and-a-half-week window
- Answering contamination and baseline-fairness objections with evidence
- Writing for the area chair who decides in July
Example prompts
- “/colm-author-response”
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 Author Response loads about 1.6k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 651 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). 651 words, ~1,568 tokens.
Download SKILL.mdSave it as
.claude/skills/colm-author-response/SKILL.md (or your agent's skills folder).- name
- colm-author-response
- description
- Use when writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May, running cache-based follow-up experiments inside the roughly two-and-a-half-week window, answering contamination and baseline-fairness objections with evidence, and writing for the area chair who decides in July.
COLM Author Response
In 2026 the COLM rebuttal ran May 22 to June 8: reviews and the response window opened the same day, giving about eighteen days between first sight of the reviews and the last word you get before the July 8 decision. A rebuttal in that geometry is a project with a plan, not a reply-all reflex.
Budget the eighteen days
days 1-2 read only; draft nothing; log every reviewer claim into the four bins
(misreading / evidence gap / scope fight / correct hit — colm-review-process)
days 3-9 run the winnable experiments — cache-based analyses first, single-GPU
or small-API-budget runs second; anything needing full retraining is
out of scope, say so plainly
days 10-13 draft one response per reviewer + a short common preamble for
cross-cutting points; every paragraph anchored to a page, table,
appendix section, or new number
days 14-16 co-author cold read: does each response open with its conclusion?
days 17-18 post with margin; OpenReview deadline-hour uploads are self-harmThe highest-yield experiments are the ones your artifact discipline pre-paid for: a
cached-responses archive lets you re-slice results, add a metric, or test a reviewer
hypothesis in hours without touching a model (colm-artifact-evaluation).
The objections COLM reviewers actually raise
These four LM-specific objections dominate borderline cases; each has a right and a wrong answer shape:
| Objection | Weak answer | Strong answer |
|---|---|---|
| "Benchmark is likely contaminated for these models." | "This benchmark is widely used." | Overlap analysis numbers, or dated-item split showing the effect survives on post-cutoff items |
| "Baselines are under-tuned; better prompting closes the gap." | "We used standard prompts." | The tried-ledger: k prompt variants per system, matched budgets; if the gap narrows, report the narrowed gap |
| "Results are on one model family; is this about LMs or about model X?" | "We expect it generalizes." | One added family inside the window, claim rescoped in the revision either way |
| "API model results won't reproduce." | "We used the public API." | Version strings + query dates already in App. A, plus commitment to release the response cache |
Notice the pattern: every strong answer is either evidence you can generate this week or a scope concession that makes the paper truer. Both move ACs; indignation moves nothing.
Writing mechanics
- Conclusion first, then support. "The gap survives decontamination (new Table R1): on items post-dating every model's cutoff, the effect is 7.9 points." Then the method sentence.
- Number new artifacts R1, R2, ... and reference them consistently; the AC skims all responses in one sitting and consistent labels are navigation.
- Quote the reviewer's own words for each point you answer — it prevents the "they dodged my question" reading — and answer the words, not a nastier paraphrase.
- Concede in the open. A visible "R2 is right; we overclaimed X and have rescoped to Y" is the single most credibility-generating sentence a rebuttal can contain.
- Stay anonymous. The discussion is inside double-blind: no lab names, no "in our previous paper," no links that resolve to you.
- Keep LLM-policy discipline — if a response experiment used LLM-based evaluation, it is disclosable under the same 2026 policy as the paper.
Show full SKILL.md (244 more words)Show less
Handling the difficult cases
- The low-engagement review (two lines, generic, possibly LLM-drafted without disclosure): respond substantively and briefly, then note factually in a comment visible to the AC that the review does not engage the paper's content. Flag, do not accuse.
- The scope-fight reviewer (wants a different paper): one crisp paragraph on why the paper's question is the right size, pointing at the venue's own genre — measurement and analysis papers are COLM's award lineage — then stop. Repetition reads as anxiety.
- The correct hit you cannot fix in eighteen days: say what the fix is, why it does not fit the window, and how the revision will scope claims meanwhile. ACs reward authors who can tell the difference between a flesh wound and a broken spine.
Per-reviewer response skeleton
One response per reviewer, same skeleton, filled with their words and your numbers:
Thank you for the careful reading. We address each point below.
> "<reviewer's sentence, quoted verbatim>"
<conclusion sentence with the page/table/new-artifact anchor>
<one or two support sentences — method, numbers, or the concession>
> "<next quoted point>"
...
Summary of changes committed for the revision:
1. <rescoped claim / new table R1 folded into §4 / added limitation>
2. ...
We believe the remaining disagreement (if any) is <one neutral sentence>,
which we leave to the AC's judgment.Length discipline: reviewers are reading many rebuttals in the same week you are writing yours. A response that fits on one screen per reviewer, with bolded conclusions and numbered artifacts, gets read twice; a 2,000-word essay gets skimmed once. If a point genuinely needs depth, put the depth in a clearly labeled final section so the main thread stays scannable.
After June 8
Nothing. The reviewer-AC discussion through the July 8 decision has no author
channel — resist the urge to post updates. Spend the month preparing both branches:
the camera-ready plan (due August 7 if accepted) and the resubmission map
(colm-review-process).
Output format
[Window] days remaining: <n> of ~18
[Per reviewer] R<k>: bins A/B/C/D counts + the one thing they must hear
[Experiment queue] <cache-based first, with owner and finish-by date>
[Concessions] <what gets conceded and the rescoped claim>
[AC preamble] <3-sentence summary of what changed during discussion>© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Colm Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| Triaging Issuespytorch/pytorch | 104k | — | ~4.2k | Automated safety check: Pass | Custom licence | |
| GSD Phase Discussionopen-gsd/gsd-core | 10k | 1 repos | ~1.5k | Automated safety check: Warn | MIT | |
| Distributed Triagepytorch/pytorch | 104k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT |
Similar skills
- Official
Triaging Issues
pytorch/pytorch
Triages GitHub issues by routing to oncall teams, applying labels, and closing questions.
GSD Phase Discussion
open-gsd/gsd-core
Asks adaptive questions about a project phase and records the decisions in a CONTEXT.md that later research and planning agents can act on without asking again.
Distributed Triage
pytorch/pytorch
Sub-triages issues in the oncall:distributed queue by assigning distributed module labels, routing to sub-oncalls, and marking triaged.
Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Rebuttal Response
M1n-n9/paper-lifecycle
Plan, triage, and write academic rebuttals and review responses.
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 Author Response
What does Colm Author Response do?
A skill your agent uses when writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May, running cache-based follow-up experiments inside the roughly…. Colm Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May, running cache-based follow-up experiments inside the roughly two-and-a-half-week window, answering contamination and baseline-fairness objections with evidence, and writing for the area chair who decides in July.
When should I use Colm Author Response?
Colm Author Response fits situations like: writing a COLM rebuttal in the OpenReview discussion phase — triaging reviews released in late May; running cache-based follow-up experiments inside the roughly two-and-a-half-week window; answering contamination and baseline-fairness objections with evidence; writing for the area chair who decides in July.
How do I install Colm Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-author-response -a claude-code`. Or copy the skill folder (COLM-Skills/skills/colm-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colm-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Colm Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-author-response -a codex`. Or copy the skill folder (COLM-Skills/skills/colm-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colm-author-response in your project. Codex loads it when a task matches its description.
Can I use Colm Author Response 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-author-response -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-author-response, .gemini/skills/colm-author-response, .github/skills/colm-author-response and .opencode/skills/colm-author-response in your project.
What does Colm Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Colm Author Response is instructions for the agent only.
Does Colm Author Response 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 Author Response 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 Author Response use?
Colm Author Response 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 Author Response 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 Author Response?
Skills that share tags, products or a category with Colm Author Response: Review Triage Phase (prisma/orm, 48k stars), Triaging Issues (pytorch/pytorch, 104k stars), GSD Phase Discussion (open-gsd/gsd-core, 10k stars) and Distributed Triage (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Colm Author Response?
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.