iclr-artifact-evaluation
Use when packaging ICLR code, data, checkpoints, demos, logs, and reproduction instructions for reviewers or post-acceptance release, including anonymized links and private OpenReview discussion-period sharing. Use when a reviewer asks for a missing repro path, when a public comment questions whether claims can be verified, or when converting an anonymous supplement into a durable post-acceptance release for the permanent ICLR record.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-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.
# ICLR Artifact Evaluation Use this to prepare artifacts that make an ICLR paper reproducible and reviewable. ICLR may not run a separate artifact-badge process for every paper, so the practical bar is whether reviewers and ACs can verify the claims without identity leakage or excessive setup. ## Artifact package - Provide a minimal reproduction path for every central table or figure: command, config, seed, expected runtime, hardware, and expected output file. - Include data provenance, preprocessing scripts, licenses, and any access restrictions. - Separate heavy checkpoints or datasets from the core anonymized supplement when file-size limits require it; document private reviewer links clearly. - Remove usernames, organization names, cloud buckets, Git history, API keys, and metadata that can deanonymize authors. - Add a smoke-test script that runs in minutes and confirms environment integrity. - Mark any unreleasable component and give a defensible reason, not a vague "proprietary" note. ## ICLR-specific handling - Submit supplementary material by the paper deadline when the current Author Guide requires it. - During discussion, use private links or revised supplements only with
- Artifact package
- ICLR-specific handling
- What reviewers actually open
- Worked vignette
- Reviewer-pushback patterns
- Output format
What does the iclr-artifact-evaluation skill do?
Use when packaging ICLR code, data, checkpoints, demos, logs, and reproduction instructions for reviewers or post-acceptance release, including anonymized links and private OpenReview discussion-period sharing. Use when a reviewer asks for a missing repro path, when a public comment questions whether claims can be verified, or when converting an anonymous supplement into a durable post-acceptance release for the permanent ICLR record.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iclr-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.