Individual skill

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.

IROS-Skills/skills/iros-related-work/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,411
Repository last updated: Sep 27, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

academic-writing Repository topic
agent-skills Repository topic
journal Repository topic
academic-research Repository topic
ai-agents Repository topic
anthropic Repository topic
awesome-list Repository topic
claude Repository topic
claude-code Repository topic
economics Repository topic
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,798 bytes

Read excerpt


# 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