colm-author-response
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-author-response --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 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 ```text 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-harm ``` The 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 ho
- Budget the eighteen days
- The objections COLM reviewers actually raise
- Writing mechanics
- Handling the difficult cases
- Per-reviewer response skeleton
- After June 8
- Output format
What does the colm-author-response skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-author-response --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.