cikm-writing-style
Use when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously, compressing into appendix-inclusive page budgets, keeping claims inside the evidence, and maintaining double-blind and disclosure-compliant prose.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-writing-style --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 Writing Style A CIKM paper is read in three accents at once. The IR reviewer scans for the task and the evaluation; the mining reviewer scans for the mechanism and its delta; the KM/database reviewer scans for the data reality — schemas, scale, heterogeneity, noise. Style at this venue means making all three scans succeed in the first page, inside a budget where appendices offer no escape (10 pages including them for 2026 full papers). ## The first page, three scans deep Order the opening so each lane hits its anchor early: 1. **The information problem** in domain terms — what is being retrieved, mined, linked, or integrated, and for whom. 2. **Why the boundary is the hard part.** CIKM contributions usually live where lanes meet; say which interaction breaks existing single-lane methods ("KG completion models assume static graphs; enterprise search feeds them a stream"). 3. **The mechanism, named.** One clause a mining reviewer can repeat in their review. 4. **The evidence preview, calibrated.** Datasets, baselines, and the honest size of the win — with the deployment or resource evidence up front if the track demands it. If the paper cannot state point 2, it is a single-lan
- The first page, three scans deep
- Vocabulary discipline across lanes
- Budget compression, appendix-inclusive
- Anonymity and disclosure in prose
- Section skeleton for a 10-page full paper
- Title and abstract as routing devices
- Micro-rewrite exercise
- Limitations without self-sabotage
- Output format
What does the cikm-writing-style skill do?
Use when revising a CIKM manuscript for the tri-community readership — writing an opening that lands with IR, data-mining, and knowledge-management reviewers simultaneously, compressing into appendix-inclusive page budgets, keeping claims inside the evidence, and maintaining double-blind and disclosure-compliant prose.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-writing-style --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.