iros-related-work
Use when positioning an IROS submission against robotics-systems literature across ICRA, IROS, RSS, CoRL, RA-L, and T-RO, covering the lanes embodied-systems reviewers check, concurrent arXiv work, prior-version overlap, IEEE Xplore archival status, and keeping self-citations anonymous under the double-anonymous cycle.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-related-work --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 Related Work Use this to audit novelty and eligibility. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors. At IROS the question a reviewer asks is not only "is this new?" but "does the paper know the nearest *systems* it resembles and say what it does differently?" ## Positioning checks - Separate a **systems contribution** from a component tweak: a new integration, a new capability under a constraint, a new reliability level, or a deployment insight — not merely a swapped module. - Cover the robotics-systems lanes, not just the one nearest your method; a manipulation paper still owes the perception and planning neighbors it builds on. - Treat **IEEE Xplore proceedings, RA-L, and T-RO** as archival; position against them honestly rather than around them. - Cite arXiv and prior workshop versions so **double-anonymous review survives** — never point a reviewer to an identity-revealing page or repository. - Explain overlap with any prior or concurrent version of your own work, and do not submit duplicate archival material. ## The lanes robotics reviewers check | Lane | Typical sources | What IROS reviewers check | |---|--
- Positioning checks
- The lanes robotics reviewers check
- Concurrent-work judgment calls
- Positioning vignette
- Output format
What does the iros-related-work skill do?
Use when positioning an IROS submission against robotics-systems literature across ICRA, IROS, RSS, CoRL, RA-L, and T-RO, covering the lanes embodied-systems reviewers check, concurrent arXiv work, prior-version overlap, IEEE Xplore archival status, and keeping self-citations anonymous under the double-anonymous cycle.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-related-work --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 984 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.