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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-writing-style --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 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. - Budget **references as content**; they count against the page limit, so a bloated bibliography costs real space. - Convert **demo-speak to numbers**: "works robustly" becomes a trial count with a success interval and a failure taxonomy. - Keep **double-anonymous** wording clean in self-citations, prior-pla
- Revision rules
- Figure-first discipline
- Sentence-level rewrites
- Vignette: compressing into the page budget
- Output format
What does the iros-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-writing-style --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.