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 CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference…
MITAuto-check passed
Install Cikm Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-workflow .claude/skills/cikm-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 "cikm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-workflow into .claude/skills/cikm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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/CIKM-Skills/skills/cikm-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 cikm-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-workflow .agents/skills/cikm-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 "cikm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-workflow into .agents/skills/cikm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-workflow .cursor/skills/cikm-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 "cikm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-workflow into .cursor/skills/cikm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 CIKM-Skills/skills/cikm-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 cikm-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-workflow .gemini/skills/cikm-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 "cikm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-workflow into .gemini/skills/cikm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-workflow .github/skills/cikm-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 "cikm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-workflow into .github/skills/cikm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-workflow .opencode/skills/cikm-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 "cikm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-workflow into .opencode/skills/cikm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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
cikm-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 862 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 CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference…
- Planning a CIKM project calendar across the May abstract/paper gates
- SKILL.md covers Where the 2026 cycle stands now, Backward plan to a May…, Multi-track coordination and Role assignments that prevent…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- June short-track gates
What it does
Cikm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.7k 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
- Planning a CIKM project calendar across the May abstract/paper gates
- June short-track gates
- August notification and camera-ready
- The November conference
Example prompts
- “/cikm-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
Cikm Workflow loads about 1.7k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 862 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). 862 words, ~1,729 tokens.
Download SKILL.mdSave it as
.claude/skills/cikm-workflow/SKILL.md (or your agent's skills folder).- name
- cikm-workflow
- description
- 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.
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 — 待核实), cikm-author-response takes over on short notice.
Mode B — aiming at the next edition. The May/November rhythm is a planning prior only until the 2027 site posts dates. Build backward from a provisional mid-May gate and treat the abstract deadline as the real freeze: title, abstract, author list — authorship is frozen there under the ACM policy — and the track choice.
Backward plan to a May full-paper gate
| Weeks before the paper deadline | Milestone for an IR/mining/KM paper |
|---|---|
| 10 | Track chosen (cikm-topic-selection); datasets and baselines secured |
| 7 | Core results in; mechanism ablations scheduled |
| 5 | Draft in ACM two-column format — appendices count inside the budget, so measure now |
| 3 | Internal read by someone from the other community lane the paper claims |
| 1.5 | Abstract gate: final title/abstract/authors/track in EasyChair |
| 1 | Anonymity sweep, GenAI Usage Disclosure section written, reviewer nomination assigned |
| 0 | PDF upload; declared arXiv status matches reality |
Two CIKM-specific traps in that table. First, the abstract deadline is one week before the paper deadline and freezes authorship — late collaborator additions are formally barred afterward. Second, the appendix-inside-the-limit rule means the "we'll move it to the appendix" reflex saves nothing; overflow must move to the cited artifact or be cut.
Multi-track coordination
Groups often carry a full paper, a resource paper, and a demo toward the same CIKM. Coordinate them: each needs its own EasyChair track selection and its own author-reviewer nomination (a missed nomination is a stated desk reject), each needs its own GenAI disclosure section, and the contributions must not overlap into self-plagiarism. Stagger internal deadlines — the full paper to the May gate, the short-form pieces to the June gate — so one team is not writing three papers in one week.
Show full SKILL.md (397 more words)Show less
Role assignments that prevent CIKM-specific failures
The desk-reject triggers at this venue are administrative, so assign them to named people rather than to "the team":
| Role | Owns | Failure it prevents |
|---|---|---|
| Form owner | EasyChair track choice, reviewer nomination, arXiv declaration | The two stated desk rejects |
| Budget owner | Page measurement with appendices counted in | Overflow discovered at upload |
| Compliance owner | GenAI Usage Disclosure section, anonymity sweep | ACM AI-policy and blinding violations |
| Artifact owner | Anonymous review artifact → public release path | Dead links at camera-ready |
| Logistics owner | Registration, visa, presentation planning | November scramble |
One person may hold several roles on a small team; no role may be unheld. Log who holds what in the project tracker the day the track is chosen.
Cycle-verification ritual
Because CIKM re-platforms annually, open each new cycle with a thirty-minute verification pass before any planning meeting: locate the new host site from the series page (the domain will have changed), read the important-dates page and diff it against last year's rhythm, read the policies page for changed disclosure or nomination rules, and confirm the submission platform — EasyChair in 2026, but platform changes between editions are exactly the kind of fact teams assume wrongly. Write the findings into the project tracker with the access date, source map style. Every date in this skill is such a dated finding, not a rule.
Fallback ring
A CIKM rejection lands in early August, in time for WSDM's traditional late-summer gate (verify), ECIR in autumn, and SIGIR the following January. Log which lane the reviews faulted; that tells you whether the fix is more evidence (stay in the family) or a different audience (change family).
The conference itself is a work object
The November meeting deserves calendar time as more than a talk slot. CIKM's program concentrates the three communities this pack keeps invoking, plus the workshop day where next year's boundary topics surface first; treat attendance as pipeline work — scout which lanes are converging on your problem, note which tracks absorbed papers like the one you are planning, and talk to the resource authors whose datasets you will build on. For demo and applied authors the conference is part of the deliverable (booth time, live systems), which the logistics owner should plan for in the same tracker as the paper work.
Annual rhythm, compressed
Dec-Feb route + build (topic selection, datasets, baselines)
Mar-Apr results + draft in ACM format; internal cross-lane read
mid-May abstract gate (freeze) → paper gate
June short/resource/demo gates
Jul-early Aug review wait = artifact + camera-ready prep (Mode A)
Aug notification (7th in 2026) → 13-day camera-ready sprint (20th)
Sep-Oct presentation prep, travel, demo hardening
Nov conference; post-conference: absorb feedback, plan the next cycleDates shown are the verified 2026 instances; the shape recurs, the numbers do not.
Output format
[Mode] under-review wait / camera-ready sprint / next-edition build
[Next hard date] <date + which official page it came from>
[Freeze status] authorship frozen? track locked? artifact runnable?
[This week's three tasks] <ordered>
[Fallback] <next venue if the decision is negative, with its gate>© 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 CIKM-Skills/skills/cikm-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cikm 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 |
|---|---|---|---|---|---|---|
| Cikm Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Google Calendarcodewhale-hq/Codewhale | 41k | — | ~512 | Automated safety check: Pass | MIT | |
| Abstractbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~495 | Automated safety check: Notes | Custom licence | |
| 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 | |
| Feishu Calendar Managerop7418/CodePilot | 6.5k | 1 repos | ~1.4k | Automated safety check: Pass | Custom licence |
Similar skills
Abstract
brycewang-stanford/Auto-Empirical-Research-Skills
Reads the manuscript and notebooks to generate a structured abstract.
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.
Feishu Calendar Manager
op7418/CodePilot
Tool guidance for Feishu calendars: creating, listing, updating and searching events, managing attendees and replies, and checking free and busy time.
Abstraction
EpicenterHQ/epicenter
Shape a complex idea, workflow, or design around the judgment a person needs to make.
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 Cikm Workflow
What does Cikm Workflow do?
A skill your agent uses 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…. Cikm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Cikm Workflow?
Cikm Workflow fits situations like: planning a CIKM project calendar across the May abstract/paper gates; june short-track gates; august notification and camera-ready; the November conference.
How do I install Cikm Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-workflow -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Cikm Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-workflow -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-workflow in your project. Codex loads it when a task matches its description.
Can I use Cikm 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 cikm-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/cikm-workflow, .gemini/skills/cikm-workflow, .github/skills/cikm-workflow and .opencode/skills/cikm-workflow in your project.
What does Cikm Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Cikm Workflow is instructions for the agent only.
Does Cikm 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 Cikm 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 Cikm Workflow use?
Cikm 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 Cikm Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Cikm Workflow?
Skills that share tags, products or a category with Cikm Workflow: Google Calendar (codewhale-hq/Codewhale, 41k stars), Abstract (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k 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 Cikm Workflow?
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.