kdd-review-process
Use when reasoning about how KDD papers get judged in its dual-cycle OpenReview process: per-review rebuttal, area-chair recommendations weighed on merit through reproducibility and ethics, PC-chair decisions, the Resubmit outcome feeding the next cycle, the mixed academic-industry reviewer pool, and generative-AI review rules.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-review-process --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 Review Process Use this to model decisions rather than guess at them. KDD review runs on OpenReview, per track and per cycle (the venue groups are literally named by track x cycle, e.g. `Research_Track_Cycle_2`). Reconfirm the current cycle's mechanics before relying on any stage detail — KDD tunes its process between cycles, not just between years. ## Decision machinery - **Reviewers** score against the CFP's stated factors: technical merit, originality, potential impact, quality of execution, quality of presentation, related work, reproducibility of results, and ethics. - **Authors** respond to each review in the rebuttal window — text only, no hyperlinks. - **Area chairs** synthesize reviews, rebuttals, and reviewer discussion into a recommendation. - **PC chairs** make final decisions. This last step is real, not ceremonial: calibration across areas happens above the AC. ## The three-outcome game Unlike single-shot venues, KDD's decision space includes **Resubmit**, and the CFP frames resubmissions that properly address noted concerns as having better odds than fresh submissions. Strategic consequences: | Outcome | What it means | Author's next move | |---|---|---| | Acce
- Decision machinery
- The three-outcome game
- Who reviews at KDD
- Review-integrity rules worth knowing as an author
- Reading a KDD review packet
- Cycle dynamics
- Leverage per decision factor
- Stage-by-stage realism
- Output format
What does the kdd-review-process skill do?
Use when reasoning about how KDD papers get judged in its dual-cycle OpenReview process: per-review rebuttal, area-chair recommendations weighed on merit through reproducibility and ethics, PC-chair decisions, the Resubmit outcome feeding the next cycle, the mixed academic-industry reviewer pool, and generative-AI review rules.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-review-process --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.