rss-artifact-evaluation
Use when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as anonymous review-time evidence and then as the public release the venue's free open-access proceedings culture expects, without any badge program to structure it.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-artifact-evaluation --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 Artifact Evaluation Package the artifacts as if a skeptical peer lab will pick them up — because at RSS, that is the actual evaluation mechanism. No badge track or artifact committee was verified for the 2026 cycle (待核实 each edition); the discipline is therefore self-imposed, and the reward is post-publication: RSS papers are free to every reader at roboticsproceedings.org, so strong artifacts get found and reused quickly. ## The robotics artifact stack Inventory what the paper's claims actually rest on, layer by layer: | Layer | Artifact | Review-time state | Release state | |---|---|---|---| | Claim analysis | Scripts turning logs into tables | in supplement | public repo | | Evidence corpus | Trial ledger + footage | anonymized | full, licensed | | Learned components | Policy/model weights + training configs | weights or recipe | both | | Software stack | Planner/controller code, sim environments | source in archive | tagged release | | Hardware layer | Platform ledger, CAD for custom parts, BOM | described in PDF | files where possible | | Protocol | Reset/intervention/success-criterion doc | in supplement | versioned doc | The stack ordering is a triage order: the top la
- The robotics artifact stack
- Review-time state (anonymous)
- Release-time state (public)
- Mechanical anonymity sweep for robotics archives
- Sizing the inspection to reality
- Handling the un-releasable
- License and citation plumbing at release
- Output format
lab and platform tells in code, configs, and robot descriptions
grep -riE "(lab|univ|institute|group)[-_a-z]*" --include="*.yaml" --include="*.xacro" .
grep -rl "<your-lab-acronym>" . # ROS package prefixes
find . -name "*.urdf" -o -name "*.xacro" | xargs grep -l "author\|copyright"
history and metadata
rm -rf .git; find . -name "*.ipynb" -exec jq '.metadata' {} \;
exiftool supplement_video.mp4 | grep -iE "creator|artist|gps|serial"What does the rss-artifact-evaluation skill do?
Use when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as anonymous review-time evidence and then as the public release the venue's free open-access proceedings culture expects, without any badge program to structure it.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-artifact-evaluation --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.