kdd-artifact-evaluation
Use when packaging code, datasets, configs, and deployment evidence for a KDD paper, where the repository cited in the submission is the only artifact reviewers can reach because rebuttals ban links. Covers anonymized repo construction, scale-claim harnesses, ADS evidence without production data, and post-acceptance release.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-artifact-evaluation --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 Artifact Evaluation Use this while the submission is being assembled — not after. KDD's review mechanics create one hard constraint that reorders all artifact work: **the rebuttal phase does not allow hyperlinks**, so the anonymized repository referenced inside the submitted PDF is the complete and final artifact channel for the whole review. There is no "we'll share code if reviewers ask"; asking happens in a phase where you cannot answer with a link. ## Artifact strategy by track | Track | Primary artifact | What reviewers actually probe | Non-shippable core, and its substitute | |---|---|---|---| | Research | Anonymized code + configs + data loaders | Can the headline table be regenerated? Does the scale claim have a runnable path? | Massive datasets → downsampled slice + full-scale download script | | ADS | Measurement definitions + pipeline skeleton | Are post-launch metrics precisely defined? Is the eval window stated? | Production data/code → metric spec, schema, synthetic replay generator | | Datasets & Benchmarks | The dataset itself + loaders + baseline harness | License, provenance, documentation, versioning | Nothing — the artifact is the paper | ## Building the a
- Artifact strategy by track
- Building the anonymized repository
- Scale claims need scale artifacts
- ADS evidence packaging without leaking production
- After acceptance
- Vignette: packaging a billion-edge graph paper
- Common artifact failures at this venue
- Output format
anonymous-artifact/ smoke-test on a clean machine: docker run --rm -v $PWD:/w -w /w python:3.11 bash -c "pip install -r env/requirements.txt && bash run.sh --sample"
What does the kdd-artifact-evaluation skill do?
Use when packaging code, datasets, configs, and deployment evidence for a KDD paper, where the repository cited in the submission is the only artifact reviewers can reach because rebuttals ban links. Covers anonymized repo construction, scale-claim harnesses, ADS evidence without production data, and post-acceptance release.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-artifact-evaluation --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.