cikm-author-response
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-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.
# CIKM Author Response 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 map | 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 | ## If a window opens: the tri-lane reply 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
- Situation map
- If a window opens: the tri-lane reply
- Micro-example: the mining-lane scalability objection
- No window, accepted: the revision note
- No window, rejected: the resubmission brief
- Tone calibration for a three-community room
- Verify-before-writing checklist
- The one-page ceiling
- Output format
What does the cikm-author-response skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-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.