icra-artifact-evaluation
Use when packaging the artifacts behind an ICRA paper — ROS packages, controllers, simulation environments, trained policies, CAD and PCB files, datasets, and trial logs — into something a robotics reviewer or reader can actually run or audit, given that ICRA has no formal artifact-badging track to certify it for you.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-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.
# ICRA Artifact Evaluation ICRA, unlike several software-systems conferences, has had no standing artifact evaluation committee or badge system in recent cycles (re-check the current year's calls before asserting this to authors — tracks appear and disappear). The absence cuts both ways: nobody will certify your artifact, and nobody will catch its problems before readers do. This skill applies an artifact-evaluator's discipline voluntarily, because in robotics the artifact often *is* the contribution's proof. ## The robotics artifact stack A robotics paper's artifact is rarely just "the code." Inventory all six layers and decide, per layer, released / partially released / withheld-with-reason: | Layer | Typical contents | Common blocker | |---|---|---| | Algorithms | planners, controllers, learning code | none — release | | Integration | ROS launch files, configs, calibration | "works only on our stack" | | Simulation | worlds, robot models (URDF/SDF), randomization | third-party asset licenses | | Learned weights | trained policies, perception models | training data licensing | | Hardware design | CAD, PCB, BOM for custom parts | patent/commercialization plans | | Evidence | rosba
- The robotics artifact stack
- The five-minute-skeptic standard
- Hardware-dependent artifacts
- Datasets and logs as artifacts
- Review-time vs acceptance-time states
- Safety as an artifact property
- Withholding honestly
- Packaging sequence
- Output format
git clone <anonymized-artifact-url> && cd artifact docker build -t icra-artifact . # or: ./setup.sh — one command, pinned deps docker run icra-artifact make figure3 # regenerate a headline result in sim docker run icra-artifact make table2 # recompute stats from released logs cat CLAIMS.md # claim → command → expected output map
What does the icra-artifact-evaluation skill do?
Use when packaging the artifacts behind an ICRA paper — ROS packages, controllers, simulation environments, trained policies, CAD and PCB files, datasets, and trial logs — into something a robotics reviewer or reader can actually run or audit, given that ICRA has no formal artifact-badging track to certify it for you.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-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.