/acmmm-camera-ready
Use when preparing the ACM MM (ACM Multimedia) camera-ready version of record — de-anonymizing safely, completing the ACM rights form and CCS concepts, meeting ACM sigconf requirements, releasing code/data/media artifacts and any earned reproducibility badge, registering, and
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill acmmm-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
/acmmm-camera-ready
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when preparing the ACM MM (ACM Multimedia) camera-ready version of record — de-anonymizing safely, completing the ACM rights form and CCS concepts, meeting ACM sigconf requirements, releasing code/data/media artifacts and any earned reproducibility badge, registering, and
SKILL.md
acmmm-camera-ready.SKILL.mdname: acmmm-camera-ready
description: Use when preparing the ACM MM (ACM Multimedia) camera-ready version of record — de-anonymizing safely, completing the ACM rights form and CCS concepts, meeting ACM sigconf requirements, releasing code/data/media artifacts and any earned reproducibility badge, registering, and planning the oral/poster presentation in Rio.
ACM MM Camera-Ready
Use this after acceptance to turn the reviewed PDF into the ACM Digital Library version of record. Camera-ready is a distinct piece of work with its own deadline (reported August 6 for 2026) and its own failure modes — several of them ACM-specific.
De-anonymization pass
The reviewed paper was anonymous (main track); the camera-ready is not. Reverse the blinding carefully:
- Add author names, affiliations, and acknowledgements/funding.
- Restore "our previous work" phrasing and the real repository/dataset URLs.
- Replace the anonymous data/code mirror with the **permanent, public** archive (DOI).
- Re-check that no *anonymous-only* placeholder text survives.
ACM publishing requirements
| Item | What to do | |---|---| | ACM rights form | Complete the eRights process; paste the returned rights block and DOI into the paper | | CCS concepts | Add ACM Computing Classification System concepts and author keywords | | sigconf compliance | Final PDF in the current ACM `sigconf` template; pass ACM's PDF/format check | | Reference/overflow | References may occupy the extra pages; the body stays within the accepted length | | Metadata | Title, authors, affiliations, and abstract match the ACM submission exactly |
The exact ACM rights/OA options (including ACM Open) are settled here; confirm the current process (待核实 each cycle).
Artifact and badge release
code: public repo + archived DOI, LICENSE, README with run instructions
data: dataset card, license, access path (mirror or agreement)
media: final demo video/audio, now de-anonymized, playable in open players
badge: if the Reproducibility track awarded a badge, include the badge and artifact link
Camera-ready is when the public release replaces the anonymous review artifact — do not leave the community pointing at a dead anonymous link.
Registration and attendance
- At least one author must register by the deadline and present; confirm the current
registration category and any presenter requirement.
- Check visa/travel needs for **Rio de Janeiro** early — international travel is the common
logistical failure.
Presentation prep by tier
- **Oral:** a talk that leads with the cross-modal contribution and *plays the media* — the
audience should see/hear the seam your paper exploits.
- **Poster:** a single readable visual with the teaser, the mechanism, and one decisive
media example; bring a device to play a short clip.
- Prepare captioned media that works offline; conference A/V and network are unreliable.
The ACM eRights step, in order
1. Receive the ACM eRights email after acceptance; complete the rights/permissions form.
2. ACM returns the rights block + DOI + the correct conference string.
3. Paste that block verbatim into the sigconf template (do not hand-edit it).
4. Add CCS concepts and keywords; run ACM's PDF format/preflight check.
5. Upload the final PDF and source where required, matching the registered metadata.
Skipping or mistyping the rights block is a frequent camera-ready bounce; treat the returned text as fixed data, not prose to reword.
Media for the ACM Digital Library
- Supplementary video/audio can accompany the DL record; provide the **de-anonymized** final
versions in the accepted formats, captioned and playable in open players.
- Ensure the public artifact link in the paper resolves to the permanent archive, not the old
anonymous review mirror.
- If a badge was awarded, include the ACM badge and the artifact DOI so the DL entry carries it.
Final camera-ready checklist
- De-anonymized fully; rights block and DOI in place; CCS concepts added.
- sigconf format check passed; metadata matches ACM record.
- Public artifact archived and linked; any badge included.
- Registration done; presentation media prepared and offline-safe.
Output format
[De-anonymization] complete / residual anonymous text: <list>
[ACM publishing] rights + CCS + sigconf done / gaps: <list>
[Artifact release] public + archived / gaps
[Registration] done / pending
[Presentation] oral/poster plan ready / to do
[Blocking items] <ordered before the camera-ready deadline>
Read more
name: acmmm-camera-ready description: Use when preparing the ACM MM (ACM Multimedia) camera-ready version of record — de-anonymizing safely, completing the ACM rights form and CCS concepts, meeting ACM sigconf requirements, releasing code/data/media artifacts and any earned reproducibility badge, registering, and planning the oral/poster presentation in Rio.
ACM MM Camera-Ready
Use this after acceptance to turn the reviewed PDF into the ACM Digital Library version of record. Camera-ready is a distinct piece of work with its own deadline (reported August 6 for 2026) and its own failure modes — several of them ACM-specific.
De-anonymization pass
The reviewed paper was anonymous (main track); the camera-ready is not. Reverse the blinding carefully:
- Add author names, affiliations, and acknowledgements/funding.
- Restore "our previous work" phrasing and the real repository/dataset URLs.
- Replace the anonymous data/code mirror with the **permanent, public** archive (DOI).
- Re-check that no *anonymous-only* placeholder text survives.
ACM publishing requirements
| Item | What to do | |---|---| | ACM rights form | Complete the eRights process; paste the returned rights block and DOI into the paper | | CCS concepts | Add ACM Computing Classification System concepts and author keywords | | sigconf compliance | Final PDF in the current ACM `sigconf` template; pass ACM's PDF/format check | | Reference/overflow | References may occupy the extra pages; the body stays within the accepted length | | Metadata | Title, authors, affiliations, and abstract match the ACM submission exactly |
The exact ACM rights/OA options (including ACM Open) are settled here; confirm the current process (待核实 each cycle).
Artifact and badge release
code: public repo + archived DOI, LICENSE, README with run instructions data: dataset card, license, access path (mirror or agreement) media: final demo video/audio, now de-anonymized, playable in open players badge: if the Reproducibility track awarded a badge, include the badge and artifact link
Camera-ready is when the public release replaces the anonymous review artifact — do not leave the community pointing at a dead anonymous link.
Registration and attendance
- At least one author must register by the deadline and present; confirm the current
registration category and any presenter requirement.
- Check visa/travel needs for **Rio de Janeiro** early — international travel is the common
logistical failure.
Presentation prep by tier
- **Oral:** a talk that leads with the cross-modal contribution and *plays the media* — the
audience should see/hear the seam your paper exploits.
- **Poster:** a single readable visual with the teaser, the mechanism, and one decisive
media example; bring a device to play a short clip.
- Prepare captioned media that works offline; conference A/V and network are unreliable.
The ACM eRights step, in order
1. Receive the ACM eRights email after acceptance; complete the rights/permissions form. 2. ACM returns the rights block + DOI + the correct conference string. 3. Paste that block verbatim into the sigconf template (do not hand-edit it). 4. Add CCS concepts and keywords; run ACM's PDF format/preflight check. 5. Upload the final PDF and source where required, matching the registered metadata.
Skipping or mistyping the rights block is a frequent camera-ready bounce; treat the returned text as fixed data, not prose to reword.
Media for the ACM Digital Library
- Supplementary video/audio can accompany the DL record; provide the **de-anonymized** final
versions in the accepted formats, captioned and playable in open players.
- Ensure the public artifact link in the paper resolves to the permanent archive, not the old
anonymous review mirror.
- If a badge was awarded, include the ACM badge and the artifact DOI so the DL entry carries it.
Final camera-ready checklist
- De-anonymized fully; rights block and DOI in place; CCS concepts added.
- sigconf format check passed; metadata matches ACM record.
- Public artifact archived and linked; any badge included.
- Registration done; presentation media prepared and offline-safe.
Output format
[De-anonymization] complete / residual anonymous text: <list> [ACM publishing] rights + CCS + sigconf done / gaps: <list> [Artifact release] public + archived / gaps [Registration] done / pending [Presentation] oral/poster plan ready / to do [Blocking items] <ordered before the camera-ready deadline>
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

