cikm-workflow
Use when planning a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-workflow --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.
# CIKM Workflow CIKM runs a spring-submission, autumn-meeting year. The verified 2026 shape (source map, 2026-07-08): full-paper abstract May 16 and paper May 23; short, resource, and demo abstracts May 30 and papers June 6; notification for the listed tracks August 7; camera-ready August 20; conference November 7-11 in Rome — every cutoff 11:59 PM AoE. Replace these anchors with the current important-dates page before acting on any of them; CIKM re-issues its calendar annually under a new host committee. ## Where the 2026 cycle stands now As of 2026-07-08 all CIKM 2026 submission gates have closed. A team holding a submission is in the review-wait phase; a team without one is planning CIKM 2027. That split defines two working modes: **Mode A — paper under review (July → August 7).** Do the work whose absence hurts in August: keep the experimental environment runnable rather than dismantled, pre-draft the camera-ready fixes you already know about, prepare the public artifact that the anonymized submission could not name, and hold arXiv or publicity moves that conflict with what was declared on the EasyChair form. If a response mechanism materializes (unconfirmed for 2026 — 待核实), `c
- Where the 2026 cycle stands now
- Backward plan to a May full-paper gate
- Multi-track coordination
- Role assignments that prevent CIKM-specific failures
- Cycle-verification ritual
- Fallback ring
- The conference itself is a work object
- Annual rhythm, compressed
- Output format
What does the cikm-workflow skill do?
Use when planning a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-workflow --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.