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 auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets…
Install Recsys Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-submission --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-submission .claude/skills/recsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-submission into .claude/skills/recsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-submission --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-submission .agents/skills/recsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-submission into .agents/skills/recsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-submission --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-submission .cursor/skills/recsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-submission into .cursor/skills/recsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-submission --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-submission .gemini/skills/recsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-submission into .gemini/skills/recsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/recsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-submission into .github/skills/recsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-submission", 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-submission -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-submission --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-submission .opencode/skills/recsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-submission into .opencode/skills/recsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 628 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets…
- Works in 5 steps: Freeze the split: regenerate every… → Re-run baseline tuning last under an… → Compress into the content-page budget by… → …
- Auditing an ACM RecSys submission before the deadline — routing between the Main
- SKILL.md covers Pick the track before the format, Anonymization for recommender…, Blocking risks and Desk-reject and triage table, plus 3 more sections
- Calls pdftotext
What it does
Recsys Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets with appendices counted inside, double-blind anonymization for recommender papers, the anonymous-repository expectation, and desk-reject triage.
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.
It sits in Research & Science, covering Reproducible research. 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
- Auditing an ACM RecSys submission before the deadline — routing between the Main
- Reproducibility
- Industry and Resource tracks
- The ACM two-column content-page budgets with appendices counted inside
Example prompts
- “/recsys-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Freeze the split: regenerate every ranking table from the versioned dataset and a temporal
- Re-run baseline tuning last under an equal budget; a stale, under-tuned baseline is the
- Compress into the content-page budget by demoting per-dataset analyses to the appendix or
- Anonymity sweep: PDF metadata, acknowledgements, log provenance, deployed-system name,
- Confirm the submission-form abstract matches the PDF abstract and the track is correct.
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 628 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). 628 words, ~1,457 tokens.
Download SKILL.mdSave it as
.claude/skills/recsys-submission/SKILL.md (or your agent's skills folder).- name
- recsys-submission
- description
- Use when auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets with appendices counted inside, double-blind anonymization for recommender papers, the anonymous-repository expectation, and desk-reject triage.
RecSys Submission
Run this audit before anything is uploaded to the RecSys submission system. RecSys is a single-community but multi-track venue: the same manuscript can be legal in one track and desk-rejectable in another, so the audit begins with "which track is this PDF for?" and only then checks format. Reopen the current edition's Call for Contributions — every number below is a 2026-cycle anchor (verified 2026-07-09), not a permanent rule.
Pick the track before the format
For 2026 RecSys reorganized its lineup: it dropped the Late-Breaking Results (LBR) poster track and added Research & Practice (R&P) Notes. Route the contribution first.
| Track | 2026 budget | What belongs here |
|---|---|---|
| Main - long paper | 8 content pages | A rounded recommendation contribution with offline (and ideally online) evidence |
| Main - short paper | 4 content pages | One focused, complete finding |
| Main - Past, Present & Future | 4 content pages | Reflective/forward-looking position on a recommendation topic |
| Reproducibility | see current CFP | Repeating, refuting, or re-scoping prior results; datasets/frameworks for future reproduction |
| Industry | see current CFP | Deployed systems, production constraints, live A/B evidence |
| Resource / Dataset | see current CFP | A community dataset or software resource with build methodology |
| R&P Notes (posters) | see current CFP | Short findings/experiences; replaces LBR for 2026 |
References are excluded from the page count; appendices count inside it. Use the ACM two-column template unmodified — no margin, font, or spacing surgery.
Anonymization for recommender papers specifically
Generic double-blind advice misses the leaks recommender papers actually carry:
- Proprietary logs and platform. "Interaction logs from our video platform in region X" can name the company. Keep the statistics, genericize the source.
- Deployed system names. If the ranker already runs in production under a public name, the name de-anonymizes; rename for review or argue from the current policy on preprints.
- The anonymous repository. RecSys expects a code/data link inside the paper rather than a supplement upload — mirror it to an anonymized host and strip the owner, commit authors, and cluster paths from history.
- Self-citations in third person; acknowledgements and funding removed; PDF metadata stripped.
Blocking risks
- Wrong track for the contribution (a deployed-system paper squeezed into a Main long paper, or a reproduction study submitted as a novel-method paper).
- Over budget once appendices are counted inside the limit.
- Identity leak via logs, platform, deployed system name, or repository owner.
- Untuned baselines or a random split on sequential data — not a format desk reject, but the
fastest route to a low score (see
recsys-experiments). - Parallel submission of the same work to another venue.
Show full SKILL.md (221 more words)Show less
Desk-reject and triage table
| Trigger | Severity at RecSys | Repair window |
|---|---|---|
| Over budget (appendix counted in) | Desk reject | None after the deadline |
| Template tampering | Desk reject or chair flag | None |
| Identity leak in PDF, logs, or repository | Desk reject | None |
| Wrong track's submission form | Desk reject or forced move | Usually none |
| Parallel/dual submission | Desk reject at any time | None |
| Baselines untuned; random split on session data | Review-stage damage | Only before the deadline |
Final-week sequence for an offline-evaluation paper
- Freeze the split: regenerate every ranking table from the versioned dataset and a temporal split so the PDF and the anonymous repository agree.
- Re-run baseline tuning last under an equal budget; a stale, under-tuned baseline is the classic reviewer catch when the numbers move.
- Compress into the content-page budget by demoting per-dataset analyses to the appendix or repository, never by shrinking floats.
- Anonymity sweep: PDF metadata, acknowledgements, log provenance, deployed-system name, repository owner.
- Confirm the submission-form abstract matches the PDF abstract and the track is correct.
# Pre-upload checks that catch the silent killers
pdfinfo paper.pdf | grep -iE "author|creator" # metadata identity leak
grep -inE "acknowledg|our (platform|service|company)" *.tex # textual / platform leaks
pdftotext paper.pdf - | grep -icE "tuned|grid search|equal budget" # baseline tuning stated?
pdftotext paper.pdf - | grep -icE "temporal split|leave-one-last" # leakage-aware split?Format anchors
- RecSys uses the ACM two-column proceedings template; dense ranking tables and multi-panel offline/online figures overflow columns fast, so compress early rather than on deadline night.
- The page counts above describe the 2026 cycle; treat every number as provisional and recheck the current Call for Contributions before relying on it.
Output format
[RecSys readiness] Ready / Needs fixes / Wrong track / Not ready
[Track] main-long / main-short / past-present-future / reproducibility / industry / resource / R&P-note
[Budget check] <pages used>/<budget>, appendix-inside-budget confirmed yes-no
[Anonymity risks] <logs / platform / deployed name / repository owner / metadata>
[Evidence risk] <baseline tuning / split leakage / offline-only claim>
[Fix order] <ordered blocking fixes>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Recsys Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Bactopia Toolbactopia/bactopia | 522 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
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 Submission
What does Recsys Submission do?
A skill your agent uses when auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets…. Recsys Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets with appendices counted inside, double-blind anonymization for recommender papers, the anonymous-repository expectation, and desk-reject triage.
When should I use Recsys Submission?
Recsys Submission fits situations like: auditing an ACM RecSys submission before the deadline — routing between the Main; reproducibility; industry and Resource tracks; the ACM two-column content-page budgets with appendices counted inside.
How do I install Recsys Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-submission -a claude-code`. Or copy the skill folder (RecSys-Skills/skills/recsys-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/recsys-submission in your project. Claude Code loads it when a task matches its description.
How do I install Recsys Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-submission -a codex`. Or copy the skill folder (RecSys-Skills/skills/recsys-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/recsys-submission in your project. Codex loads it when a task matches its description.
Can I use Recsys Submission 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-submission -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-submission, .gemini/skills/recsys-submission, .github/skills/recsys-submission and .opencode/skills/recsys-submission in your project.
What does Recsys Submission need to run?
Going by SKILL.md and its folder, Recsys Submission needs the command-line tools its instructions call (pdftotext).
Does Recsys Submission 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 Submission 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 Submission use?
Recsys Submission 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 Submission use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 Submission?
Skills that share tags, products or a category with Recsys Submission: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Recsys Submission?
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.