icra-reproducibility
Use when hardening an ICRA paper's reproducibility — specifying robot platform, firmware, ROS and driver versions, control rates, and sensor calibration; logging rosbags and seeds; separating what others can rerun (code, sim) from what they can only audit (your hardware trials); and writing honest availability statements.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-reproducibility --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 Reproducibility Reproducibility at a robotics conference means something different than at an ML venue: no reader can rerun your hardware trials without your robot, your room, and your objects. The achievable standard is therefore two-tier — **rerunnable** (code, simulation, analysis) and **auditable** (hardware evidence logged well enough that a skeptic can verify you did what you claim). ICRA papers earn trust by being explicit about which tier each result sits in. ## The specification ledger A robotics result is unreproducible if the platform is underspecified. The paper (body, since there is no appendix escape) plus released materials should pin: | Layer | Must specify | Example of "enough" | |---|---|---| | Robot | model, DOF, payload, firmware version | "UR5e, PolyScope 5.11" | | End effector | model, mods, wear state if relevant | "Robotiq 2F-85, stock pads" | | Sensors | model, resolution, rate, mounting frame | "D435i @ 640×480, 30 Hz, wrist" | | Compute | on-board vs off-board, GPU, latency path | "off-board 3080, 5G-free wired" | | Middleware | ROS distro, key package versions | "ROS 2 Humble, MoveIt 2.5.4" | | Control | loop rates, gains or their source | "impeda
- The specification ledger
- Logging: the rosbag is the lab notebook
- Determinism where it exists, honesty where it doesn't
- Release scaffold
- Compute and latency reporting
- Availability statement patterns
- Pre-submission reproducibility pass
- Output format
What does the icra-reproducibility skill do?
Use when hardening an ICRA paper's reproducibility — specifying robot platform, firmware, ROS and driver versions, control rates, and sensor calibration; logging rosbags and seeds; separating what others can rerun (code, sim) from what they can only audit (your hardware trials); and writing honest availability statements.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icra-reproducibility --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.