kdd-camera-ready
Use when preparing an accepted KDD paper for ACM proceedings, covering the 12-page proceedings budget with 9 content pages, the extra content page over the submission, the 3-page cap on references plus appendix, ACM e-rights and TAPS source processing, ACM Open APC status, de-anonymization, and Digital Library metadata for SIGKDD.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-camera-ready --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 Camera Ready Use this after acceptance. KDD publishes through ACM, which means the final version is not "the PDF you upload" — it is the output of ACM's production pipeline (e-rights, then TAPS) applied to your **source files**. Papers that compile locally but violate acmart conventions stall in TAPS, so start this process the week the decision arrives, not the week the proceedings deadline arrives. ## The page arithmetic (2026 anchor — reverify per cycle) Accepted KDD 2026 papers all received the same proceedings budget: **12 pages total, of which 9 are content pages**. Since submissions were 8 content pages, acceptance buys exactly **one extra content page**, while references and appendix together must fit in the remaining **3 pages**. - Spend the ninth page deliberately: reviewer-requested ablations, the scoping sentences promised in rebuttal, and de-anonymized acknowledgements all compete for it. - The 3-page references+appendix cap is the trap: submissions with long optional appendices must **cut appendix material**, not just add a page. Decide early what migrates into the body, what moves to the public repository, and what dies. - Keep section, table, and algorithm numb
- The page arithmetic (2026 anchor — reverify per cycle)
- ACM production pipeline
- De-anonymization sweep
- Money and access
- Worked example: spending the ninth page
- Proceedings metadata checklist
- Timeline discipline
- Output format
Typical TAPS package hygiene before zipping (KDD-specific naming: see the acceptance email; the zip name encodes proceedings acronym + paper id) grep -rn "anonymous" main.tex sections/*.tex # leftover anonymity flags grep -rn "\\\\vspace\|\\\\baselineskip" *.tex # spacing hacks TAPS rejects grep -rn "includegraphics" *.tex | wc -l # every figure file must ship in the zip biber --tool --validate-datamodel refs.bib # broken .bib entries stall TAPS builds
What does the kdd-camera-ready skill do?
Use when preparing an accepted KDD paper for ACM proceedings, covering the 12-page proceedings budget with 9 content pages, the extra content page over the submission, the 3-page cap on references plus appendix, ACM e-rights and TAPS source processing, ACM Open APC status, de-anonymization, and Digital Library metadata for SIGKDD.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill kdd-camera-ready --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.