Google Calendar
codewhale-hq/Codewhale
Reads schedules, checks free and busy time, and creates or updates Google Calendar events through the Calendar API, with care around invites and recurring series.
A skill your agent uses when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July…
MITAuto-check passed
Install Colm Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-workflow --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-workflow .claude/skills/colm-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-workflow into .claude/skills/colm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-workflow --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-workflow .agents/skills/colm-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-workflow into .agents/skills/colm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-workflow --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-workflow .cursor/skills/colm-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-workflow into .cursor/skills/colm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills colm-workflow --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-workflow .gemini/skills/colm-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-workflow into .gemini/skills/colm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/colm-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-workflow into .github/skills/colm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/colm-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/COLM-Skills/skills/colm-workflow into .opencode/skills/colm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "colm-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 778 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July…
- August camera-ready
- SKILL.md covers The 2026 cycle as a template…, Backward plan from a March…, Coordination artifacts for a… and Slotting COLM into the venue…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- October conference
What it does
Colm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.
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.
When your agent uses it
- August camera-ready
- October conference
- Coordinating co-authors
- Reciprocal-reviewing duties
Example prompts
- “/colm-workflow”
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 Workflow loads about 1.8k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 778 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). 778 words, ~1,802 tokens.
Download SKILL.mdSave it as
.claude/skills/colm-workflow/SKILL.md (or your agent's skills folder).- name
- colm-workflow
- description
- Use when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.
COLM Workflow
COLM gives you exactly one shot per year: one deadline (late March in 2026), one rebuttal, one decision (early July), one October stage. Campaign planning is therefore mostly backward induction from March — and, because LM projects burn compute and involve many hands, the critical path is usually GPUs and co-author availability, not writing.
The 2026 cycle as a template (all dates verified 2026-07-08)
| Date (2026) | Event | What must already be true |
|---|---|---|
| February | OpenReview opens | Profiles current for every author |
| March 26 | Abstract deadline | Real abstract; reciprocal reviewer chosen |
| March 31 | Full paper deadline | Frozen claims, pinned evidence, anonymized package |
| May 22 | Reviews released | Response owners pre-assigned; cache warm |
| May 22 - June 8 | Rebuttal | ~18 days; plan in colm-author-response |
| July 8 | Decisions | Both branches pre-planned |
| August 7 | Camera-ready | Public artifacts ready to ship simultaneously |
| October 6-9 | Conference, San Francisco | Presenter, visa, poster all handled |
Live-phase note: on this pack's access date — 2026-07-08 — the 2026 cycle is at
decision day. If that is you, jump to colm-camera-ready or the reject branch in
colm-review-process. If you are planning fresh work, you are planning COLM
2027: dates unannounced (待核实), with late March the reasonable working
assumption to be corrected the moment colmweb.org posts the real calendar.
Backward plan from a March deadline
T-20w (Nov) route the project (colm-topic-selection); if COLM, freeze the
one-sentence finding and the evaluation design — contamination
handling decided NOW, not retrofitted (colm-experiments)
T-16w (Dec) compute budget locked: training runs, eval sweeps, API spend;
book cluster time — March demand is when everyone else trains too
T-12w (Jan) main experiments running; pinning discipline live from day one
(colm-reproducibility); related-work lanes assigned (colm-related-work)
T-8w (Feb) full draft v1; internal red-team review against the four attacks;
OpenReview profiles + reciprocal-reviewer map done when the venue opens
T-4w (Mar) freeze claims; kill or hedge anything unverified; build the
anonymized package (colm-supplementary)
T-1w abstract in (Mar 26); mechanical sweeps; co-author policy items
T-0 (Mar 31) upload; re-download; read coldTwo LM-specific scheduling truths: evaluation takes as long as training once you include prompt-sensitivity runs, multiple families, and CI-grade sampling — budget it explicitly; and the February cluster crunch is real — every LM group targets the same spring deadlines, so compute reserved in December is worth double compute begged for in March.
Coordination artifacts for a multi-author LM paper
- A claims ledger — every claim, its owner, its evidence status (verified / running / at-risk). The T-4w freeze operates on this ledger.
- A reciprocal-reviewing map — who is nominated for which submission across the whole group's March portfolio; the same person cannot cover two papers, and anyone on 4+ submissions is drafted into the pool regardless.
- A policy checklist per co-author — OpenReview profile, Code of Ethics acknowledgment, LLM-usage disclosure input. These are the tasks only their owners can do, which is what makes them deadline risks.
- A decision-tree memo written before July: if accept → who runs camera-ready and the artifact release in the August-vacation month; if reject → target venue (autumn ICLR? next NeurIPS? COLM 2027?) and which review criticisms gate the resubmission.
Slotting COLM into the venue year
COLM's March deadline sits after the ICLR decision (winter) and before the NeurIPS
deadline (spring), which creates the standard LM-group rotation: ICLR reject →
strengthen → COLM; COLM reject (July) → strengthen → ICLR (autumn). Use the
rotation deliberately, with colm-topic-selection as the gate each time — a paper
bouncing between venues unchanged is not a strategy, it is a queue.
Show full SKILL.md (329 more words)Show less
The small-lab variant
The plan above assumes a group; a two-person or advisor-student team runs the same calendar with different bottlenecks:
| Constraint | Adaptation |
|---|---|
| No compute reserve | Anchor claims on open-weight models small enough to rerun; design the paper so API spend is evaluation-only and capped |
| One person does everything | The T-4w claim freeze becomes T-6w; the last month is writing and packaging only |
| No internal red team | Trade cold reads with a neighboring group in February — the four-attacks review (colm-experiments) does not require seniority, only distance |
| Advisor bandwidth | Book the advisor's full-draft read for a named week in February; "when it's ready" means March 29 |
| Single submission | Reciprocal-reviewing is simpler (one nominee) but the 4+ auto-draft rule may still catch a prolific advisor — check |
The compensating advantage: small teams pivot. If January experiments kill the framing, a two-person team can re-route to a workshop or the autumn cycle without a committee meeting — take that exit deliberately rather than limping to March.
Failure patterns this calendar produces
- Evaluation designed after training finishes → contamination handling becomes an apology instead of a design (start it at T-20w).
- Abstract stub on March 26 → bad reviewer matching that no rebuttal can fix.
- Rebuttal window discovered at review-release → the 18 days start with three days of panic; pre-assign owners in March.
- August camera-ready month colliding with vacations → name the owner in July.
Workshop track as a parallel lane
COLM's workshop day (October 9 in 2026) runs its own later calendar — in 2026, workshop proposals were due April 14, and contributed workshop papers had a suggested June 23 deadline with mandatory notification by July 24. For work that misses March or is not archival-ready, the workshop lane keeps the project inside the COLM community's October gathering without burning the main-track shot — and a workshop audience in October is the best red team a March 2027 main-track version will ever get. Check each workshop's own pages; their deadlines and archival status vary (待核实 per workshop).
Output format
[Target cycle] COLM 202X — deadline <confirmed / working assumption 待核实>
[Phase now] <planning / experiments / freeze / submitted / rebuttal / decision / camera-ready>
[Critical path] <compute / evaluation / writing / co-author policy items>
[Ledger health] claims verified <k>/<n>; at-risk: <items>
[Group constraints] reciprocal map ▢ 4+-submission authors: <names>
[Next milestone] <date — what must be true>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Colm Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Google Calendarcodewhale-hq/Codewhale | 41k | — | ~512 | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 275k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Team Calendarsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Gws Calendar Agendagoogleworkspace/cli | 31k | 1 repos | ~389 | Automated safety check: Pass | Apache-2.0 | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
Team Calendar
sickn33/agentic-awesome-skills
Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module.
Gws Calendar Agenda
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Campaign Cleaner Automation
ComposioHQ/awesome-claude-skills
Automate Campaign Cleaner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
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 Workflow
What does Colm Workflow do?
A skill your agent uses when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July…. Colm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.
When should I use Colm Workflow?
Colm Workflow fits situations like: august camera-ready; october conference; coordinating co-authors; reciprocal-reviewing duties.
How do I install Colm Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-workflow -a claude-code`. Or copy the skill folder (COLM-Skills/skills/colm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/colm-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Colm Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-workflow -a codex`. Or copy the skill folder (COLM-Skills/skills/colm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/colm-workflow in your project. Codex loads it when a task matches its description.
Can I use Colm Workflow 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-workflow -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-workflow, .gemini/skills/colm-workflow, .github/skills/colm-workflow and .opencode/skills/colm-workflow in your project.
What does Colm Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Colm Workflow is instructions for the agent only.
Does Colm Workflow 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 Workflow 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 Workflow use?
Colm Workflow 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 Workflow use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Workflow?
Skills that share tags, products or a category with Colm Workflow: Google Calendar (codewhale-hq/Codewhale, 41k stars), Marketing Campaign (affaan-m/ECC, 275k stars), Team Calendar (sickn33/agentic-awesome-skills, 47k stars) and Gws Calendar Agenda (googleworkspace/cli, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Colm Workflow?
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.