cscw-camera-ready
Use when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue assignment, and the separate track of presenting at the next CSCW conference.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-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.
# CSCW Camera-Ready and Production Acceptance at CSCW starts two parallel tracks that most venues fuse into one: the paper becomes a **journal article in PACMHCI** on ACM's production schedule, and separately the authors are **invited to present at the next CSCW conference**. Keep the tracks distinct in your planning — the article's publication and the talk's logistics run on different clocks with different owners. ## Track 1: the PACMHCI article **Execute the conditions first.** Many acceptances arrive as Conditional Accept with Minor Changes: a named list verified before the acceptance is final. Treat the list as a contract — do the items, document where, and resist bundling in unrequested rewrites that could reopen questions. **Deanonymization is a build step, not a find-replace.** Reverse every layer the submission masked: - Restore authors, affiliations, and the acknowledgements section (people, funders, grant numbers) — this is the text most often still missing at the deadline because it never existed in any draft. - Convert third-person self-citations back to first person where natural. - Re-point anonymized repository links to the public, attributed release (`cscw-artifact-
- Track 1: the PACMHCI article
- Track 2: the conference presentation
- Two-track checklist
- Final sweep
What does the cscw-camera-ready skill do?
Use when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue assignment, and the separate track of presenting at the next CSCW conference.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-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 984 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.