iros-artifact-evaluation
Use when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code, and data, what an embodied-systems reviewer opens first, review-time anonymity versus acceptance-time public release, and making a claim auditable not asserted.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-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.
# IROS Artifact Evaluation IROS has no formal artifact-evaluation track or badge, so "artifact" here means the evidence bundle a reviewer *could* inspect and that a careful author prepares anyway. The audience is an embodied-systems reviewer who trusts a logged trajectory over a claimed one, and who cannot rerun your robot but can read your logs, configs, and code. ## The robotics artifact stack - **Hardware ledger:** platform, sensors (make/model/firmware), actuators, onboard computer, and power budget — the embodiment the result depends on. - **Logs:** time-stamped rosbag-equivalent recordings for representative trials, so a claim about a contact force or trajectory is auditable. - **Configs:** the exact parameters, calibration, and launch files that produced the reported runs. - **Code:** the system as run, with an entry point and a one-minute orientation in the README. - **Data:** any dataset or object set, with provenance and licensing; for restricted data, enough detail for credible reproduction without violating terms. ## What an IROS reviewer inspects first | Claim type | First artifact inspected | Common failure caught | |---|---|---| | "Runs onboard at rate X" | Timing lo
- The robotics artifact stack
- What an IROS reviewer inspects first
- Review-time versus acceptance-time states
- Worked vignette: packaging a field-robot result
- Output format
What does the iros-artifact-evaluation skill do?
Use when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code, and data, what an embodied-systems reviewer opens first, review-time anonymity versus acceptance-time public release, and making a claim auditable not asserted.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-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.