Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
A skill your agent uses when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the…
Install Recsys Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-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/RecSys-Skills/skills/recsys-review-process .claude/skills/recsys-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 "recsys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-review-process into .claude/skills/recsys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-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/RecSys-Skills/skills/recsys-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 recsys-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-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/RecSys-Skills/skills/recsys-review-process .agents/skills/recsys-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 "recsys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-review-process into .agents/skills/recsys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-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 recsys-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-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/RecSys-Skills/skills/recsys-review-process .cursor/skills/recsys-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 "recsys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-review-process into .cursor/skills/recsys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-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 RecSys-Skills/skills/recsys-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 recsys-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-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/RecSys-Skills/skills/recsys-review-process .gemini/skills/recsys-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 "recsys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-review-process into .gemini/skills/recsys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-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 recsys-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 recsys-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/RecSys-Skills/skills/recsys-review-process .github/skills/recsys-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 "recsys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-review-process into .github/skills/recsys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-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 recsys-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 recsys-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/RecSys-Skills/skills/recsys-review-process .opencode/skills/recsys-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 "recsys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-review-process into .opencode/skills/recsys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-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
recsys-review-process- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 437 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 planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the…
- Planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer
- SKILL.md covers Process model, Who reviews here, and what…, 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 rebuttal phase
What it does
Recsys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the reproducibility-crisis culture shapes reviewer priorities, the offline-versus-online evaluation lens, and how acceptance leads to ACM Digital Library publication.
Its SKILL.md is about 1k 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 Reproducible research and 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
- Planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer
- The rebuttal phase
- How the reproducibility-crisis culture shapes reviewer priorities
- The offline-versus-online evaluation lens
Example prompts
- “/recsys-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
Recsys Review Process loads about 1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 437 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). 437 words, ~1,000 tokens.
Download SKILL.mdSave it as
.claude/skills/recsys-review-process/SKILL.md (or your agent's skills folder).- name
- recsys-review-process
- description
- Use when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the reproducibility-crisis culture shapes reviewer priorities, the offline-versus-online evaluation lens, and how acceptance leads to ACM Digital Library publication.
RecSys Review Process
Use this to reason about review-stage strategy. Reopen the current Call for Contributions, the committees page, and any reviewer guidelines before making process claims — mechanics are cycle-specific.
Process model
- RecSys review is mutually anonymous (double-blind). Each submission is read by at least three PC members and overseen by a Senior PC member who synthesizes the recommendation.
- There is an author rebuttal phase (2026: June 4-9) for a short clarifying narrative.
- Reviewers weigh recommendation novelty, evaluation validity, reproducibility, clarity, and relevance to the recommender community — not raw metric wins alone.
- The most useful reply is a decision-focused clarification that gives the Senior PC a clean rationale for acceptance or rejection.
- Accepted papers are published in the ACM Digital Library, so camera-ready compliance and metadata matter as much as the initial decision.
Who reviews here, and what they distrust
- The pool is a single-domain recommender community: expect at least one reviewer who has internalized the field's reproducibility debate and will probe baseline tuning line by line.
- Because RecSys is topically tight, matches are close and an under-tuned comparison or a leaky split gets caught rather than skimmed past.
- Borderline offline-evaluation papers usually fall on one of three edges: baselines tuned less hard than the proposed method, a random split where a temporal one was needed, or an offline metric asserted to imply a deployment win with no bridge.
Show full SKILL.md (208 more words)Show less
Scoring leverage table
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Recommendation novelty | A named user/item modeling or evaluation idea | An architecture swap with no recommendation-specific insight |
| Evaluation validity | Equal-budget baselines, temporal split, full-ranking metrics, variance | Untuned baselines, random split, sampled metrics reported as full |
| Deployment relevance | Off-policy estimate, simulator, or A/B result | "Offline nDCG rose, therefore users benefit" |
| Reproducibility | A runnable anonymous repository regenerating the tables | A promise to release code "upon acceptance" only |
| Clarity | One notation source, honest limitations | Buried assumptions; a random-split protocol left implicit |
Stage-by-stage realism
- Initial reviews: triage by what the Senior PC would weigh, not by reviewer tone.
- Rebuttal: the window is short; an early, precise narrative on the central evaluation objection
beats a late line-by-line reply (see
recsys-author-response). - Decision: the Senior PC synthesizes; one unresolved evaluation-validity objection outweighs several resolved clarity complaints.
- Post-decision: ACM Digital Library publication means the rights form and metadata become the final gate.
Vignette: reading a split decision
Two reviewers like the method; one flags that baselines were tuned only on defaults. At RecSys that single objection is decisive because it maps onto the community's reproducibility anxiety — so the rebuttal must resolve that thread, with the equal-budget grid, before polishing anything the other reviewers raised.
Output format
[Current stage] submitted / reviews / rebuttal / decision / camera-ready
[Decision actors] <PC reviewers / Senior PC>
[Likely leverage] <novelty / evaluation validity / deployment relevance / reproducibility / clarity>
[Forbidden moves] <identity leak / unseen new results / unsupported deployment claims>
[Next response 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 RecSys-Skills/skills/recsys-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Recsys 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 |
|---|---|---|---|---|---|---|
| Recsys Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| Ma Peer Reviewhtlin222/meta-pipe | 139 | — | ~1k | Automated safety check: Pass | Custom licence | |
| Icml Reviewersundial-org/skills | 153 | — | ~2.4k | Automated safety check: Pass | None | |
| Review Paperpedrohcgs/claude-code-my-workflow | 1.7k | — | ~7.3k | Automated safety check: Pass | MIT | |
| Scientific Workflow ToolsDrugClaw/DrugClaw | 126 | — | ~712 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ma Peer Review
htlin222/meta-pipe
Act as Reviewer 1 and Reviewer 2 for a meta-analysis manuscript, checking rigor, reproducibility, and reporting compliance.
Icml Reviewer
sundial-org/skills
Paper reviewer that evaluates machine learning research projects following official ICML reviewer guidelines.
Review Paper
pedrohcgs/claude-code-my-workflow
Comprehensive manuscript review with three modes: single-pass (default), --adversarial critic-fixer loop, and --peer [journal] simulated peer-review pipeline (editor + 2 dispositioned referees +…
Scientific Workflow Tools
DrugClaw/DrugClaw
Research-method workflow guide for hypothesis framing, peer-review style critique, reproducibility planning, study-design checks, and scientific-writing structure.
Paper Review
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses when a paper is complete or near-complete and a holistic pre-submission audit is needed.
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 Recsys Review Process
What does Recsys Review Process do?
A skill your agent uses when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the…. Recsys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the reproducibility-crisis culture shapes reviewer priorities, the offline-versus-online evaluation lens, and how acceptance leads to ACM Digital Library publication.
When should I use Recsys Review Process?
Recsys Review Process fits situations like: planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer; the rebuttal phase; how the reproducibility-crisis culture shapes reviewer priorities; the offline-versus-online evaluation lens.
How do I install Recsys Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-review-process -a claude-code`. Or copy the skill folder (RecSys-Skills/skills/recsys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/recsys-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Recsys Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-review-process -a codex`. Or copy the skill folder (RecSys-Skills/skills/recsys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/recsys-review-process in your project. Codex loads it when a task matches its description.
Can I use Recsys 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 recsys-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/recsys-review-process, .gemini/skills/recsys-review-process, .github/skills/recsys-review-process and .opencode/skills/recsys-review-process in your project.
What does Recsys Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Recsys Review Process is instructions for the agent only.
Does Recsys 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 Recsys 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 Recsys Review Process use?
Recsys 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 Recsys Review Process use?
About 1k tokens (SKILL.md is roughly 4k 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 Recsys Review Process?
Skills that share tags, products or a category with Recsys Review Process: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), Ma Peer Review (htlin222/meta-pipe, 139 stars), Icml Reviewer (sundial-org/skills, 153 stars) and Review Paper (pedrohcgs/claude-code-my-workflow, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Recsys 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.