/acmmm-artifact-evaluation
Use when packaging code, models, datasets, or media as ACM MM (ACM Multimedia) artifacts — building the anonymous review package versus the public release, and choosing between the Open Source Software Competition, the Dataset track, the Reproducibility track, and main-track
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill acmmm-artifact-evaluation --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-artifact-evaluation
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when packaging code, models, datasets, or media as ACM MM (ACM Multimedia) artifacts — building the anonymous review package versus the public release, and choosing between the Open Source Software Competition, the Dataset track, the Reproducibility track, and main-track
SKILL.md
acmmm-artifact-evaluation.SKILL.mdname: acmmm-artifact-evaluation
description: Use when packaging code, models, datasets, or media as ACM MM (ACM Multimedia) artifacts — building the anonymous review package versus the public release, and choosing between the Open Source Software Competition, the Dataset track, the Reproducibility track, and main-track supplementary evidence, each with its own blinding and expectations.
ACM MM Artifact Evaluation
Use this to turn an ACM Multimedia project's code, models, media, and data into the *right* artifact for the *right* track. ACM MM has a track economy around artifacts, and the choice determines blinding, format, and what reviewers judge.
Which track is the artifact?
| Artifact is primarily... | Route to | Blinding | Judged on | |---|---|---|---| | A reusable software system/framework | Open Source Software Competition | Single-blind | Adoption, quality, license, docs | | A new dataset/benchmark | Dataset track | Single-blind | Scale, quality, ethics, usefulness | | A reproduction of published results | Reproducibility track | Single-blind | Whether results rebuild; ACM badges | | Supporting evidence for a method paper | Main-track supplement | Double-blind | Whether it backs the paper's claims |
The named single-blind tracks exist *because* the artifact's identity cannot be hidden; a main-track method paper's artifact, by contrast, must be **anonymous** through review.
Two artifacts, two audiences
Plan both from the start:
- **Anonymous review artifact** — what reviewers see during double-blind review: an
anonymized repository, an anonymous data mirror, stripped media metadata, and a README that reveals no author identity.
- **Public release artifact** — what ships at/after camera-ready: the de-anonymized
repository, a permanent archive (DOI), the license, and the final dataset/model.
review/ -> anonymous repo, anon data mirror, no names in code/media, run instructions
release/ -> public repo + DOI, LICENSE, model weights, dataset card, citation
Open Source Software Competition
- The bar is a system others will *use*: clear install, documentation, examples, an
OSI-approved license, and evidence of quality or adoption.
- Reference models and reproducible examples matter more than a single benchmark number —
this is the lane exemplified by community frameworks and portable libraries.
Dataset track
- Ship a **dataset card**: collection method, size, splits, license, consent, and known
biases or limitations.
- Address ethics and rights explicitly, especially for user-generated or scraped media; a
dataset a reviewer cannot legally use is not a contribution.
Licensing and rights decisions
- Choose a code license (permissive vs. copyleft) and a **data** license separately; they are
not the same choice.
- For media, confirm you have the right to redistribute; where you cannot, provide a
retrieval script or agreement path instead of the raw files.
- Record third-party asset licenses so the release is clean.
Ethics and consent for media artifacts
Multimedia artifacts carry people's faces, voices, and content, so the ethics review is not a formality:
- **Consent and rights** — confirm you may redistribute the media; user-generated content often
cannot be re-hosted, so ship a retrieval script or agreement path instead.
- **Privacy** — remove or justify identifiable individuals who did not consent; a dataset of
scraped faces is a rejection risk regardless of its scale.
- **Documentation** — a dataset card that states collection method, consent, license, and known
biases is part of the contribution, not paperwork.
Timeline: review artifact, then release
before paper deadline: anonymous review artifact ready (repo + data mirror, no identity)
during review: reviewers/AC access the anonymous artifact
on acceptance: build the public release (de-anonymized repo + DOI + license)
by camera-ready: release replaces the anonymous mirror; dataset/model final
Plan the public release early even though it ships late — a scramble at camera-ready is how projects end up with a broken anonymous link and no working public archive.
Output format
[Track] Open Source / Dataset / Reproducibility / main-track supplement
[Blinding] correct for track / mismatch
[Review artifact] anonymous + runnable / gaps: <list>
[Release artifact] archived + licensed / gaps: <list>
[Rights] code+data+media licenses set / open questions: <list>
[Top fixes] <ordered>
Read more
name: acmmm-artifact-evaluation description: Use when packaging code, models, datasets, or media as ACM MM (ACM Multimedia) artifacts — building the anonymous review package versus the public release, and choosing between the Open Source Software Competition, the Dataset track, the Reproducibility track, and main-track supplementary evidence, each with its own blinding and expectations.
ACM MM Artifact Evaluation
Use this to turn an ACM Multimedia project's code, models, media, and data into the *right* artifact for the *right* track. ACM MM has a track economy around artifacts, and the choice determines blinding, format, and what reviewers judge.
Which track is the artifact?
| Artifact is primarily... | Route to | Blinding | Judged on | |---|---|---|---| | A reusable software system/framework | Open Source Software Competition | Single-blind | Adoption, quality, license, docs | | A new dataset/benchmark | Dataset track | Single-blind | Scale, quality, ethics, usefulness | | A reproduction of published results | Reproducibility track | Single-blind | Whether results rebuild; ACM badges | | Supporting evidence for a method paper | Main-track supplement | Double-blind | Whether it backs the paper's claims |
The named single-blind tracks exist *because* the artifact's identity cannot be hidden; a main-track method paper's artifact, by contrast, must be **anonymous** through review.
Two artifacts, two audiences
Plan both from the start:
- **Anonymous review artifact** — what reviewers see during double-blind review: an
anonymized repository, an anonymous data mirror, stripped media metadata, and a README that reveals no author identity.
- **Public release artifact** — what ships at/after camera-ready: the de-anonymized
repository, a permanent archive (DOI), the license, and the final dataset/model.
review/ -> anonymous repo, anon data mirror, no names in code/media, run instructions release/ -> public repo + DOI, LICENSE, model weights, dataset card, citation
Open Source Software Competition
- The bar is a system others will *use*: clear install, documentation, examples, an
OSI-approved license, and evidence of quality or adoption.
- Reference models and reproducible examples matter more than a single benchmark number —
this is the lane exemplified by community frameworks and portable libraries.
Dataset track
- Ship a **dataset card**: collection method, size, splits, license, consent, and known
biases or limitations.
- Address ethics and rights explicitly, especially for user-generated or scraped media; a
dataset a reviewer cannot legally use is not a contribution.
Licensing and rights decisions
- Choose a code license (permissive vs. copyleft) and a **data** license separately; they are
not the same choice.
- For media, confirm you have the right to redistribute; where you cannot, provide a
retrieval script or agreement path instead of the raw files.
- Record third-party asset licenses so the release is clean.
Ethics and consent for media artifacts
Multimedia artifacts carry people's faces, voices, and content, so the ethics review is not a formality:
- **Consent and rights** — confirm you may redistribute the media; user-generated content often
cannot be re-hosted, so ship a retrieval script or agreement path instead.
- **Privacy** — remove or justify identifiable individuals who did not consent; a dataset of
scraped faces is a rejection risk regardless of its scale.
- **Documentation** — a dataset card that states collection method, consent, license, and known
biases is part of the contribution, not paperwork.
Timeline: review artifact, then release
before paper deadline: anonymous review artifact ready (repo + data mirror, no identity) during review: reviewers/AC access the anonymous artifact on acceptance: build the public release (de-anonymized repo + DOI + license) by camera-ready: release replaces the anonymous mirror; dataset/model final
Plan the public release early even though it ships late — a scramble at camera-ready is how projects end up with a broken anonymous link and no working public archive.
Output format
[Track] Open Source / Dataset / Reproducibility / main-track supplement [Blinding] correct for track / mismatch [Review artifact] anonymous + runnable / gaps: <list> [Release artifact] archived + licensed / gaps: <list> [Rights] code+data+media licenses set / open questions: <list> [Top fixes] <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

