/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,
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-camera-ready --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ccs-camera-ready
Context preview
The summary Claude sees to decide when to auto-load this skill.
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,
SKILL.md
ccs-camera-ready.SKILL.mdname: ccs-camera-ready
description: 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.
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.
Badge placement map
| Badge earned in artifact evaluation | Where it goes | What to confirm | |---|---|---| | Artifacts Available | First page, with the archival DOI/URL | The archive is public and permanent before camera-ready | | Artifacts Evaluated - Functional | First page | The committee's functional result is final | | Artifacts Evaluated - Reusable | First page | Documentation matches the reusable claim | | Results Reproduced | First page | The reproduced results match the camera-ready numbers |
De-anonymization sweep
- Restore the author block, acknowledgements, grants, and contribution statements the
anonymous version stripped.
- Rewrite third-person self-citations into natural first person where it improves clarity.
- Replace anonymized repository placeholders with the public, licensed, archived artifact and
test every link from a logged-out browser.
- Re-check that de-anonymizing did not silently reveal an embargoed vendor before its patch.
ACM proceedings reflow
- Switching from the submission build to the final `sigconf` build changes spacing; recheck
every page break, protocol figure, and wide result table after adding the author block.
- Material that fit the 12-page anonymous body can overflow once affiliations,
acknowledgements, and the rights block are added; confirm the final length against the camera-ready page instruction rather than assuming.
- Keep theorem, protocol, and section numbering identical to the reviewed version so the
meta-review and shepherd record stay traceable.
Worked example: integrating a shepherd requirement
The shepherd asked that the adaptive-attack results move from the appendix into the main evaluation. Camera-ready move: promote the adaptive table into Section 6, add one sentence interpreting the degraded defense numbers honestly, and leave the full attack derivation in the appendix — without strengthening any claim the reviewers did not see.
Hedged logistics
- Registration pricing, the exact camera-ready and rights-form deadlines, and badge-placement
mechanics change every cycle; confirm against the notification email and current instructions.
Output format
[Camera-ready status] Ready / Needs fixes / Blocked
[Final package] <PDF / source / bib / ACM rights form / badges / artifacts>
[Policy checks] <format / authors / disclosure timing / registration / presentation>
[Reviewer-change map] <shepherd/revision requirement -> final edit>
[Remaining owner] <person -> task>
Read more
name: ccs-camera-ready description: 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.
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.
Badge placement map
| Badge earned in artifact evaluation | Where it goes | What to confirm | |---|---|---| | Artifacts Available | First page, with the archival DOI/URL | The archive is public and permanent before camera-ready | | Artifacts Evaluated - Functional | First page | The committee's functional result is final | | Artifacts Evaluated - Reusable | First page | Documentation matches the reusable claim | | Results Reproduced | First page | The reproduced results match the camera-ready numbers |
De-anonymization sweep
- Restore the author block, acknowledgements, grants, and contribution statements the
anonymous version stripped.
- Rewrite third-person self-citations into natural first person where it improves clarity.
- Replace anonymized repository placeholders with the public, licensed, archived artifact and
test every link from a logged-out browser.
- Re-check that de-anonymizing did not silently reveal an embargoed vendor before its patch.
ACM proceedings reflow
- Switching from the submission build to the final `sigconf` build changes spacing; recheck
every page break, protocol figure, and wide result table after adding the author block.
- Material that fit the 12-page anonymous body can overflow once affiliations,
acknowledgements, and the rights block are added; confirm the final length against the camera-ready page instruction rather than assuming.
- Keep theorem, protocol, and section numbering identical to the reviewed version so the
meta-review and shepherd record stay traceable.
Worked example: integrating a shepherd requirement
The shepherd asked that the adaptive-attack results move from the appendix into the main evaluation. Camera-ready move: promote the adaptive table into Section 6, add one sentence interpreting the degraded defense numbers honestly, and leave the full attack derivation in the appendix — without strengthening any claim the reviewers did not see.
Hedged logistics
- Registration pricing, the exact camera-ready and rights-form deadlines, and badge-placement
mechanics change every cycle; confirm against the notification email and current instructions.
Output format
[Camera-ready status] Ready / Needs fixes / Blocked [Final package] <PDF / source / bib / ACM rights form / badges / artifacts> [Policy checks] <format / authors / disclosure timing / registration / presentation> [Reviewer-change map] <shepherd/revision requirement -> final edit> [Remaining owner] <person -> task>
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /aaai-artifact-evaluation
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
Open skill - /aaai-author-response
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round
Open skill - /aaai-camera-ready
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and
Open skill - /aaai-experiments
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and
Open skill - /aaai-related-work
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a
Open skill - /aaai-reproducibility
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that
Open skill

