salonskills

A personal collection of Claude Code skills — documented here so I can reuse them and share them with others.

Each skill is a self-contained folder under .claude/skills/. A skill is just a SKILL.md (instructions + a description of when to use it) plus any bundled reference files. Claude Code loads a skill automatically when your request matches what it does — you can also just ask for it by name.

Skills

🧠 brainrot-reviewer

An unhinged Gen-Z "brainrot" code review — emoji-spammed, big-bro-roasting-"lil bro" energy — that's secretly a rigorous PR review underneath. It figures out what actually changed (a PR, a branch diff, or a lab vs. its instructions), does a real review (correctness, tests, dead code, commit hygiene, spec adherence…), then delivers it in brainrot style. Prints the review to chat, then offers to save it to review.md or post it as a PR comment (if the code came from a PR) or a new issue (otherwise). Tone auto-calibrates: it glazes genuinely clean code and roasts sloppy code.

Try: "brainrot review this branch", "roast my code", "review this lab but make it funny"

🔎 research-scout-personalized

An adversarial novelty / prior-art scout that tries hard to kill your research idea with the literature before you sink months into it. On first use it onboards you with a quick researcher profile (field, unfair advantage, data/compute access, target venue, timeframe) and saves it; after that it reuses that profile automatically and returns a decisive GO / NO-GO verdict — with citations — anchored on the gap only you can fill. Your profile is stored locally and gitignored, so it never gets shared.

Try: "is this novel?", "scout this topic", "go/no-go on this idea", "update my research profile"

Download & install

Clone the repo:

git clone https://github.com/<your-username>/salonskills.git

Then pick how you want the skills available:

A) Use them right here — open Claude Code in the cloned repo. Both skills live in .claude/skills/ and load automatically while you work in this folder.

B) Install a skill globally (available in every project) — copy its folder into your personal skills directory:

# macOS / Linux
mkdir -p ~/.claude/skills
cp -r .claude/skills/brainrot-reviewer ~/.claude/skills/

# Windows (PowerShell)
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null
Copy-Item -Recurse ".claude\skills\brainrot-reviewer" "$HOME\.claude\skills\"

C) Install into another project — copy the skill folder into that project's .claude/skills/ directory.

After copying a skill in, start a fresh Claude Code session so it gets picked up.

Using a skill

Just describe the task — skills trigger automatically when your request matches their description (e.g. "do a brainrot review of my current branch"). You don't need to memorize a command.

Repo layout

salonskills/
├── README.md
└── .claude/
    └── skills/
        ├── brainrot-reviewer/
        │   ├── SKILL.md
        │   └── references/style-guide.md
        └── research-scout-personalized/
            └── SKILL.md

Notes

• Built for Claude Code (CLI, desktop app, or IDE extension) with Skills support.
• Some skills bundle extra reference files (e.g. brainrot-reviewer/references/style-guide.md) that are loaded on demand, only when needed.
• A few skills keep local state that should not be shared — e.g. research-scout-personalized saves your researcher profile to .claude/research-scout-personalized/profile.json, which is gitignored.