kdd-related-work
Use when positioning a KDD submission against the data-mining lineage (prior KDD volumes, ICDM, SDM, WSDM, CIKM, WWW) and the ML flagships, handling venue misattribution traps, cross-cycle resubmission overlap, concurrent arXiv work, and the mechanism-contrast style of novelty argument that ACM SIGKDD reviewers expect.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-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.
# KDD Related Work Use this to audit positioning before the writing freeze. KDD sits inside a dense family of venues that share topics but not registers, and its reviewers know the mining lineage personally — misplacing a classic paper's venue or missing the direct KDD predecessor of your own method are both instantly visible errors here. ## The lineage obligation A KDD submission is expected to know its own conference's history on the topic. Before writing, build the ancestry chain: which prior KDD papers created the problem's vocabulary, and what does this paper change structurally? The DeepWalk (KDD 2014) → node2vec (KDD 2016) → metapath2vec (KDD 2017) chain in `resources/exemplars/library.md` is the canonical shape — each successor names the structural property of the data its predecessor mishandled. A related-work section that surveys families ("embedding methods can be divided into...") instead of stating deltas is journal register, not KDD register. ## Venue map for positioning | Literature lane | Venues | What KDD reviewers check | |---|---|---| | Own lineage | Prior KDD volumes (ACM DL) | Is the nearest KDD ancestor cited and contrasted mechanically? | | Mining siblings |
- The lineage obligation
- Venue map for positioning
- Misattribution traps
- Novelty sentence pattern
- Overlap declarations specific to KDD
- Vignette: positioning an LLM-era mining paper
- Pre-freeze audit
- Output format
What does the kdd-related-work skill do?
Use when positioning a KDD submission against the data-mining lineage (prior KDD volumes, ICDM, SDM, WSDM, CIKM, WWW) and the ML flagships, handling venue misattribution traps, cross-cycle resubmission overlap, concurrent arXiv work, and the mechanism-contrast style of novelty argument that ACM SIGKDD reviewers expect.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-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.