A skill your agent uses when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-author-response .claude/skills/cikm-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 "cikm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-author-response into .claude/skills/cikm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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/CIKM-Skills/skills/cikm-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 cikm-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-author-response .agents/skills/cikm-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 "cikm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-author-response into .agents/skills/cikm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-author-response .cursor/skills/cikm-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 "cikm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-author-response into .cursor/skills/cikm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 CIKM-Skills/skills/cikm-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 cikm-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-author-response .gemini/skills/cikm-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 "cikm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-author-response into .gemini/skills/cikm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-author-response .github/skills/cikm-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 "cikm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-author-response into .github/skills/cikm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-author-response .opencode/skills/cikm-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 "cikm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-author-response into .opencode/skills/cikm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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.
cikm-author-responseA skill your agent uses when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision…
Cikm Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision notes that answer reviewer concerns, handling post-decision chair correspondence, and converting rejection reviews into a resubmission brief.
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.
It sits in Education, covering Study guides and flashcards. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cikm Author Response loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 749 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 749 words, ~1,608 tokens.
.claude/skills/cikm-author-response/SKILL.md (or your agent's skills folder).CIKM's response mechanics are genuinely cycle-dependent: no official statement confirming or denying a 2026 rebuttal phase could be retrieved (source map, 2026-07-08, 待核实). This skill therefore covers all four author-side writing situations around CIKM reviews, with the no-window case treated as the default — because when there is no rebuttal, the reply to reviewers gets written anyway, just in different documents.
| Situation | The document you actually write | Governing constraint |
|---|---|---|
| A response window opens | Anonymous reply inside EasyChair | Announced word/format rules; anonymity persists |
| No window, paper accepted | Camera-ready revision note | Address concerns without exceeding accepted scope |
| No window, paper rejected | Resubmission brief for the next venue | Honest triage, no venue-blaming |
| Factual process error | Confidential note to PC chairs | Facts only; never argue merit this way |
CIKM reviews arrive from up to three community lanes (cikm-review-process), so a
good reply is organized by reviewer, not by theme — each lane's reviewer should find
their own objection answered in their own vocabulary:
Reviewer: "Complexity analysis suggests quadratic blow-up on dense graphs; the experiments avoid this regime."
Reply skeleton: (a) confirm the reading is correct for worst-case density; (b) point to the submitted Table/appendix entry showing observed scaling on the densest tested graph; (c) state the density regime of the target application and that the claim is scoped to it; (d) offer a one-sentence camera-ready scope clarification. Four moves, no new experiments, no evasion.
The August 7 → August 20 camera-ready sprint (2026 dates) is where reviewer concerns
get answered in practice. Build a concern → edit ledger: every substantive review
point maps to a camera-ready change, a scoped-limitation sentence, or a reasoned
no-change. Keep the ledger; if the proceedings process or a chair asks what changed,
the answer is ready, and cikm-camera-ready consumes it directly.
Write it within a week, while context is fresh:
cikm-workflow fallback choice.CIKM's communities have different argument cultures — IR discussion leans protocol-precise, mining leans delta-and-numbers, KM/database leans systems-pragmatic — but one register works for all three: technical, specific, and unwounded. Practical rules:
Response mechanics are exactly the kind of fact this venue changes per cycle, so before drafting anything reviewer-facing:
[ ] Reopen the current cycle's author instructions / notification email:
does a response channel exist at all this year?
[ ] If yes: word/character limit, format, deadline (AoE?), and whether
new results or links are permitted or barred
[ ] Anonymity rules during the window (assume double-blind persists)
[ ] Who may submit: contact author only, or any author?
[ ] For chair notes: the stated contact route on the host site, not a
guessed email addressEvery item comes from the current host site or EasyChair instance — the 2026 source map deliberately records the rebuttal question as unresolved (待核实), and this checklist is how it gets resolved for whatever cycle is live.
Whatever the channel — window reply, camera-ready note, or chair correspondence — hold to roughly a page of substance per audience. Beyond that length, the reader is skimming, and a skimmed concession does as much damage as an unmade one. If the honest response needs three pages, the paper had three pages of problems; choose the one whose resolution changes the decision and spend the page there.
[Situation] response-window / camera-ready note / resubmission brief / chair note
[Per-reviewer leads] <R1/R2/R3: the concern each block opens with>
[Evidence anchors] <submitted section/table/artifact per concern>
[Concessions] <scoped limits admitted, in one line each>
[Deliverable deadline] <window close / Aug-20-style camera-ready gate / next venue 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
Just SKILL.md in CIKM-Skills/skills/cikm-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Cikm 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 |
|---|---|---|---|---|---|---|
| Cikm Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Deep Reading Analystginobefun/deep-reading-analyst-skill | 354 | 4 repos | ~3.6k | Automated safety check: Pass | MIT | |
| NihaishaJuneYaooo/nihaisha-nishi-tcm | 2.2k | — | ~4k | Automated safety check: Pass | None | |
| Claude Certification Tutorrohitg00/ai-engineering-from-scratch | 66k | — | ~3k | Automated safety check: Pass | MIT | |
| StudyVault Quiz Tutorbevibing/tutor-skills | 1.3k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Project Mastery Coachtudoumashu/ai-memory-skillpack | 456 | — | ~1.8k | Automated safety check: Pass | MIT |
ginobefun/deep-reading-analyst-skill
Comprehensive framework for deep analysis of articles, papers, and long-form content using 10+ thinking models (SCQA, 5W2H, critical thinking, inversion, mental models, first principles, systems…
JuneYaooo/nihaisha-nishi-tcm
A skill your agent uses when the user asks about Ni Haisha / 倪海厦 TCM course material, especially Shang Han Lun / 伤寒论, Jingui / 金匮要略, Zhongjing Xinfa / 仲景心法, clinical cases / 临床案例 / 倪师医案, Bagang…
rohitg00/ai-engineering-from-scratch
Guides a learner through one of four independent Claude certification tracks with onboarding, lessons, practice labs, mock exams and remediation.
bevibing/tutor-skills
Quizzes you on the notes in an Obsidian StudyVault, tracks proficiency per concept and drills weak areas in four-question rounds.
tudoumashu/ai-memory-skillpack
Train strict project ownership from repo-local docs/ai memory and central LLM Wiki project entities.
lijigang/ljg-skills
Turns a named classical Chinese chapter, such as one from the Tao Te Ching or the Analects, into a single annotated PNG image with notes and commentary.
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…
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…
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…
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…
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…
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…
Categories
A skill your agent uses when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision…. Cikm Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision notes that answer reviewer concerns, handling post-decision chair correspondence, and converting rejection reviews into a resubmission brief.
Cikm Author Response fits situations like: preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026); writing camera-ready revision notes that answer reviewer concerns; handling post-decision chair correspondence; converting rejection reviews into a resubmission brief.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-author-response -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-author-response in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-author-response -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-author-response in your project. Codex loads it when a task matches its description.
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-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/cikm-author-response, .gemini/skills/cikm-author-response, .github/skills/cikm-author-response and .opencode/skills/cikm-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Cikm Author Response is instructions for the agent only.
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.
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.
Cikm 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.
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cikm Author Response: Deep Reading Analyst (ginobefun/deep-reading-analyst-skill, 354 stars), Nihaisha (JuneYaooo/nihaisha-nishi-tcm, 2.2k stars), Claude Certification Tutor (rohitg00/ai-engineering-from-scratch, 66k stars) and StudyVault Quiz Tutor (bevibing/tutor-skills, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.
