# Skills

> Teach the KazoCode agent repeatable know-how with skills, folders with a SKILL.md file that load only when a task needs them. Compatible with Claude Code skills.

A skill is a folder of instructions, and optionally scripts and reference files, that teaches the agent how to do one kind of task: release a version, write a migration, follow your design system. Only each skill's name and description sit in the agent's context; the full instructions load when a task calls for them, so you can install many skills without slowing anything down.

## Create a skill

Make a folder with a `SKILL.md` file:

```md title=".kazocode/skills/release/SKILL.md"
---
name: release
description: Cut a release. Use when asked to publish, release or tag a new version.
---

1. Make sure the working tree is clean and `pnpm test` passes.
2. Bump the version in package.json following semver.
3. Update CHANGELOG.md with the changes since the last tag.
4. Commit as "Release vX.Y.Z", tag it, and push the tag.
```

The `description` is what the agent uses to decide when a skill applies, so say both what it does and when to use it.

Files next to `SKILL.md`, such as templates or scripts, can be referenced from it; the agent reads them when it follows the skill.

## Where skills are found

| Folder | Scope |
| --- | --- |
| `.kazocode/skills/`, `.claude/skills/` or `.agents/skills/` in the project | This project; commit them for your team |
| `~/.kazocode/skills/`, `~/.claude/skills/` or `~/.agents/skills/` | Every project, just for you |
| Plugins | Every project where the plugin is on |
| An organization folder set by your administrator | Everyone on the computer |

Claude Code skills work as they are.

## Using skills

The agent picks a skill when your request matches its description. You can also run one directly as a slash command by its name, such as `/release`. `/skills` lists every installed skill.
