/acmmm-workflow
Use when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill acmmm-workflow --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-workflow
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November
SKILL.md
acmmm-workflow.SKILL.mdname: acmmm-workflow
description: Use when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November presentation in Rio, with the right skill invoked at each stage.
ACM MM Workflow
Use this to run an ACM Multimedia submission as a scheduled campaign rather than a deadline scramble. The SIGMM calendar has a long gap between the April submission chain and the July decision, so the work clusters at the front and the back.
The ACM MM calendar (2026 anchors, AoE)
| Phase | 2026 date | What must be true | Skill | |---|---|---|---| | Scope + track choice | pre-March | Contribution is cross-modal; thematic area and track chosen | `acmmm-topic-selection` | | Draft + evidence | March | First page leads with the multimedia claim; ablations planned | `acmmm-writing-style`, `acmmm-experiments` | | Abstract | Mar 25 | Abstract registered in OpenReview | `acmmm-submission` | | Paper | Apr 1 | 6–8 sigconf pages, anonymous, final PDF | `acmmm-submission` | | Supplement | Apr 8 | Media/appendix package, anonymous, plays | `acmmm-supplementary` | | Rebuttal | ~Jun 4 | Anonymous response, small confirmatory results | `acmmm-author-response` | | Notification | ~early Jul | Decision + tier | `acmmm-review-process` | | Camera-ready | ~Aug 6 | De-anonymized ACM version, artifact released | `acmmm-camera-ready` | | Conference | Nov 10–14 | Registered; media-ready talk/poster | `acmmm-camera-ready` |
Treat these dates as the 2026 snapshot; reopen the current site each cycle. Note the 2026 notification date was listed inconsistently (July 7 on the CFP vs. July 9 elsewhere).
Front-loaded work (before April)
The April chain is unforgiving because three deadlines land in eight days. Do the slow work early:
- Lock the **thematic area and track** — they set format and blinding, and switching late is
expensive.
- Build the **cross-modal evidence**: matched baselines and the leave-one-modality-out
ablation that proves the fusion matters.
- Plan any **user study** now; recruiting raters cannot be done in the final week.
- Draft so the first page already leads with the multimedia contribution.
The three-deadline sprint
T-14d: freeze claims; media assets rendering from scripts
T-7d: body fits 6-8 sigconf pages; references on overflow pages only
Mar 25: abstract registered (do not miss the earliest deadline)
Apr 1: paper PDF final, anonymous, metadata-clean
Apr 8: supplement packaged, anonymous, media plays for a stranger
The long gap and the rebuttal
Between April and June, prepare the confirmatory experiments a reviewer is likely to ask for (the missing baseline, the extra ablation) so the June rebuttal is a matter of *reporting* results, not scrambling to run them.
Back end (July–November)
- On acceptance, de-anonymize, complete ACM rights/CCS, and release the public artifact.
- Register early and plan travel to **Rio**; visas and international logistics are the usual
failure.
- Build a presentation that **plays the media** — the seam between modalities should be
seen/heard, not just described.
- On rejection, use the reviews to re-target: MM Asia, ICMR, a workshop, or next year's MM.
Risk register
| Risk | Where it bites | Mitigation | |---|---|---| | Missing the abstract deadline | Mar 25 forecloses the paper | Register the abstract days early | | Wrong track blinding | Desk reject | Confirm the track call before formatting | | Fusion not shown to matter | Reviews / rebuttal | Run the leave-one-modality-out ablation pre-submission | | User study not recruited in time | Perceptual claim unbacked | Start recruiting before April | | Broken anonymous media link | Lost evidence in review | Test the mirror from a clean machine | | Rio travel/visa delay | Cannot present | Start visa paperwork at acceptance |
Re-targeting after a rejection
An ACM MM rejection is not the end of the work. Match the reviews to the next move: a retrieval-leaning paper can go to **ICMR**; a systems-leaning one to **MMSys**; a regionally scoped or earlier-stage result to **ACM Multimedia Asia** or a **workshop**; a matured version to the **ACM TOMM** journal or next year's ACM MM. Fix the decisive critique — usually the cross-modal-significance one — before resubmitting anywhere.
Output format
[Current phase] <scope/draft/abstract/paper/supplement/rebuttal/decision/camera-ready/conference>
[On track?] yes / at-risk: <what slips>
[Next deadline] <date + deliverable>
[Active skill] <which skill to run now>
[Risks] <ordered>
Read more
name: acmmm-workflow description: Use when planning the end-to-end ACM MM (ACM Multimedia) campaign calendar — from thematic-area scoping and track choice, through the April OpenReview abstract/paper/supplement chain, the June anonymous rebuttal, the July decision, the August camera-ready, and the November presentation in Rio, with the right skill invoked at each stage.
ACM MM Workflow
Use this to run an ACM Multimedia submission as a scheduled campaign rather than a deadline scramble. The SIGMM calendar has a long gap between the April submission chain and the July decision, so the work clusters at the front and the back.
The ACM MM calendar (2026 anchors, AoE)
| Phase | 2026 date | What must be true | Skill | |---|---|---|---| | Scope + track choice | pre-March | Contribution is cross-modal; thematic area and track chosen | `acmmm-topic-selection` | | Draft + evidence | March | First page leads with the multimedia claim; ablations planned | `acmmm-writing-style`, `acmmm-experiments` | | Abstract | Mar 25 | Abstract registered in OpenReview | `acmmm-submission` | | Paper | Apr 1 | 6–8 sigconf pages, anonymous, final PDF | `acmmm-submission` | | Supplement | Apr 8 | Media/appendix package, anonymous, plays | `acmmm-supplementary` | | Rebuttal | ~Jun 4 | Anonymous response, small confirmatory results | `acmmm-author-response` | | Notification | ~early Jul | Decision + tier | `acmmm-review-process` | | Camera-ready | ~Aug 6 | De-anonymized ACM version, artifact released | `acmmm-camera-ready` | | Conference | Nov 10–14 | Registered; media-ready talk/poster | `acmmm-camera-ready` |
Treat these dates as the 2026 snapshot; reopen the current site each cycle. Note the 2026 notification date was listed inconsistently (July 7 on the CFP vs. July 9 elsewhere).
Front-loaded work (before April)
The April chain is unforgiving because three deadlines land in eight days. Do the slow work early:
- Lock the **thematic area and track** — they set format and blinding, and switching late is
expensive.
- Build the **cross-modal evidence**: matched baselines and the leave-one-modality-out
ablation that proves the fusion matters.
- Plan any **user study** now; recruiting raters cannot be done in the final week.
- Draft so the first page already leads with the multimedia contribution.
The three-deadline sprint
T-14d: freeze claims; media assets rendering from scripts T-7d: body fits 6-8 sigconf pages; references on overflow pages only Mar 25: abstract registered (do not miss the earliest deadline) Apr 1: paper PDF final, anonymous, metadata-clean Apr 8: supplement packaged, anonymous, media plays for a stranger
The long gap and the rebuttal
Between April and June, prepare the confirmatory experiments a reviewer is likely to ask for (the missing baseline, the extra ablation) so the June rebuttal is a matter of *reporting* results, not scrambling to run them.
Back end (July–November)
- On acceptance, de-anonymize, complete ACM rights/CCS, and release the public artifact.
- Register early and plan travel to **Rio**; visas and international logistics are the usual
failure.
- Build a presentation that **plays the media** — the seam between modalities should be
seen/heard, not just described.
- On rejection, use the reviews to re-target: MM Asia, ICMR, a workshop, or next year's MM.
Risk register
| Risk | Where it bites | Mitigation | |---|---|---| | Missing the abstract deadline | Mar 25 forecloses the paper | Register the abstract days early | | Wrong track blinding | Desk reject | Confirm the track call before formatting | | Fusion not shown to matter | Reviews / rebuttal | Run the leave-one-modality-out ablation pre-submission | | User study not recruited in time | Perceptual claim unbacked | Start recruiting before April | | Broken anonymous media link | Lost evidence in review | Test the mirror from a clean machine | | Rio travel/visa delay | Cannot present | Start visa paperwork at acceptance |
Re-targeting after a rejection
An ACM MM rejection is not the end of the work. Match the reviews to the next move: a retrieval-leaning paper can go to **ICMR**; a systems-leaning one to **MMSys**; a regionally scoped or earlier-stage result to **ACM Multimedia Asia** or a **workshop**; a matured version to the **ACM TOMM** journal or next year's ACM MM. Fix the decisive critique — usually the cross-modal-significance one — before resubmitting anywhere.
Output format
[Current phase] <scope/draft/abstract/paper/supplement/rebuttal/decision/camera-ready/conference> [On track?] yes / at-risk: <what slips> [Next deadline] <date + deliverable> [Active skill] <which skill to run now> [Risks] <ordered>
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

