Install
A skill is a folder. The only required file is SKILL.md: frontmatter with a name and a description, then the instructions. Assets such as scripts, references and style registries sit beside it and are loaded only when the skill needs them.
Where the folder goes
- Personal skills —
~/.claude/skills/<name>/SKILL.md, available in every project. - Project skills —
<repo>/.claude/skills/<name>/SKILL.md, committed with the code. - Other runtimes — anything that reads a skills directory works; the folder name must match the
namefield.
Standalone skill
git clone https://github.com/KaelZhang321/kael-cover.git
cp -R kael-cover ~/.claude/skills/kael-cover
TeamBition toolkit
git clone https://github.com/KaelZhang321/teambition-agent-toolkit.git
cp -R teambition-agent-toolkit/skills/* ~/.claude/skills/
# then, inside your workspace, ask the agent to run tb-init
Prerequisites by skill
- kael-cover — Python 3 and an image generator the agent can call;
sipsfor per-platform exports (macOS). - product-prototype-design — Pencil MCP, for
.penoutput. - standard-prd — nothing beyond a model that can write long documents.
- site-geo-optimizer — Python 3, PyYAML, and the Astro repo it targets.
- substack-publisher — Python 3,
markdown, a validsubstack.sidcookie. - teambition-agent-toolkit — Node 18+, TeamBition App ID / secret / operator / organization.
What makes a skill load
The description field is a condition, not a pitch. It should say when to use the skill and, where useful, when not to. A skill whose description reads “helps with writing” fires on everything and helps with nothing.
The rule I hold myself to
If a skill cannot state the failure mode it prevents, it is a prompt, not a skill. Every entry on this site names at least one thing it refuses to do.
Quick check
ls ~/.claude/skills/
head -5 ~/.claude/skills/*/SKILL.md