corl-artifact-evaluation
Use when packaging the artifacts of a CoRL paper — code, training configs, demonstration datasets, policy checkpoints, simulation environments, and benchmark definitions — as anonymous review-time evidence and as durable public releases after acceptance, in a venue with no formal artifact-badging track.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-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.
# CoRL Artifact Evaluation CoRL has no separate artifact-evaluation track or badge system in the 2026 materials verified for this pack (a formal AE track remains 待核实 each cycle). Artifacts are instead judged twice, informally: by reviewers deciding whether to trust your tables, and by the community deciding — for years afterward — whether your method becomes a baseline. Package for both audiences from the start. ## Artifact inventory for a robot-learning paper | Artifact | Review-time form (anonymous) | Public form (post-acceptance) | |---|---|---| | Training code + configs | Scrubbed ZIP in the supplementary | GitHub repo, tagged release matching the paper | | Evaluation harness | Same ZIP; scripts + fixed init-state lists | Same repo; the part reused most by others | | Demonstration data | Small sample in ZIP; full set described | Archive with DOI + datasheet, license stated | | Policy checkpoints | Optional if small; else described | Hosted weights keyed to each results table | | Sim environments / tasks | Env definitions + versions in ZIP | Repo or upstream PR to the benchmark suite | | Hardware recipe | Appendix spec (rig, control interface) | Project page: BOM-level detail, p
- Artifact inventory for a robot-learning paper
- The reuse test
- Review-time packaging (anonymous)
- Post-acceptance: durable release
- Benchmarks and datasets as first-class artifacts
- Failure patterns that surface after publication
- Release checklist
What does the corl-artifact-evaluation skill do?
Use when packaging the artifacts of a CoRL paper — code, training configs, demonstration datasets, policy checkpoints, simulation environments, and benchmark definitions — as anonymous review-time evidence and as durable public releases after acceptance, in a venue with no formal artifact-badging track.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill corl-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.