Skills

A skill is a reusable set of instructions for a particular kind of task, such as preparing a release, writing a database migration, or reviewing an API change. Unlike rules, skills aren't included in every request. The agent sees each skill's name and description, and reads the full instructions only when a task calls for them. That lets you keep detailed workflows available without filling the context window.

Where skills live

Each skill is a folder with a SKILL.md file inside:

The folder can also hold supporting files, such as templates or scripts, that the skill's instructions point to. You can create and edit skills in the Rules + Skills + Commands settings.

SKILL.md format

---
name: release-notes
description: Draft release notes from recent changes. Use when preparing a release or a changelog entry.
---

# Release notes

1. List the changes since the last release with `git log --oneline <last-tag>..HEAD`.
2. Group them into Added, Changed, and Fixed.
3. Write one plain sentence per change, from the user's point of view.

Give the skill a name and a description in the frontmatter, using simple key: value lines. The agent uses the description to decide when the skill applies, so say what the skill does and when to use it. Add enabled: false to stop the agent from using a skill automatically.

Using skills

• Automatically. The agent reads an enabled skill when your request matches its description.
• On request. Type / in the message box and choose a skill to attach its instructions to your message. You can attach up to eight skills to one message.

Skills from other tools

CodeNeter also finds skills you've written for other tools:

These skills are available from the / menu right away. For the agent to use one automatically, enable it under Discovered External Skills in the Rules + Skills + Commands settings. Discovery can be turned off in the same place. A project's own .claude/skills folder isn't searched.