cikm-related-work
Use when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-related-work --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 Related Work Related work at CIKM is a three-front obligation. A submission claiming the IR-mining-KM boundary must show command of each literature it borrows from, plus the smaller literature that lives *on* the boundary — much of which is CIKM's own back catalog. A section citing only one lane tells two-thirds of the reviewer pool that their field's relevant results may be unknown to the authors. ## Three-front coverage plan | Front | Lineage to command | What its reviewer checks | |---|---|---| | Retrieval | Ranking models, neural matching (DRMM-line), evaluation practice | Is the nearest ranking method compared or distinguished? | | Mining | Representation learning (GraRep-line), graph/sequence models, scale methods | Is the mechanism's delta over the nearest mining method stated? | | KM / databases | Entity linking (TAGME-line), integration, KG construction and quality | Is the data-management cost and lineage acknowledged? | The verified exemplars in `../../resources/exemplars/library.md` mark where these lineages pass through CIKM itself; citing the venue's own milestones — DSSM for click-supervised semantic matching, RippleNet/BERT4Rec for KG- and transformer-based r
- Three-front coverage plan
- The boundary-work paragraph
- Misattribution guard
- Recency expectations by front
- Citation hygiene mechanics
- Preprints, concurrency, and the declaration rule
- Auditing the novelty sentence
- Output format
What does the cikm-related-work skill do?
Use when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-related-work --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.