Acmmm Experiments logo

Acmmm Experiments

CommunityPopular
brycewang-stanford
acmmm-experiments

Use when designing or auditing the experiments of an ACM MM (ACM Multimedia) paper — matched baselines per modality, ablations that isolate the cross-modal fusion, user studies or QoE measurement where the claim is subjective, dataset and media licensing, and honest compute reporting, so evidence supports a multimedia claim.

Overview

Publisherbrycewang-stanford
RepositoryAwesome-Journal-Skills
Skill nameacmmm-experiments
Stars
1.2K
Forks
159
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by brycewang-stanford on GitHub. Read the source before you install it.

Installation

Install the Acmmm Experiments AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-MM-Skills/skills/acmmm-experiments
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git /tmp/Awesome-Journal-Skills
mkdir -p .claude/skills
cp -r /tmp/Awesome-Journal-Skills/ACM-MM-Skills/skills/acmmm-experiments .claude/skills/acmmm-experiments
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Acmmm Experiments in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Acmmm Experiments on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Acmmm Experiments is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

ACM MM Experiments

Use this to make an ACM Multimedia paper's evidence match its claim. The reviewer's implicit questions are: does it work, does the cross-modal part cause the gain, when does it fail, and — if the target is perceptual — do people actually prefer it.

The four questions and how to answer them

QuestionEvidence that answers it
Does it work?The headline metric on a recognized benchmark, against strong, matched baselines
Does the fusion cause the gain?A leave-one-modality-out / component ablation isolating the cross-modal term
When does it fail?Failure cases per modality (e.g., noisy audio, missing captions) shown honestly
Do people prefer it?A user study with reported N, protocol, and inter-rater agreement — for subjective claims

The second row is what separates an ACM MM experiment section from a single-modality one: if removing a modality does not move the result, the paper is not really cross-modal.

Matched baselines

  • Compare against the strongest existing method, re-run under your data and preprocessing where feasible, not a weakened reimplementation.
  • Include a late-fusion / naive-concatenation baseline so the reader sees what the fancy fusion buys over the obvious one.
  • Hold everything but the mechanism fixed: same backbone, same features, same training budget, so the delta is attributable.

Ablations that isolate the cross-modal claim

text
Full model .................... reference
- audio stream ................ tests whether audio carries signal
- text/caption stream ......... tests whether language carries signal
- alignment / fusion module ... replaced by concatenation: tests the MECHANISM
- synchronization assumption .. shuffled timing: tests whether cross-modal timing matters

Report each ablation with the same metric and variance as the headline, and state which term carries most of the gain — reviewers reward a paper that can point to why it works.

User studies and QoE

When the claim is subjective (quality, naturalness, engagement, aesthetics), a benchmark number is not enough:

  • Pre-register the protocol: task, number of raters, stimuli, and the question asked.
  • Report inter-rater agreement and a significance test, not just a mean preference.
  • Describe compensation and consent briefly; a study a reviewer cannot assess is discounted.

Data, media, and compute honesty

  • State dataset licenses and any consent/usage terms for media, especially for user-generated or scraped content.
  • Report compute (hardware, training time) so cost is legible; a cross-modal model that only wins at 10x compute should say so.
  • Fix and report seeds; report variance over runs where the margin is small.

Benchmarks and metrics per modality

A cross-modal paper is judged against each community's expectations at once, so pick metrics each sub-field recognizes rather than a single convenient number.

  • Retrieval / recommendation — report ranking metrics (Recall@K, mAP, NDCG) and say which gallery/query split, because cross-modal retrieval numbers are split-sensitive.
  • Generation / synthesis — pair a distributional metric with a human/QoE judgment; automatic scores for generated media correlate imperfectly with perceived quality.
  • Recognition / detection — use the standard task metric, but show the multimodal case, not only the clean single-modality one.
  • Systems / delivery — report latency, throughput, and bitrate/quality trade-offs, not just accuracy.

State the metric's direction and any threshold, and keep the same metric across the headline table and every ablation so the reader can trace the fusion's contribution row by row.

Statistical reporting

  • Report variance (standard deviation or confidence interval) over runs when margins are small; a single-seed win on a close benchmark is not persuasive.
  • For user studies, report a significance test and inter-rater agreement, not a bare mean.
  • Do not average away modality-specific behavior: a model that helps on audio-rich clips and hurts on silent ones should show that split, not hide it in a global mean.

Common ACM MM experiment failures

  • Fusion that does not matter — ablations show no modality is load-bearing.
  • Weak baselines — beating only a vision-only or text-only strawman.
  • Asserted perception — "more natural" with no user study.
  • Unlicensed media — datasets used without stating rights.
  • Hidden cost — big gains that quietly require far more compute.

Output format

text
[Works] strong/matched baselines / weak or unmatched: <which>
[Fusion causal] ablation isolates the mechanism / does not
[Failure analysis] present per modality / missing
[Perceptual claim] user study with agreement / asserted
[Data + compute] licenses and cost reported / gaps: <list>
[Top fixes] <ordered before submission or rebuttal>

Frequently asked questions

What does the Acmmm Experiments AI skill do?

Use when designing or auditing the experiments of an ACM MM (ACM Multimedia) paper — matched baselines per modality, ablations that isolate the cross-modal fusion, user studies or QoE measurement where the claim is subjective, dataset and media licensing, and honest compute reporting, so evidence supports a multimedia claim.

Why use Acmmm Experiments on TypingMind?

Because you install it once and use it with any model. Acmmm Experiments is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Acmmm Experiments in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-MM-Skills/skills/acmmm-experiments. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Acmmm Experiments?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Acmmm Experiments?

As many as you like. As long as a model supports skills, you can use Acmmm Experiments with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Acmmm Experiments AI skill free?

Yes. It is published on GitHub by brycewang-stanford under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇