Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses 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…
Install Rss Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-review-process --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-review-process .claude/skills/rss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-review-process into .claude/skills/rss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-review-process --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-review-process .agents/skills/rss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-review-process into .agents/skills/rss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-review-process --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-review-process .cursor/skills/rss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-review-process into .cursor/skills/rss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-review-process --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-review-process .gemini/skills/rss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-review-process into .gemini/skills/rss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/rss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-review-process into .github/skills/rss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/rss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-review-process into .opencode/skills/rss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 621 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Strategizing around RSS (Robotics: Science and Systems) peer review — the double-blind OpenReview pipeline
- SKILL.md covers The 2026 pipeline, What single-track selectivity…, Reading a borderline packet and Timeline anatomy (2026…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The two-stage design where only above-threshold papers earn a one-page rebuttal
What it does
Rss Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Peer review. 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
- 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
- What single-track selectivity does to reviewer expectations
Example prompts
- “/rss-review-process”
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 Review Process loads about 1.4k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 621 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). 621 words, ~1,410 tokens.
Download SKILL.mdSave it as
.claude/skills/rss-review-process/SKILL.md (or your agent's skills folder).- name
- rss-review-process
- description
- 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.
RSS Review Process
Model how an RSS decision actually gets made. The mechanics below are the verified 2026 design (roboticsconference.org/2026/reviewps/, checked 2026-07-08); the two-stage structure itself is cycle policy, so confirm it survives before relying on it.
The 2026 pipeline
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 whole conference, so the operative question in the AC meeting is closer to "must the field hear this?" than "is this sound?" Soundness is necessary, not sufficient. Practical consequences:
| Review dynamic | Cause | Author counter-move |
|---|---|---|
| High bar for "so what" | One program, finite slots | Lead with the claim's consequence for other subfields |
| Deep methodological reads | Specialized, smaller reviewer pool | State assumptions and protocol precisely; vagueness gets caught |
| Skepticism toward demo-style evidence | Science-first venue identity | Attribute failures, isolate mechanisms, report all trials |
| Low tolerance for padding | 8-page ceiling framed as ceiling | Cut aggressively; length is not a proxy for rigor here |
Reading a borderline packet
- Separate correctness objections (a flaw in the claim or protocol) from scope objections (the claim is narrower than sold) from significance doubts (sound but not slot-worthy). Only the first two are rebuttal-addressable with existing evidence; the third is won or lost in the submission's framing.
- A lone enthusiastic review does not carry a paper through an AC meeting; a lone unanswered correctness objection can sink one. Triage accordingly.
- Decisions emerge from a synchronous meeting, so the AC's summary understanding is the decision artifact. Everything you write should compress well into two sentences an AC might say aloud.
Timeline anatomy (2026 verified dates)
| Date (AoE) | Event | Author-side implication |
|---|---|---|
| Jan 30 | Papers in | Last word for below-threshold papers |
| Feb-Mar | First round (release date 待核实) | Do not plan around an assumed date |
| Apr 3 | Invited rebuttals due | Short notice — pre-draft objection answers |
| Apr 3-27 | AC digestion + meeting | No author-visible activity; silence is normal |
| Apr 27 | Decisions | ~11 weeks before the July conference |
The compressed April-to-July runway is a distinctive RSS pressure: camera-ready, travel authorization, and artifact release all share eleven weeks.
Show full SKILL.md (219 more words)Show less
Calibrating expectations by venue contrast
- Unlike venues with universal author-response phases, RSS's threshold gate means a silent April is itself information — but never certain information, since invitation lists are confidential.
- Unlike rolling-review journals, there is no revise-and-resubmit: the meeting
outputs accept or reject, and the improvement loop runs through the next venue
slot (
rss-workflow). - Scores, forms, and thresholds are internal; public acceptance statistics were not verified for 2026 (待核实) — do not quote community folklore rates as fact.
Confidentiality and conduct
- Reviewer identities, scores, and thresholds are confidential; do not attempt identification or out-of-band contact.
- Notification wording in 2026 covered "paper and demo acceptance" even though the CFP had no demo-paper category — treat demo mechanics as 待核实 rather than inferring a track.
Who sits in the reviewer pool
- The pool spans planning, control, perception, learning, and mechanism design; topic matching at a smaller venue is tight, so expect at least one reviewer who has personally run experiments like yours — protocol hand-waving gets caught.
- Because the audience is the whole field, at least one review often comes from an adjacent subfield; jargon-dense writing loses exactly the vote the single-track format makes decisive.
- Area Chairs are established researchers appointed per edition; the AC's synthesis carries the meeting, which is why every skill in this pack optimizes for the AC-compressible summary.
Output format
[Stage] under review / rebuttal invited / no rebuttal / AC meeting pending / decided
[Objection triage] correctness: <...> | scope: <...> | significance: <...>
[AC-compressible summary] <two sentences the AC could say in the meeting>
[Rebuttal leverage] high / low / none (below threshold)
[Next move] <one action>© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Rss Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
Similar skills
Scholar Evaluation
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
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…
Related
Categories
Questions about Rss Review Process
What does Rss Review Process do?
A skill your agent uses 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…. Rss Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Rss Review Process?
Rss Review Process fits situations like: 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; what single-track selectivity does to reviewer expectations.
How do I install Rss Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-review-process -a claude-code`. Or copy the skill folder (RSS-Skills/skills/rss-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/rss-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Rss Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-review-process -a codex`. Or copy the skill folder (RSS-Skills/skills/rss-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/rss-review-process in your project. Codex loads it when a task matches its description.
Can I use Rss Review Process 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-review-process -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-review-process, .gemini/skills/rss-review-process, .github/skills/rss-review-process and .opencode/skills/rss-review-process in your project.
What does Rss Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Rss Review Process is instructions for the agent only.
Does Rss Review Process 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 Review Process 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 Review Process use?
Rss Review Process 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 Review Process use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Review Process?
Skills that share tags, products or a category with Rss Review Process: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rss Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.