Skip to content
cccskills
FreePublished on GitHub

acmmm-related-work

Use when building or auditing the related-work section of an ACM MM (ACM Multimedia) paper — covering the multimedia literature spread across vision, audio/speech, language, HCI/QoE, and systems, handling arXiv-speed concurrency, keeping citations double-blind, and verifying that cited "ACM MM papers" are ACM MM and not ICMR, MMSys, CVPR, or TOMM.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md4.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

ACM MM Related Work

Use this to position an ACM Multimedia paper against a literature that is unusually spread out: a cross-modal contribution touches several single-modality communities plus the multimedia venues that combine them.

The five multimedia shelves

A strong ACM MM related-work section shows command of all shelves the contribution touches, not just the author's home community:

  • Vision — the visual side (CVPR/ICCV/ECCV) your method builds on or competes with.
  • Audio/speech and music — the acoustic side (ICASSP, INTERSPEECH, ISMIR) if a stream is audio.
  • Language — the text side (ACL/EMNLP) if captions, transcripts, or descriptions matter.
  • HCI / QoE / human-centric — perception, engagement, and interaction (CHI, QoMEX) when the claim is subjective.
  • Multimedia proper — ACM MM, ICMR, MMSys, and TOMM, where these threads are combined.

Coverage vs. venue-hygiene table

TaskWhat to doFailure it prevents
Cover each modality you useCite the current best single-modality work per stream"You ignored the vision literature"
Cite the fusion lineageTrace the cross-modal line your method extends"No delta over existing fusion"
Verify the venue stringConfirm each "ACM MM" cite on dblp conf/mmMisattributing an ICMR/CVPR paper to ACM MM
Handle concurrencyNote contemporaneous arXiv work honestly"You missed / overclaimed novelty vs. X"
Keep it blindCite your own prior work in third personDouble-blind violation

Positioning, not listing

Do not enumerate. For each closest neighbor, state in one clause what it did and in one clause what your paper adds — and make sure the delta is cross-modal, since "we swap a better encoder" is a single-modality delta a reviewer will discount.

[Neighbor] Late-fusion audio-visual highlight scoring (VenueYear).
[Their move] Average per-modality scores.
[Our delta] Score the timing DISAGREEMENT between streams — a signal averaging cannot represent.

Concurrency under arXiv speed

Multimedia sub-areas move fast and preprint heavily. Acknowledge genuinely concurrent work (roughly same-window preprints) as concurrent rather than prior, do not claim to beat a method you did not run, and do not silently drop a close preprint — a reviewer who knows it reads the omission as evasion.

Double-blind citation hygiene

  • Cite your own earlier papers in the third person ("Prior work [X] showed..."), never "our previous paper."
  • Avoid anonymity leaks through a dataset, system name, or repository that only your group uses.
  • The single-blind tracks (Reproducibility, Open Source Software, Dataset) relax this — but the main track and Brave New Ideas do not.

Building the section in passes

Pass 1: list the modalities and sub-fields your contribution touches (the shelves).
Pass 2: for each shelf, cite the current strongest 2-3 works you build on or beat.
Pass 3: trace the FUSION lineage — the cross-modal line your method extends — as its own thread.
Pass 4: add same-window arXiv work as concurrent, not prior.
Pass 5: verify every "ACM MM" cite on dblp; convert your self-cites to third person.

A reader should finish the section able to name which prior fusion approach you improve on and why the single-modality shelves are covered but not the whole story.

The multimedia-specific omission risk

Because a cross-modal paper sits between communities, the dangerous omission is usually the other community's closest work — a vision-trained author who misses the audio or IR paper that already did half the job. Before submitting, ask a question from each shelf's perspective: "what would an audio reviewer, an IR reviewer, and a systems reviewer each say I missed?" That triage catches the omissions that sink cross-area papers.

Venue-verification pass

Before submission, spot-check every citation that claims an ACM MM placement against dblp's conf/mm edition record. The common traps: ICMR papers cited as ACM MM, TOMM journal articles cited as the conference, and CVPR/ICCV vision papers cited as multimedia. Fix the venue string or the claim that rests on it.

Output format

[Shelf coverage] vision/audio/language/HCI-QoE/multimedia — <covered / gaps>
[Fusion lineage] traced / missing
[Deltas] cross-modal and specific / single-modality or vague: <list>
[Concurrency] handled / risky omissions: <list>
[Blindness] clean / leaks: <list>
[Venue hygiene] verified / suspect cites: <list>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 before SPC/AC discussion.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 final public artifact release.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 reproducibility-checklist alignment for Phase-1 survival.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 related-work section legible to non-specialist reviewers.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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 Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

See all skills by brycewang-stanford

Report a problem with this skill