Shared Claude Code Skills β
Canonical, version-controlled copies of the team's shareable Claude Code skills.
.claude/ is gitignored, so skills installed there are per-machine and never shipped with the repo. This folder is the source of truth: each skill lives here complete (its SKILL.md plus any scripts it calls), so anyone can install it into their own .claude/.
NOTE
The raw skill files are excluded from the rendered docs site (srcExclude: ['skills/*/**'] in .vitepress/config.mts) β they are sources to copy, not pages to read (this README still renders). The human-facing guides live elsewhere (e.g. Worktree Skill, Alert Triage).
Available skills β
| Skill | Folder | Guide |
|---|---|---|
worktree | worktree/ | Worktree Skill |
review-issue | review-issue/ | Alert Triage |
Install a skill β
A skill installs into .claude/skills/<name>/ β either project-local (<repo>/.claude/skills/, this repo only) or global (~/.claude/skills/, every repo).
Works for any skill in the table above β replace <name> with worktree, review-issue, etc.
Option A β ask Claude β
In Claude Code, name the skill you want, e.g. "add the worktree skill" or "add the review-issue skill". Claude copies apps/docs/skills/<name>/ into .claude/skills/<name>/; restart Claude Code and confirm /<name> appears in the skill list.
Option B β copy it yourself β
From the repo root:
# project-local (this repo only)
cp -R apps/docs/skills/<name> .claude/skills/<name>
# or global (all repos)
cp -R apps/docs/skills/<name> ~/.claude/skills/<name>Restart Claude Code afterwards so it picks up the new skill.
TIP
Some skills need MCP servers connected (e.g. review-issue needs grafana/slack/linear/sentry). The skill's guide page lists its prerequisites.
Add a new shared skill β
- Create
apps/docs/skills/<name>/and put the complete skill in it (SKILL.md+ scripts). - Add a row to the table above (and a guide page if it warrants one).
- Keep this copy in sync whenever you change the working copy in
.claude/skills/<name>/.