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 planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and…
Install Recsys Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-workflow --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-workflow .claude/skills/recsys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-workflow into .claude/skills/recsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-workflow --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-workflow .agents/skills/recsys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-workflow into .agents/skills/recsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-workflow --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-workflow .cursor/skills/recsys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-workflow into .cursor/skills/recsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-workflow --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-workflow .gemini/skills/recsys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-workflow into .gemini/skills/recsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/recsys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-workflow into .github/skills/recsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/recsys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-workflow into .opencode/skills/recsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 468 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and…
- Planning an ACM RecSys project timeline from venue fit through abstract
- SKILL.md covers Per-track dates are not the same, Milestones, Backward plan from the paper… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The anonymous repository
What it does
Recsys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and presentation, with backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main, Reproducibility, Industry, Resource, R&P Notes).
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. 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 an ACM RecSys project timeline from venue fit through abstract
- The anonymous repository
- ACM camera-ready
- With backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main
Example prompts
- “/recsys-workflow”
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 Workflow loads about 1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 468 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). 468 words, ~1,036 tokens.
Download SKILL.mdSave it as
.claude/skills/recsys-workflow/SKILL.md (or your agent's skills folder).- name
- recsys-workflow
- description
- Use when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and presentation, with backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main, Reproducibility, Industry, Resource, R&P Notes).
RecSys Workflow
Use this as the project-management skill for a RecSys submission. Replace all dates with the current official timetable and work backwards from the submission-system cutoffs.
RecSys is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Chairs (2026 General Chairs: Joseph A. Konstan, George Karypis, Gediminas Adomavicius; Program Chairs: Minmin Chen, Bart Goethals, Martijn Willemsen — verified 2026-07-09), and the cost model is registration fees, with proceedings in the ACM Digital Library. Chairs rotate yearly, so re-check the current committees page rather than carrying a name forward.
Per-track dates are not the same
The 2026 cycle ran several tracks on different timetables — do not assume the Main Track dates apply to your track.
| Track (2026, AoE) | Abstract | Paper | Notification | Camera-ready |
|---|---|---|---|---|
| Main (long/short/PPF) | Apr 14 | Apr 21 | Jul 9 | 待核实 |
| Reproducibility | Apr 28 | May 5 | Jul 9 | Jul 27 |
| Industry | (site Mar 2) | May 21 | Jul 9 | Jul 27 |
| Resource / Dataset | Apr 28 | May 5 | Jul 9 | 待核实 |
| R&P Notes / Demos | — | Jul 15 | — | — |
The Main-Track rebuttal window was June 4-9, 2026. Anchor every one of these to the current CFP; they are historical anchors, not permanent rules.
Milestones
- Venue fit: confirm the contribution is genuinely a recommendation result (see
recsys-topic-selection). - Evidence lock: freeze datasets, the split protocol, tuned baselines, seeds, ablations, and the anonymous repository contents.
- Abstract deadline: submit real title, abstract, authors, and topic areas.
- Paper deadline: upload the anonymous PDF, the in-paper anonymous repository link, and required fields.
- Rebuttal: draft a concise anonymous narrative on the central evaluation objection.
- Decision: archive reviews, rebuttal, and the submitted version.
- Acceptance: prepare the ACM camera-ready, rights form, registration, presentation, and the public artifact release.
Show full SKILL.md (180 more words)Show less
Backward plan from the paper deadline
| Weeks out (heuristic) | Offline-evaluation recommender milestone |
|---|---|
| 8+ | Datasets, versions, and split protocol frozen |
| 6 | Baselines tuned under an equal budget; grids logged |
| 4 | Ablations and the off-policy/simulator bridge complete, seeds logged |
| 3 | Full draft in the ACM two-column template |
| 2 | Internal mock review by a reproducibility-minded reader |
| 1 | Anonymity sweep; anonymous repository builds on a clean machine |
| 0 | Abstract then full paper on the submission system |
These offsets are planning heuristics only — anchor them to the current official timetable.
Failure modes by stage
- Baselines still on default configs at week 3 forces an unfair-comparison reject in the making.
- Leaving template conversion to the final week surfaces two-column overflow late.
- Skipping the mock review forfeits the only chance to hear "this split leaks the future" from a friend instead of a reviewer.
- Building the anonymous repository under deadline pressure is how commit-author leaks ship.
Coordination notes
- Assign one owner for the tuning-and-seeds protocol and another for the anonymity sweep.
- Archive the exact submitted PDF and repository state, since the rebuttal must quote them.
Output format
[Current stage] idea / experiments / writing / abstract / submission / rebuttal / accepted
[Track + next deadline] <track> - <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <baseline tuning / split / anonymity / repository / presentation>
[Owner map] <task -> person or role>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Recsys Workflow 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 Workflow 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 | |
| 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 Workflow
What does Recsys Workflow do?
A skill your agent uses when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and…. Recsys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and presentation, with backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main, Reproducibility, Industry, Resource, R&P Notes).
When should I use Recsys Workflow?
Recsys Workflow fits situations like: planning an ACM RecSys project timeline from venue fit through abstract; the anonymous repository; ACM camera-ready; with backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main.
How do I install Recsys Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-workflow -a claude-code`. Or copy the skill folder (RecSys-Skills/skills/recsys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/recsys-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Recsys Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-workflow -a codex`. Or copy the skill folder (RecSys-Skills/skills/recsys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/recsys-workflow in your project. Codex loads it when a task matches its description.
Can I use Recsys Workflow 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-workflow -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-workflow, .gemini/skills/recsys-workflow, .github/skills/recsys-workflow and .opencode/skills/recsys-workflow in your project.
What does Recsys Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Recsys Workflow is instructions for the agent only.
Does Recsys Workflow 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 Workflow 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 Workflow use?
Recsys Workflow 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 Workflow use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Recsys Workflow?
Skills that share tags, products or a category with Recsys Workflow: 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 Workflow?
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.