ICRA Skills

A 12-skill depth pack for ICRA (IEEE International Conference on Robotics and Automation) submissions: venue routing including the RA-L-with-conference-presentation pathway, PaperPlaza submission audits, the 6+2 page rule, video attachments, real-robot evidence standards, review-process modeling, camera-ready and IEEE Xplore publication. Grounded in the ICRA 2026 (Vienna) cycle and the announced I

by @brycewang-stanford 11 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/icra-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 11 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-icra-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 11
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Icra Submission · brycewang-stanford
Use when auditing an ICRA paper for upload — PaperPlaza account and metadata, the 6-page-plus-2-reference-page limit, IEEE two-column template compliance, the double-anonymous rule introduced in the 2026 cycle, video-attachment specs (180 s, 20 MB), dual-submission conflicts with RA-L, and return-without-review triggers.

1k repo stars
▌
Icra Experiments · brycewang-stanford
Use when designing or auditing the experimental section of an ICRA paper — real-robot versus simulation-only evidence, trial counts and success-rate reporting, task distributions and resets, baseline fairness on shared hardware, sim-to-real transfer claims, failure-mode analysis, and the statistics robotics reviewers actually expect.

1k repo stars
▌
Icra Camera Ready · brycewang-stanford
Use when converting an accepted ICRA paper into its final form — the 8-page total limit including references, de-anonymization after double-anonymous review, PaperPlaza final upload and PDF compliance, IEEE electronic copyright transfer, final video, author registration requirements, and IEEE Xplore publication.

1k repo stars
▌
Icra Related Work · brycewang-stanford
Use when building or auditing the related-work section of an ICRA paper — covering the conference's own recent proceedings plus IROS, RSS, CoRL, RA-L, and T-RO lanes, handling arXiv-only robotics work, citing your own platform papers under ICRA's double-anonymous rules, and positioning against commercial systems.

1k repo stars
▌
Icra Supplementary · brycewang-stanford
Use when planning ICRA supplementary material, which in this venue means primarily the video attachment — 180 seconds, 20 MB, submitted in fixed PaperPlaza windows — plus external code links; covers storyboarding, showing failures, anonymization of footage, and what may never live only outside the 6+2-page PDF.

1k repo stars
▌
Icra Writing Style · brycewang-stanford
Use when drafting or tightening an ICRA manuscript — leading with the robot task and physical constraint, compressing a systems story into 6 IEEE two-column pages, writing figure-first for skimming reviewers, quantifying instead of demo-speak, and keeping notation consistent across kinematics, control, and learning sections.

1k repo stars
▌
Icra Review Process · brycewang-stanford
Use when explaining or strategizing around ICRA's review pipeline — the RAS Conference Editorial Board of Editors and Associate Editors, reviewer recruitment through PaperPlaza, the absence of an author rebuttal in the classic ICRA flow, the January accept/reject decision, and how this differs from RA-L's revise-capable journal review.

1k repo stars
▌
Icra Author Response · brycewang-stanford
Use when responding to ICRA reviews in the channels that actually exist — turning decision-day reviewer comments into a disciplined camera-ready revision, writing the revise-and-resubmit response letter on the RA-L pathway, or converting an ICRA reject into a targeted IROS or RA-L resubmission — since classic ICRA offers no rebuttal.

1k repo stars
▌
Icra Reproducibility · brycewang-stanford
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.

1k repo stars
▌
Icra Topic Selection · brycewang-stanford
Use when deciding whether a robotics project belongs at ICRA, choosing between a direct ICRA submission and the RA-L journal route with conference presentation, or re-routing to IROS, RSS, CoRL, T-RO, HRI, or CASE based on contribution type, evidence shape, and the embodiment test.

1k repo stars
▌
Icra Artifact Evaluation · brycewang-stanford
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.

1k repo stars