rss-related-work
Use when positioning an RSS (Robotics: Science and Systems) submission within the literature — covering the robotics-conference lanes (RSS/ICRA/IROS/CoRL) plus journals and ML venues, handling fast-moving arXiv concurrency in robot learning, keeping self-references double-blind, and turning related work into claim-sharpening contrasts.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-related-work --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 Related Work Position the paper so its claim's novelty is checkable. At a selective single-track venue, related work is not a courtesy section — it is where the Area Chair verifies that the field genuinely lacks what the paper asserts. ## The lanes an RSS reviewer expects covered | Lane | Where it lives | The question your coverage must answer | |---|---|---| | RSS's own line | roboticsproce
What does the rss-related-work skill do?
Use when positioning an RSS (Robotics: Science and Systems) submission within the literature — covering the robotics-conference lanes (RSS/ICRA/IROS/CoRL) plus journals and ML venues, handling fast-moving arXiv concurrency in robot learning, keeping self-references double-blind, and turning related work into claim-sharpening contrasts.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-related-work --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.