kdd-workflow
Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-workflow --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 Workflow Use this as the project-management layer. KDD's calendar is structurally different from single-deadline ML venues: **two cycles per year**, each with an abstract deadline about one week before the paper deadline (2026 anchors: Jul 24/Jul 31, 2025 and Feb 1/Feb 8, 2026, AoE), a rebuttal window inside review, and a Resubmit outcome that connects the cycles into a pipeline. Plan the pipeline, not a single date. KDD is an ACM conference, not a journal: no standing editor, leadership rotates per edition (the KDD 2026 committee roster lives on the conference site; individual names 待核实 before citing), and the cost surface is registration plus, under ACM Open, a possible APC for authors at non-participating institutions — with a temporary 65% ACM subsidy announced for 2026. Verify all money facts against current pages. ## Cycle-choice decision | Situation | Choose | Reasoning | |---|---|---| | Evidence complete, paper drafted | Nearest cycle | Waiting adds staleness risk in fast subfields | | Core result solid, ablations/scale runs missing | Next cycle | Rebuttal cannot carry links, so missing evidence has no delivery channel later | | Prior cycle returned Resubmit | Next cy
- Cycle-choice decision
- Pipeline milestones (per cycle)
- The Resubmit loop as a plan
- Failure modes on this calendar
- Vignette: one paper, three cycles, two tracks
- Capacity planning numbers
- Output format
What does the kdd-workflow skill do?
Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-workflow --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.