src/skills/ containing a SKILL.md and any supporting references. This page covers the format and the conventions that keep a skill useful.
Create the folder
Make a folder named for the skill (the folder name is how you’ll attach it to an agent) and add aSKILL.md:
Write SKILL.md
ASKILL.md follows the Agent Skills specification: YAML frontmatter with a name and a description, then a focused body.
src/skills/support/SKILL.md
| Frontmatter | What it does |
|---|---|
name | The skill’s name; match it to the folder name |
description | A short summary of when the agent should use this skill |
description matters: it’s what an agent uses to decide whether a skill is relevant, so describe the situation it applies to, not just what it contains.
Keep the body short, push detail to references
Skills work by progressive disclosure: the agent reads the shortSKILL.md first, then loads deeper material only when the task needs it. Keep SKILL.md to the essentials and put long policies, examples, and edge cases in a references/ folder:
/workspace/agent/skills/{slug}/, so the agent can open a reference by path when it decides it needs it.
References aren’t the only kind of supporting material. The whole folder is copied verbatim, so a skill can also ship helper scripts the agent runs with its shell tools, or assets like templates and fixtures it reads:
SKILL.md.
Point the agent at the skill
A skill is available to an agent once you attach it, but you’ll often nudge the agent toward it in thesystemPrompt so it knows the skill exists and when to reach for it:
Next steps
Attach skills to agents
Attach a skill to an agent by folder name.
Skills overview
What project skills are and when to use them.
Import skills
Reuse skills from external registries.
Files
Add static reference documents to a workspace.