kdd-submission
Use when auditing a KDD submission for readiness in either cycle, covering Research vs ADS track declaration, OpenReview profile completeness for all authors, the ACM sigconf 8-content-page budget, double-blind checks, in-paper artifact references, resubmission declarations, and desk-reject triggers specific to ACM SIGKDD.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-submission --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 Submission Run this audit twice: once when the abstract is registered, once before the full-paper deadline. KDD's abstract and paper deadlines are about a week apart in each cycle (2026 Cycle 1: July 24 / July 31, 2025; Cycle 2: February 1 / February 8, 2026, all AoE), and several failure modes below are only fixable in that gap. Reopen the current track CFP first — every number here is a 2026-cycle anchor, not a permanent rule. ## Track and cycle declaration - One paper, one track: the same work may not go to the Research Track and the Applied Data Science Track simultaneously. If the team is still arguing about track choice at submission week, run `kdd-topic-selection` before anything else. - Confirm which cycle the deadline belongs to. A team planning around "the KDD deadline" without naming the cycle is planning around the wrong date half the time. - Resubmissions from a prior cycle's Resubmit decision must be flagged in the form, must carry the previous OpenReview forum id, and must prepend a one-page summary of changes as the first page of the PDF. Omitting the summary page wastes the resubmission advantage. ## OpenReview profile gate KDD 2026 required a **complete Open
- Track and cycle declaration
- OpenReview profile gate
- Format audit
- Desk-reject and severity table
- Final-week sequence
- Vignette: an ADS submission that nearly desk-rejected itself
- Cross-cycle edge cases
- Output format
What does the kdd-submission skill do?
Use when auditing a KDD submission for readiness in either cycle, covering Research vs ADS track declaration, OpenReview profile completeness for all authors, the ACM sigconf 8-content-page budget, double-blind checks, in-paper artifact references, resubmission declarations, and desk-reject triggers specific to ACM SIGKDD.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-submission --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.