Skills

Markdown files in a folder. Advertised by name and description, loaded only when the model needs them.

Where they live

Nested directory or flat file, both work. On the same id the project wins.

.agents/skills/git-release/SKILL.md   → id git-release
.agents/skills/review.md              → id review
~/.agents/skills/                     → user scope

Frontmatter

---
name: Git Release
description: Prepare and publish releases
---
Step 1: ...

A skill with a description is advertised in the system prompt, by id, name and description only. The model loads the full body on demand through the skill tool, so skill content never bloats the prompt upfront.

Using one

Let the model pick: When your request matches an advertised description, it calls skill git-release itself.
Force one: Mention the id in your message.
Browse: /skills lists what is loaded.

Toggling skills on or off is not implemented: every loaded skill is active in every session.