icml-artifact-evaluation
Use when packaging ICML artifacts - code, data, model weights, simulators, benchmarks, proof scripts, notebooks, anonymous repositories, and supplementary code/data ZIPs - for both the double-blind review package and the public release that accompanies accepted PMLR papers. Use when checking anonymity, decision relevance, licensing, and the OpenReview code URL field under current ICML rules.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icml-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ICML Artifact Evaluation ICML does not let artifacts sit outside the paper's scientific argument. Reproducibility and code availability are explicitly considered in decision-making, and accepted submissions may publish the original supplementary material on OpenReview. ## Review-stage package - Decide whether the artifact is code, data, model weights, simulator, benchmark, proof script, notebook, or supplementary manuscript. - Anonymize authors, repository ownership, filenames, commit history, logs, model cards, dataset cards, licenses, and personal paths. - If using an anonymous repository, put it on a branch that will not change after the submission deadline. - Put critical evaluation material in the paper body, not only in supplement. Reviewers decide whether to consult appendices or supplementary material. - Provide minimal commands, environment details, expected runtime, hardware assumptions, and result mapping. ## Public-release package - Because accepted original supplementary material may become public, review-stage artifacts should not contain private, illegal, or unreleasable content. - For camera-ready, final supplementary material is not uploaded separately; code/data
- Review-stage package
- Public-release package
- Anonymity leak checklist
- Worked vignette: optimizer artifact package
- Output format
What does the icml-artifact-evaluation skill do?
Use when packaging ICML artifacts - code, data, model weights, simulators, benchmarks, proof scripts, notebooks, anonymous repositories, and supplementary code/data ZIPs - for both the double-blind review package and the public release that accompanies accepted PMLR papers. Use when checking anonymity, decision relevance, licensing, and the OpenReview code URL field under current ICML rules.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icml-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.