Individual skill
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.
KDD-Skills/skills/kdd-related-work/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- data Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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