rss-review-process
Use when explaining or strategizing around RSS (Robotics: Science and Systems) peer review — the double-blind OpenReview pipeline, the two-stage design where only above-threshold papers earn a one-page rebuttal, the Area Chair meeting that sets decisions, and what single-track selectivity does to reviewer expectations.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-review-process --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.
# RSS Review Process Model how an RSS decision actually gets made. The mechanics below are the verified 2026 design (roboticsconference.org/reviewps/, checked 2026-07-08); the two-stage structure itself is cycle policy, so confirm it survives before relying on it. ## The 2026 pipeline ```text OpenReview submission (double-blind) │ first review round │ threshold gate ── below ──▶ reject (no rebuttal opportunity) │ above invited one-page rebuttal (due 2026-04-03 AoE) │ Area Chair reads rebuttal │ (forwards to reviewers only if extra feedback is needed) Area Chair meeting ──▶ decisions (2026-04-27 AoE) ``` Two properties distinguish this from ML-conference discussion phases: - **The rebuttal is earned, not granted.** Papers below the first-round threshold are decided without author input. Consequence: the submission itself must pre-answer foreseeable objections; there may be no second chance (`rss-writing-style`). - **The audience of the rebuttal is the AC.** Reviewers may never see it. Write for the person running the meeting, not for a back-and-forth thread (`rss-author-response`). ## What single-track selectivity does to reviewing Every accepted paper takes a slot in front of the w
- The 2026 pipeline
- What single-track selectivity does to reviewing
- Reading a borderline packet
- Timeline anatomy (2026 verified dates)
- Calibrating expectations by venue contrast
- Confidentiality and conduct
- Who sits in the reviewer pool
- Output format
What does the rss-review-process skill do?
Use when explaining or strategizing around RSS (Robotics: Science and Systems) peer review — the double-blind OpenReview pipeline, the two-stage design where only above-threshold papers earn a one-page rebuttal, the Area Chair meeting that sets decisions, and what single-track selectivity does to reviewer expectations.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-review-process --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.