ccs-camera-ready
Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-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.
# CCS Camera Ready Use this after acceptance or after clearing a minor revision. Reopen the current CCS camera-ready instructions, the ACM rights form, the registration page, and the notification or shepherd email before advising authors. ## Camera-ready audit - Convert the anonymous submission to the public proceedings version: author names, affiliations, acknowledgements, funding, and artifact links restored. - Apply the ACM `sigconf` final template and the ACM rights-management block; the DOI, the conference reference string, and the copyright notice come from the ACM eRights system. - Incorporate exactly what the shepherd or the minor-revision decision required, without expanding the contribution beyond what was reviewed. - Place any artifact-evaluation badges earned (Available, Functional, Reusable, Results Reproduced) as instructed; badge placement is part of the ACM camera-ready workflow. - Confirm the final title and abstract match the HotCRP-registered title and abstract if the cycle froze them at registration. - Coordinate disclosure timing: the public proceedings version and any released exploit or advisory should not appear before the agreed vendor-disclosure date. ## B
- Camera-ready audit
- Badge placement map
- De-anonymization sweep
- ACM proceedings reflow
- Worked example: integrating a shepherd requirement
- Hedged logistics
- Output format
What does the ccs-camera-ready skill do?
Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-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.