Use when targeting Robotics: Science and Systems (RSS) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for robotics flagship.
Robotics: Science and Systems (RSS) is a top computer-science conference venue for robotics science, algorithms, perception, manipulation, control, learning, and theory for robots. It rewards a robotics paper with concentrated scientific novelty and rigorous embodied evidence. Treat this skill as a fit / venue-selection / re-framing tool for conference submission strategy, not as a substitute for the current year's CFP, author kit, ethics policy, or submission portal.
Because CS conferences change deadlines, templates, page limits, review workflow, artifact rules, AI-use policy, and rebuttal formats every cycle, always verify the live official instructions before making a submission-ready recommendation. Start from the official source anchor recorded for this venue in ../../resources/conference-roster.md and ../../resources/official-source-map.md.
When to trigger
The author names RSS / Robotics: Science and Systems as the target venue.
A manuscript in robotics science needs a conference-fit read before being formatted or submitted.
The paper must be re-framed from journal style or arXiv style into a selective CS conference narrative.
The author needs an evidence-gap, anonymity, artifact, rebuttal, or re-routing diagnosis for this venue.
Scope & topic fit
Core fit: robotics science, algorithms, perception, manipulation, control, learning, and theory for robots.
Best submissions make a precise contribution type visible: algorithm, theorem, system, dataset, benchmark, empirical finding, design artifact, tool, or socio-technical analysis.
The paper should explain why the result matters to RSS's reviewers, not just why it is interesting to the authors' lab or product context.
Position related work against the most recent conference-cycle papers in this venue and its closest siblings; stale comparisons are a common early-review weakness.
If the contribution is interdisciplinary, state which part is CS research and which part is domain evidence.
Venue-specific calibration
Reviewer lens: Read reviewers as embodied-systems researchers. Hardware, simulation, task distributions, and failure rates matter more than a clean curve alone.
Contribution hook to foreground: the venue-specific contribution bar.
Scope vocabulary to use naturally in the abstract and introduction: robotics science, algorithms, perception, manipulation, control, learning, and theory for robots.
Official anchor domain: roboticsconference.org. Quote annual rules only after opening that source and the current-year CFP/author kit.
Close-neighbor routing guardrail
Use this profile only when the manuscript's central contribution is genuinely in robotics
flagship and the author can say why RSS reviewers are the primary audience, not merely a
convenient deadline.
Closest roster neighbors to compare before final routing: ieee-international-conference-on- robotics-and-automation (ICRA), ieee-rsj-international-conference-on-intelligent-robots- and-systems (IROS), acm-ieee-international-conference-on-human-robot-interaction (HRI),
ieee-international-conference-on-robot-and-human-interactive-communication (RO-MAN). Break
ties by contribution type, evidence shape, reviewer community, and the current official CFP
from roboticsconference.org.
What distinguishes this venue from its closest siblings
Format.Single-track and highly selective, foundations/algorithmic-model forward — the deliberate contrast to the larger multi-track IEEE robotics venues ICRA (IEEE RAS) and IROS (IEEE/RSJ).
Center of gravity. Conceptual and algorithmic robotics contributions where the model or analysis is the result; hardware is evidence, not the headline.
Routing. Integrated-system or application breadth usually fits ICRA/IROS better; reserve RSS for results whose generality a single-track audience will reward.
Method & evidence bar
Report hardware, simulation, environment, task distribution, reset procedure, and failure cases; embodied evidence must be inspectable.
Compare against meaningful robot-learning, planning, or control baselines under matched assumptions.
Separate simulation gains from real-world transfer and quantify reliability, not only best-case success.
For RSS, the evidence must support the venue-specific signature: a robotics paper with concentrated scientific novelty and rigorous embodied evidence.
Include limitations, negative results, compute/resource reporting, data provenance, and ethics details when they affect the claim.
Structure & house style
Lead with the robot task and system constraint before the algorithmic component.
Use video or supplementary material only as allowed by the current anonymous-review policy.
Use the current official template exactly; do not guess page limits, font sizes, supplement rules, anonymity exceptions, or camera-ready requirements from old cycles.
The introduction should answer: problem, why now, what is new, why this venue, and what evidence proves the claim.
Put the strongest result in the main paper, not only in the appendix or supplement; reviewers should not have to reconstruct the contribution.
Re-check the current cycle's CFP, author kit, submission system, abstract/paper deadlines, page limits, supplementary-material rules, anonymity policy, dual-submission policy, ethics policy, AI-use policy, artifact/code/data expectations, rebuttal/author-response format, and camera-ready requirements.
Confirm the review workflow and portal: OpenReview / CMT / HotCRP / PCS / START or society portal, as specified for the current cycle.
Check whether accepted papers require in-person presentation, separate registration, artifact badges, proceedings copyright, or post-acceptance release forms.
If the live official instructions conflict with this skill, the official instructions win.
Pre-submission self-check
One sentence states why this manuscript belongs at RSS, using the venue's scope rather than generic "top conference" language.
The claim is calibrated to the evidence: no broader than the datasets, proofs, systems, user studies, deployments, or threat model support.
Related work includes the nearest current-cycle robotics flagship papers and explains the technical delta.
The paper satisfies the current official template, anonymity, ethics, artifact, and rebuttal requirements.
The main paper is self-contained enough for reviewers to evaluate novelty and correctness without hunting through external links.
Common desk-reject triggers
Simulation-only evidence for a claim about real robots.
No clear task distribution, few trials, or missing failure analysis.
A learning curve without robot-specific insight or system integration.
Formatting, anonymity, dual-submission, external-link, or supplement violations under the current-year policy.
A contribution framed for a neighboring field while giving RSS reviewers too little technical or empirical substance.
Re-routing decision
If the paper misses RSS's bar, compare against ieee-international-conference-on-robotics-and-automation / ieee-rsj-international-conference-on-intelligent-robots-and-systems / conference-on-robot-learning / acm-ieee-international-conference-on-human-robot-interaction. Re-route based on contribution type, not prestige: theory to a theory venue, systems to a systems venue, application-heavy work to a domain venue, and early ideas to workshops or shorter tracks when the official CFP supports them.
Output format
[Fit] High / Medium / Low (one-line reason)
[Target] Robotics: Science and Systems (RSS)
[Contribution type] algorithm / theory / system / dataset / benchmark / empirical / design / security / other
[Main evidence gap] <single most important missing proof, experiment, study, artifact, or policy check>
[Official items to re-check] CFP / author kit / deadline / format / anonymity / ethics / AI-use / artifact / rebuttal / camera-ready
[Top rejection risk] <venue-specific risk>
[Re-route suggestion] <better-matched conference or journal if not a fit>
1---2name: robotics-science-and-systems3description: Use when targeting Robotics: Science and Systems (RSS) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for robotics flagship.4---567# Robotics: Science and Systems (RSS)
89## Conference positioning
1011Robotics: Science and Systems (RSS) is a top computer-science conference venue for robotics science, algorithms, perception, manipulation, control, learning, and theory for robots. It rewards a robotics paper with concentrated scientific novelty and rigorous embodied evidence. Treat this skill as a **fit / venue-selection / re-framing** tool for conference submission strategy, not as a substitute for the current year's CFP, author kit, ethics policy, or submission portal.
1213Because CS conferences change deadlines, templates, page limits, review workflow, artifact rules, AI-use policy, and rebuttal formats every cycle, always verify the live official instructions before making a submission-ready recommendation. Start from the official source anchor recorded for this venue in `../../resources/conference-roster.md` and `../../resources/official-source-map.md`.
1415## When to trigger
1617- The author names RSS / Robotics: Science and Systems as the target venue.
18- A manuscript in robotics science needs a conference-fit read before being formatted or submitted.
19- The paper must be re-framed from journal style or arXiv style into a selective CS conference narrative.
20- The author needs an evidence-gap, anonymity, artifact, rebuttal, or re-routing diagnosis for this venue.
2122## Scope & topic fit
2324- Core fit: robotics science, algorithms, perception, manipulation, control, learning, and theory for robots.
25- Best submissions make a precise contribution type visible: algorithm, theorem, system, dataset, benchmark, empirical finding, design artifact, tool, or socio-technical analysis.
26- The paper should explain why the result matters to RSS's reviewers, not just why it is interesting to the authors' lab or product context.
27- Position related work against the most recent conference-cycle papers in this venue and its closest siblings; stale comparisons are a common early-review weakness.
28- If the contribution is interdisciplinary, state which part is CS research and which part is domain evidence.
2930## Venue-specific calibration
3132- Reviewer lens: Read reviewers as embodied-systems researchers. Hardware, simulation, task distributions, and failure rates matter more than a clean curve alone.
33- Contribution hook to foreground: the venue-specific contribution bar.
34- Scope vocabulary to use naturally in the abstract and introduction: robotics science, algorithms, perception, manipulation, control, learning, and theory for robots.
35- Distinctive fingerprint for reviewer calibration: robotics, algorithms, perception, manipulation, control, learning, theory, robots, venue-specific, contribution, flagship, roboticsconference.
36- Official anchor domain: roboticsconference.org. Quote annual rules only after opening that source and the current-year CFP/author kit.
3738## Close-neighbor routing guardrail
3940- Use this profile only when the manuscript's central contribution is genuinely in robotics
41 flagship and the author can say why RSS reviewers are the primary audience, not merely a
42 convenient deadline.
43- Closest roster neighbors to compare before final routing: `ieee-international-conference-on-
44 robotics-and-automation` (ICRA), `ieee-rsj-international-conference-on-intelligent-robots-
45 and-systems` (IROS), `acm-ieee-international-conference-on-human-robot-interaction` (HRI),
46 `ieee-international-conference-on-robot-and-human-interactive-communication` (RO-MAN). Break
47 ties by contribution type, evidence shape, reviewer community, and the current official CFP
48 from roboticsconference.org.
4950## What distinguishes this venue from its closest siblings
5152- **Format.** **Single-track and highly selective**, foundations/algorithmic-model forward — the deliberate contrast to the larger multi-track IEEE robotics venues **ICRA** (IEEE RAS) and **IROS** (IEEE/RSJ).
53- **Center of gravity.** Conceptual and algorithmic robotics contributions where the model or analysis is the result; hardware is evidence, not the headline.
54- **Routing.** Integrated-system or application breadth usually fits ICRA/IROS better; reserve RSS for results whose generality a single-track audience will reward.
5556## Method & evidence bar
5758- Report hardware, simulation, environment, task distribution, reset procedure, and failure cases; embodied evidence must be inspectable.
59- Compare against meaningful robot-learning, planning, or control baselines under matched assumptions.
60- Separate simulation gains from real-world transfer and quantify reliability, not only best-case success.
61- For RSS, the evidence must support the venue-specific signature: a robotics paper with concentrated scientific novelty and rigorous embodied evidence.
62- Include limitations, negative results, compute/resource reporting, data provenance, and ethics details when they affect the claim.
6364## Structure & house style
6566- Lead with the robot task and system constraint before the algorithmic component.
67- Use video or supplementary material only as allowed by the current anonymous-review policy.
68- Use the current official template exactly; do not guess page limits, font sizes, supplement rules, anonymity exceptions, or camera-ready requirements from old cycles.
69- The introduction should answer: problem, why now, what is new, why this venue, and what evidence proves the claim.
70- Put the strongest result in the main paper, not only in the appendix or supplement; reviewers should not have to reconstruct the contribution.
7172## Official-cycle checklist
7374- Open the live official venue page: https://roboticsconference.org/
75- Re-check the current cycle's CFP, author kit, submission system, abstract/paper deadlines, page limits, supplementary-material rules, anonymity policy, dual-submission policy, ethics policy, AI-use policy, artifact/code/data expectations, rebuttal/author-response format, and camera-ready requirements.
76- Confirm the review workflow and portal: OpenReview / CMT / HotCRP / PCS / START or society portal, as specified for the current cycle.
77- Check whether accepted papers require in-person presentation, separate registration, artifact badges, proceedings copyright, or post-acceptance release forms.
78- If the live official instructions conflict with this skill, the official instructions win.
7980## Pre-submission self-check
8182- [ ] One sentence states why this manuscript belongs at RSS, using the venue's scope rather than generic "top conference" language.
83- [ ] The claim is calibrated to the evidence: no broader than the datasets, proofs, systems, user studies, deployments, or threat model support.
84- [ ] Related work includes the nearest current-cycle robotics flagship papers and explains the technical delta.
85- [ ] The paper satisfies the current official template, anonymity, ethics, artifact, and rebuttal requirements.
86- [ ] The main paper is self-contained enough for reviewers to evaluate novelty and correctness without hunting through external links.
8788## Common desk-reject triggers
8990- Simulation-only evidence for a claim about real robots.
91- No clear task distribution, few trials, or missing failure analysis.
92- A learning curve without robot-specific insight or system integration.
93- Formatting, anonymity, dual-submission, external-link, or supplement violations under the current-year policy.
94- A contribution framed for a neighboring field while giving RSS reviewers too little technical or empirical substance.
9596## Re-routing decision
9798If the paper misses RSS's bar, compare against `ieee-international-conference-on-robotics-and-automation` / `ieee-rsj-international-conference-on-intelligent-robots-and-systems` / `conference-on-robot-learning` / `acm-ieee-international-conference-on-human-robot-interaction`. Re-route based on contribution type, not prestige: theory to a theory venue, systems to a systems venue, application-heavy work to a domain venue, and early ideas to workshops or shorter tracks when the official CFP supports them.
99100## Output format
101102```text
103[Fit] High / Medium / Low (one-line reason)
104[Target] Robotics: Science and Systems (RSS)
105[Contribution type] algorithm / theory / system / dataset / benchmark / empirical / design / security / other
106[Main evidence gap] <single most important missing proof, experiment, study, artifact, or policy check>
107[Official items to re-check] CFP / author kit / deadline / format / anonymity / ethics / AI-use / artifact / rebuttal / camera-ready
108[Top rejection risk] <venue-specific risk>
109[Re-route suggestion] <better-matched conference or journal if not a fit>
110```
111112---
113114**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Computer-Science-Conference-Skills/skills/robotics-science-and-systems/SKILL.md`
Run npx skillmds add thedixitjain/robotics-science-and-systems in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Use when targeting Robotics: Science and Systems (RSS) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for robotics flagship. It is listed under Research & Search on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.