Organization
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing structured data on a business or brand website homepage.
A skill your agent uses when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that…
MITAuto-check passed
Install Recsys Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-supplementary --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-supplementary .claude/skills/recsys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-supplementary into .claude/skills/recsys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-supplementary", 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-supplementaryType 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-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-supplementary --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-supplementary .agents/skills/recsys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-supplementary into .agents/skills/recsys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-supplementary", 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-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-supplementary --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-supplementary .cursor/skills/recsys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-supplementary into .cursor/skills/recsys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-supplementary", 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-supplementary--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-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills recsys-supplementary --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-supplementary .gemini/skills/recsys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-supplementary into .gemini/skills/recsys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-supplementary", 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-supplementaryInstalls 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-supplementary -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-supplementary .github/skills/recsys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-supplementary into .github/skills/recsys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-supplementary", 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-supplementary -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-supplementary --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-supplementary .opencode/skills/recsys-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RecSys-Skills/skills/recsys-supplementary into .opencode/skills/recsys-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "recsys-supplementary", 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-supplementary- GitHub stars
- 1.2k
- Token cost
- ~985 tokens
- SKILL.md length
- 413 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that…
- The appendix that counts inside the page budget
- SKILL.md covers The three-bucket decision, What to keep in the body no…, What gets read, and how… and Vignette: splitting an…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The anonymous in-paper repository
What it does
Recsys Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that counts inside the page budget, and the anonymous in-paper repository, so tuning grids, extra datasets, and ablations land where reviewers use them.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- The appendix that counts inside the page budget
- The anonymous in-paper repository
- So tuning grids
- Ablations land where reviewers use them
Example prompts
- “/recsys-supplementary”
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 Supplementary loads about 985 tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 413 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). 413 words, ~985 tokens.
Download SKILL.mdSave it as
.claude/skills/recsys-supplementary/SKILL.md (or your agent's skills folder).- name
- recsys-supplementary
- description
- Use when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that counts inside the page budget, and the anonymous in-paper repository, so tuning grids, extra datasets, and ablations land where reviewers use them.
RecSys Supplementary
Use this when deciding where each piece of supporting material goes. RecSys is unusual: it does not invite a separate anonymous supplement file the way OpenReview venues do. Instead the appendix counts inside the content-page budget, and executable or bulky material lives in the anonymous repository linked from the paper. That constraint drives every placement decision.
The three-bucket decision
| Bucket | What belongs here | Constraint |
|---|---|---|
| Main body (8 / 4 pages) | The recommendation claim, method, headline offline table, the offline-online bridge, key ablation | Must stand alone; a reviewer should grasp the contribution without the appendix |
| Appendix (inside the budget) | Proof of any bound, dataset details, tuning grids, extra ablations, per-dataset breakdowns | Every page here is a page not spent on the body — include only what changes belief |
| Anonymous repository | Code, configs, checkpoints, logged propensities, raw run outputs, seeds | Reviewers may not open it; nothing decision-critical can live only here |
The sharpest RecSys-specific edge: because the appendix eats your page budget, authors are tempted to push essential evidence (like the equal-budget tuning grid) into the repository — but that is exactly the evidence a skeptical reviewer wants to see stated, so summarize it in the appendix and keep the full grid in the repository.
What to keep in the body no matter what
- The method and its assumption (e.g., positivity for an off-policy estimator).
- The headline ranking table with tuned baselines and reported variance.
- The one ablation that isolates the mechanism.
- One sentence stating the split protocol and whether metrics are full-ranking.
Show full SKILL.md (163 more words)Show less
What gets read, and how carefully
| Item | Inspection likelihood | Practical implication |
|---|---|---|
| Headline offline table | High | Belongs in the body, not the appendix |
| Tuning grid summary | Medium-high | Summarize in the appendix; reviewers check for equal budget |
| Extra datasets / ablations | Medium | Reference each from the body or it is invisible |
| Code repository | Variable (reviewer discretion) | README must orient a reader in one minute |
| Raw run logs | Low | Repository only; never rely on them for a claim |
Vignette: splitting an off-policy ranking paper
A submission proposing an exposure-corrected ranker: the body keeps the estimator, its positivity assumption, the tuned headline table, and the simulator bridge figure; the appendix holds the propensity-model details, the equal-budget tuning grid summary, and per-dataset breakdowns; the repository carries the seeded runner, checkpoints, and logged propensities. Nothing decision- critical lives only in the repository, because repository inspection is discretionary.
Cross-reference discipline
Body Table 1 --cites--> App. B (tuning grid) --mirrors--> repo/configs/*.yaml
Body Fig. 1 --cites--> App. C (simulator setup) --mirrors--> repo/sim/run.shOrphaned appendix material — a table no body sentence points to — wastes budget and is effectively invisible under reviewer discretion.
Output format
[Placement status] Ready / Needs fixes / Not ready
[Body-only items] <method / assumption / headline table / key ablation / split statement>
[Appendix items] <proofs / tuning-grid summary / extra datasets — inside the budget>
[Repository items] <code / configs / checkpoints / propensities / logs>
[Main-paper dependency] <what breaks if the appendix or repo is ignored>© 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-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Recsys Supplementary 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 Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~985 | Automated safety check: Pass | MIT | |
| Organizationthedaviddias/Front-End-Checklist | 74k | — | ~609 | Automated safety check: Pass | MIT | |
| File Organizerdavila7/claude-code-templates | 33k | 7 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Persona Customer Supportgoogleworkspace/cli | 31k | — | ~303 | Automated safety check: Pass | Apache-2.0 | |
| Customer Support Agentmastra-ai/mastra | 29k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Organize Spaceasgeirtj/system_prompts_leaks | 69k | — | ~1.6k | Automated safety check: Pass | CC0-1.0 |
Similar skills
File Organizer
davila7/claude-code-templates
Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures.
Persona Customer Support
googleworkspace/cli
Manage customer support — track tickets, respond, escalate issues.
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
Organize Space
asgeirtj/system_prompts_leaks
Organize existing ChatGPT Pages and Space structure when the user requests changes to that structure.
Organize Files
jxxghp/MoviePilot
A skill your agent uses when the user asks MoviePilot to identify and organize a local or downloaded video/music file, season folder, recording, album directory, or mixed folder that automatic…
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…
Questions about Recsys Supplementary
What does Recsys Supplementary do?
A skill your agent uses when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that…. Recsys Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that counts inside the page budget, and the anonymous in-paper repository, so tuning grids, extra datasets, and ablations land where reviewers use them.
When should I use Recsys Supplementary?
Recsys Supplementary fits situations like: the appendix that counts inside the page budget; the anonymous in-paper repository; so tuning grids; ablations land where reviewers use them.
How do I install Recsys Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-supplementary -a claude-code`. Or copy the skill folder (RecSys-Skills/skills/recsys-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/recsys-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Recsys Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-supplementary -a codex`. Or copy the skill folder (RecSys-Skills/skills/recsys-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/recsys-supplementary in your project. Codex loads it when a task matches its description.
Can I use Recsys Supplementary 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-supplementary -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-supplementary, .gemini/skills/recsys-supplementary, .github/skills/recsys-supplementary and .opencode/skills/recsys-supplementary in your project.
What does Recsys Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Recsys Supplementary is instructions for the agent only.
Does Recsys Supplementary 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 Supplementary 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 Supplementary use?
Recsys Supplementary 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 Supplementary use?
About 985 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 Recsys Supplementary?
Skills that share tags, products or a category with Recsys Supplementary: Organization (thedaviddias/Front-End-Checklist, 74k stars), File Organizer (davila7/claude-code-templates, 33k stars), Persona Customer Support (googleworkspace/cli, 31k stars) and Customer Support Agent (mastra-ai/mastra, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Recsys Supplementary?
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.