A collection of reusable Claude Code skills. These are skills I use in my own workflow that I think are generic enough to be useful beyond my specific setup.
Skills are SKILL.md files that teach Claude Code how to handle specific tasks. Drop one into your ~/.claude/skills/<name>/ directory and Claude will pick it up automatically.
| Skill | Description |
|---|---|
| archive-plan | Retire a finished plan: verify what actually shipped against real artifacts (never the plan's own status line), then file it under plans/archive/ |
| claude-windows | Compute the optimal Claude usage-window ping schedule from your work hours and register cloud routines that pin the window boundaries |
| code-review | Review a PR, diff file, or local changes: an orchestrator triages the change and dispatches to one of four specialized skills (lite, deep, infra, content) |
| devils-advocate | One-shot devil's-advocate critique of a plan or design: steel-manned strengths, severity-tagged findings with alternatives, verdict |
| double-check | Re-check your own last reply for unverified claims, excess length, and overengineering, then re-issue a corrected version |
| exit-session | Before closing a session, save only what the next one would need, flag anything exiting would lose, then confirm it is safe to /exit |
| grill-me | Stress-test a plan or design through a structured interview, one decision at a time. Inspired by Matt Pocock |
| investigate | Investigate a question to a grounded conclusion where every claim is verified against a primary source or flagged as a hypothesis |
| layman | Explain a ticket, file, or concept the way you'd explain it to a smart teenager, in a few plain sentences. Read the backstory |
| obsidian-charts | Reference for chart code inside Obsidian dataviewjs blocks: YAML chart blocks, direct Chart.js rendering, palette, and pitfalls |
| tldr | Reduce a reply or text block to its core conclusion in the fewest words |
| writing-artifacts | Mechanical hygiene pass over a drafted Markdown artifact before it's finalised: cuts process narration, dangling references, padding, and AI writing tics, never the substance |
| writing-instructions | Place a behavioral rule in the right instruction file, deduped against the rules already there and written tight |
| writing-skills | Guide the creation or update of a SKILL.md file with the right structure and fields. Read the backstory |
Each skill has its own README with installation instructions. The general pattern:
cp -r skills/<skill-name> ~/.claude/skills/The code-review family installs as five folders (the orchestrator plus its four child skills); see its README for details.
MIT