Individual skill
iros-writing-style
Use when revising an IROS paper for a task-first opening, an integrated-system narrative, the references-counted-in page budget with no supplementary PDF, double-anonymous wording, demo-speak-to-numbers rewrites, and figure-first structure that carries the argument in the body for embodied-systems reviewers.
IROS-Skills/skills/iros-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- 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,405
- 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
- finance Derived category
- writing Derived category
- 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,898 bytes
Read excerpt
# IROS Writing Style
Use this when revising the main paper. An IROS paper has to make a reviewer picture the robot, the task,
and the physical constraint quickly, then trust that the system runs — all inside a page budget that
counts references and offers no appendix escape hatch.
## Revision rules
- Open with the **robot task and the embodiment constraint**, not with "robots are increasingly
important." The first paragraph should name the platform, the task, and what makes it physically hard.
- Present the contribution as an **integrated system**: name the sensors, the interfaces between
components, and the compute/latency budget, so the pipeline is reconstructable from the body.
- Treat the **body as the whole paper** — IROS has no supplementary PDF. Anything load-bearing (metric
definition, protocol, key ablation) lives in the main text or it does not exist for the reviewer.