Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied…
Install Iros Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-review-process .claude/skills/iros-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 "iros-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-review-process into .claude/skills/iros-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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/IROS-Skills/skills/iros-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 iros-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-review-process .agents/skills/iros-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 "iros-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-review-process into .agents/skills/iros-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-review-process .cursor/skills/iros-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 "iros-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-review-process into .cursor/skills/iros-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 IROS-Skills/skills/iros-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 iros-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-review-process .gemini/skills/iros-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 "iros-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-review-process into .gemini/skills/iros-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-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 iros-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/IROS-Skills/skills/iros-review-process .github/skills/iros-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 "iros-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-review-process into .github/skills/iros-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-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 iros-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/IROS-Skills/skills/iros-review-process .opencode/skills/iros-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 "iros-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-review-process into .opencode/skills/iros-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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
iros-review-process- GitHub stars
- 1.2k
- Token cost
- ~976 tokens
- SKILL.md length
- 417 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied…
- Reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline
- SKILL.md covers Process model, The no-rebuttal consequence, Scoring leverage table and Stage-by-stage realism, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The traditional no-rebuttal single-notification model
What it does
Iros Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied evidence steer reviewers, the 2026 double-anonymous posture, decision criteria for systems papers, and IEEE Xplore proceedings outcomes.
Its SKILL.md is about 980 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
- Reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline
- The traditional no-rebuttal single-notification model
- How the video and embodied evidence steer reviewers
- The 2026 double-anonymous posture
Example prompts
- “/iros-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
Iros Review Process loads about 976 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 417 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). 417 words, ~976 tokens.
Download SKILL.mdSave it as
.claude/skills/iros-review-process/SKILL.md (or your agent's skills folder).- name
- iros-review-process
- description
- Use when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied evidence steer reviewers, the 2026 double-anonymous posture, decision criteria for systems papers, and IEEE Xplore proceedings outcomes.
IROS Review Process
Use this to reason about review-stage strategy. Reopen the current CFP, PaperPlaza instructions, and any reviewer guidelines before making process claims — IROS review mechanics are set per edition by the co-sponsoring IEEE/RSJ committee.
Process model
- Submission and review run on PaperPlaza. Papers are handled by an Associate Editor under an Editor, who assign and synthesize reviews; there is no standing editor-in-chief for the conference.
- Reviewers are embodied-systems researchers. They weigh hardware, task distributions, trial counts, failure analysis, and sim-to-real honesty at least as much as a clean plot.
- The video is read as evidence: many reviewers watch it before the text, so a weak or misleading video colors the whole review.
- The 2026 cycle is double-anonymous; author identity should not be inferable from text, figures, or video.
- Accepted papers go to IEEE Xplore, so camera-ready compliance and the copyright form matter as much as the initial decision.
The no-rebuttal consequence
IROS has traditionally delivered reviews together with the decision and no author-response phase. This changes strategy fundamentally: you cannot answer an objection after the fact, so every foreseeable objection must be pre-answered in the paper and the video. The video functions as the only asynchronous "rebuttal" a reviewer gets — a shown-and-labeled failure disarms the "did it really work?" reviewer before they can write it down. Confirm the current cycle's policy before assuming a rebuttal exists or does not.
Show full SKILL.md (186 more words)Show less
Scoring leverage table
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Technical merit | A system that integrates cleanly and runs under a real constraint | A component swap dressed up as a system |
| Evidence | Trials, resets, failures, and a stated sim-to-real gap | A hero demo with no counts and no failures |
| Clarity | A system diagram and figures that carry the argument | An argument that needs an appendix IROS does not provide |
| Reproducibility | Hardware ledger, logs, honest availability | "Code coming soon" with no specs |
Stage-by-stage realism
- Submission to notification is a long silence (spring to mid-June in 2026); there is no interaction to manage, only evidence to preserve for camera-ready.
- Notification arrives with the reviews; with no rebuttal, the lever is the camera-ready revision and the meta-review's requested changes.
- A single unresolved "I don't believe the robot did this" concern outweighs several resolved clarity nits, because embodied credibility is the currency here.
Reject-to-next-venue realism
Because IROS is on the fall calendar, a reject can route to the next ICRA, to CoRL, or to an RA-L submission with revision — decide by the reviews' substance, not by prestige.
Reading a review packet:
[ ] separate "the robot didn't convince me" from "writing unclear"
[ ] list objections that a camera-ready edit can address vs cannot
[ ] note every evidence gap the reviewers named for the next run
[ ] pick the re-route (ICRA / CoRL / RA-L) if rejected, by substanceOutput format
[Current stage] submitted / in-review / notified / camera-ready
[Decision actors] <Associate Editor / Editor / reviewers>
[Likely leverage] <integration / evidence / clarity / reproducibility>
[No-rebuttal implication] <what must be pre-answered in paper + video>
[Next move] <camera-ready edit or re-route>© 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 IROS-Skills/skills/iros-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iros 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 |
|---|---|---|---|---|---|---|
| Iros Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~976 | 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 Iros Review Process
What does Iros Review Process do?
A skill your agent uses when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied…. Iros Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied evidence steer reviewers, the 2026 double-anonymous posture, decision criteria for systems papers, and IEEE Xplore proceedings outcomes.
When should I use Iros Review Process?
Iros Review Process fits situations like: reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline; the traditional no-rebuttal single-notification model; how the video and embodied evidence steer reviewers; the 2026 double-anonymous posture.
How do I install Iros Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-review-process -a claude-code`. Or copy the skill folder (IROS-Skills/skills/iros-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iros-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Iros Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-review-process -a codex`. Or copy the skill folder (IROS-Skills/skills/iros-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iros-review-process in your project. Codex loads it when a task matches its description.
Can I use Iros 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 iros-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/iros-review-process, .gemini/skills/iros-review-process, .github/skills/iros-review-process and .opencode/skills/iros-review-process in your project.
What does Iros Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Iros Review Process is instructions for the agent only.
Does Iros 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 Iros 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 Iros Review Process use?
Iros 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 Iros Review Process use?
About 976 tokens (SKILL.md is roughly 3.9k 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 Iros Review Process?
Skills that share tags, products or a category with Iros 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 Iros Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.