cikm-camera-ready
Use when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-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.
# CIKM Camera Ready CIKM 2026 notifies on August 7 and collects camera-ready on August 20 — a thirteen-day window (source map, 2026-07-08). Because CIKM publishes through ACM's Digital Library (the CIKM '25 volume is DOI 10.1145/3746252), that window contains not just editing but ACM's production machinery: e-rights completion, then source upload through TAPS, whose validation rejects malformed LaTeX. Start the clock at notification, not when the camera-ready email arrives. ## Thirteen-day sequence | Day | Action | |---|---| | 0-1 | Reopen the camera-ready instructions; confirm final page allowance (待核实 whether acceptance adds pages) | | 1-3 | De-anonymization pass; apply the concern → edit ledger from `cikm-author-response` | | 3-5 | e-rights form completed by the designated author; copyright block generated | | 5-9 | TAPS-clean source: standard `acmart`, no forbidden packages, rights commands in place | | 9-11 | Metadata layer: CCS concepts, keywords, author ORCIDs, affiliations as they should appear forever | | 11-13 | Final validated PDF; artifact links live and public; buffer for TAPS rejects | ## De-anonymization is more than adding names - Restore authors, affiliations, ackn
- Thirteen-day sequence
- De-anonymization is more than adding names
- The metadata outlives the talk
- Revision scope discipline
- TAPS survival notes
- Proceedings-record hygiene
- The camera-ready diff audit
- After publication
- Rome logistics strand (parallel, not sequential)
- Output format
What does the cikm-camera-ready skill do?
Use when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-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.