Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an accepted RSS (Robotics: Science and Systems) paper into its public form — de-anonymization and platform-attribution restoration, adding the external links…
MITAuto-check passed
Install Rss Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-camera-ready --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/RSS-Skills/skills/rss-camera-ready .claude/skills/rss-camera-ready && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-ready into .claude/skills/rss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-camera-ready", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-readyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-camera-ready --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/RSS-Skills/skills/rss-camera-ready .agents/skills/rss-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-ready into .agents/skills/rss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-camera-ready", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-camera-ready --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/RSS-Skills/skills/rss-camera-ready .cursor/skills/rss-camera-ready && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-ready into .cursor/skills/rss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-camera-ready", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path RSS-Skills/skills/rss-camera-ready--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-camera-ready --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/RSS-Skills/skills/rss-camera-ready .gemini/skills/rss-camera-ready && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-ready into .gemini/skills/rss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-camera-ready", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-camera-readyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/RSS-Skills/skills/rss-camera-ready .github/skills/rss-camera-ready && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-ready into .github/skills/rss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-camera-ready", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-camera-ready --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/RSS-Skills/skills/rss-camera-ready .opencode/skills/rss-camera-ready && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-camera-ready into .opencode/skills/rss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-camera-ready", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rss-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 667 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an accepted RSS (Robotics: Science and Systems) paper into its public form — de-anonymization and platform-attribution restoration, adding the external links…
- Works in 4 steps: Build the talk for the distant-subfield… → Show real footage early; a single uncut… → Rehearse the failure question — "when… → …
- Adding the external links the CFP reserves for this stage
- SKILL.md covers What changes at this stage,…, Edits that are — and are not —…, Publication mechanics and The single-track presentation, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rss Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted RSS (Robotics: Science and Systems) paper into its public form — de-anonymization and platform-attribution restoration, adding the external links the CFP reserves for this stage, publication in the free roboticsproceedings.org archive with a 10.15607 DOI, and single-track presentation preparation.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Adding the external links the CFP reserves for this stage
- Publication in the free roboticsproceedings.org archive with a 10.15607 DOI
- Single-track presentation preparation
Example prompts
- “/rss-camera-ready”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Build the talk for the distant-subfield attendee: one slide establishing why your
- Show real footage early; a single uncut clip buys more belief than an
- Rehearse the failure question — "when does it break?" is the most common
- Poster/spotlight mechanics vary per edition (待核实 in author instructions);
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rss Camera Ready loads about 1.5k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 667 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 667 words, ~1,517 tokens.
Download SKILL.mdSave it as
.claude/skills/rss-camera-ready/SKILL.md (or your agent's skills folder).- name
- rss-camera-ready
- description
- Use when converting an accepted RSS (Robotics: Science and Systems) paper into its public form — de-anonymization and platform-attribution restoration, adding the external links the CFP reserves for this stage, publication in the free roboticsproceedings.org archive with a 10.15607 DOI, and single-track presentation preparation.
RSS Camera Ready
Turn the anonymous accepted version into the archival one. The 2026 camera-ready deadline was never publicly surfaced (待核实 — take it from the acceptance email); everything else below is verified venue mechanics as of 2026-07-08.
What changes at this stage, specifically at RSS
| Submission state | Camera-ready state |
|---|---|
| Anonymous authors | Full author block, affiliations, funding |
| Generic hardware provenance | Restored platform attribution and lab lineage |
| No external links (CFP rule) | Project page, repo, video links welcome |
| Anonymized supplement archive | Public artifact release (rss-artifact-evaluation) |
| Reviewed claims | Same claims + accepted clarifications only |
The links row is the venue-specific one: RSS 2026 explicitly deferred all external linking to the camera-ready, so this is the moment the project page, code repository, and hosted video enter the paper. Test every link logged-out before submitting the final PDF.
Edits that are — and are not — in scope
- In scope: corrections promised in the rebuttal, scope-sentence adjustments the AC asked for, fixed typos, restored acknowledgements, added links.
- Out of scope: new experiments upgrading the claims, retitled contributions, or quietly strengthened numbers. The accepted paper is what the AC meeting endorsed; divergence beyond clarification is an integrity problem, not a formatting one.
- Keep section, table, and figure numbering stable where possible so the review record still maps onto the final text.
Publication mechanics
- RSS proceedings appear at roboticsproceedings.org — free to read, no author
fee, no paywall — with DOIs of the form
10.15607/RSS.<year>.<vol>.<paper>. Verify your final metadata (title capitalization, author order, affiliations) exactly as it should be archived; the volume page is what dblp and citation indices ingest. - There is no APC anywhere in this pipeline; the cost model is conference registration. Whether at least one author must register/present in person was not publicly verified for 2026 (待核实 against the acceptance email).
The single-track presentation
Acceptance at RSS means presenting to the entire conference, not a parallel-session slice — the preparation bar is accordingly higher:
- Build the talk for the distant-subfield attendee: one slide establishing why your problem matters outside your niche, before any method detail.
- Show real footage early; a single uncut clip buys more belief than an architecture diagram.
- Rehearse the failure question — "when does it break?" is the most common single-track question, and your failure table is the prepared answer.
- Poster/spotlight mechanics vary per edition (待核实 in author instructions); prepare the poster to carry the trial evidence the talk compresses away.
Show full SKILL.md (270 more words)Show less
Archive-metadata proof pass
The roboticsproceedings.org volume page is the record dblp, Google Scholar, and citation managers will ingest — proof it like a legal document:
- Author name forms consistent with each author's existing publication record (initials vs full names decide whether citation graphs merge or fork).
- Title capitalization and any math/Unicode rendered as intended.
- Affiliations current at publication time, not at submission time.
- Funding acknowledgements exactly as grant terms require.
- The
10.15607/RSS.*DOI, once minted, is what belongs in your CV and repo citation file — point the repository's citation entry at the proceedings page, not at the arXiv mirror.
Between acceptance and Sydney: an ordered runway
Eleven weeks separated the 2026 decision (April 27) from conference week (July 13-17). A workable ordering:
| Weeks after decision | Action |
|---|---|
| 0-1 | Extract acceptance-email requirements; calendar the camera-ready date |
| 1-3 | Final PDF edits (clarifications only) + de-anonymization sweep |
| 1-4 | Visa and travel booking — the long pole for many teams |
| 3-6 | Public artifact release built and tested (rss-artifact-evaluation) |
| 6-9 | Talk drafted and rehearsed against the whole-audience test |
| 9-11 | Poster printed; footage loaded locally; links re-tested logged-out |
Final-pass checklist
[ ] Acceptance-email requirements extracted (deadline, format, forms) — sole source
[ ] Author block, funding, acknowledgements restored
[ ] Platform attribution un-anonymized; self-citations re-personalized
[ ] Links added and tested logged-out: repo / project page / video
[ ] Claims diff vs accepted version = clarifications only
[ ] Metadata proofread as-it-will-be-archived
[ ] Public artifact release live before the conference talk drives traffic to itHedged logistics (all 待核实 per cycle)
- Camera-ready deadline, template version, and any form uploads: sole source is the acceptance email plus the author-instructions page it links.
- Registration classes, pricing, and whether a paper requires a specific class or in-person presenter: verify on the current registration page.
- Copyright/consent mechanics for the proceedings: RSS's open-access model differs from IEEE-style transfer flows — do not assume either shape; read the form sent.
- Talk length, spotlight-vs-poster split, and session assignment: published with the program, not the acceptance email; recheck close to conference week.
Output format
[Camera-ready status] blocked / in progress / submitted
[Sole-source items] <from acceptance email: deadline, forms>
[Diff audit] clarifications only / out-of-scope edits found
[Link check] <url -> ok/broken>
[Presentation prep] whole-audience slide / footage / failure answer© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in RSS-Skills/skills/rss-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Rss Camera Ready next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rss Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 62k | — | ~247 | Automated safety check: Pass | Custom licence | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Robots Meta Conflictthedaviddias/Front-End-Checklist | 74k | — | ~555 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Robots Meta Conflict
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to sites that use both robots.txt disallow rules and meta robots noindex tags.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Rss Camera Ready
What does Rss Camera Ready do?
A skill your agent uses when converting an accepted RSS (Robotics: Science and Systems) paper into its public form — de-anonymization and platform-attribution restoration, adding the external links…. Rss Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills.15607 DOI, and single-track presentation preparation.
When should I use Rss Camera Ready?
Rss Camera Ready fits situations like: adding the external links the CFP reserves for this stage; publication in the free roboticsproceedings.org archive with a 10.15607 DOI; single-track presentation preparation.
How do I install Rss Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a claude-code`. Or copy the skill folder (RSS-Skills/skills/rss-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/rss-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Rss Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a codex`. Or copy the skill folder (RSS-Skills/skills/rss-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/rss-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Rss Camera Ready in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rss-camera-ready, .gemini/skills/rss-camera-ready, .github/skills/rss-camera-ready and .opencode/skills/rss-camera-ready in your project.
What does Rss Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Rss Camera Ready is instructions for the agent only.
Does Rss Camera Ready access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rss Camera Ready safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rss Camera Ready use?
Rss Camera Ready is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rss Camera Ready use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Rss Camera Ready?
Skills that share tags, products or a category with Rss Camera Ready: Convert (remotion-dev/remotion, 62k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Robots Meta Conflict (thedaviddias/Front-End-Checklist, 74k stars) and Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rss Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.