An Agent Skills bundle uses SKILL.md to describe a reusable procedural workflow. The file starts with YAML frontmatter for discovery and use, followed by the workflow in its main body. section 6.1.2
Table 6.1 Fields that can be included in a skill’s frontmatter
|
Field
|
Required
|
Description
|
|
name
|
Yes
|
A unique
identifier for the skill. Must be lowercase letters, numbers, and hyphens
only. Cannot start or end with a hyphen. Maximum 64 characters.
|
|
description
|
Yes
|
Describes
what the skill’s procedural workflow does and in what scenarios it should be
applied. Maximum 1024 characters.
|
|
license
|
No
|
The name of
the license that covers the skill (e.g. MIT) or the name of the license file
that is bundled in the skills resources.
|
|
compatibility
|
No
|
Describes
any environment constraints or requirements the skill has. Maximum 500
characters.
|
|
metadata
|
No
|
An
arbitrary key-value map for additional properties not covered by the
standard, like author or version.
|
|
allowed-tools
|
No
|
A
space-delimited list of tools (each specified by name) the LLM agent can use
to execute the skill.
|
Check the frontmatter fields and their requirements when defining a skill's metadata. section 6.1.2
A skill file and its optional resources work together:
- Provide the required name and description in frontmatter; optional fields include license, compatibility, metadata, and allowed-tools. section 6.1.2
- Write the procedural workflow in the Markdown body. It can refer to scripts, supplementary references, or assets stored in adjacent directories; keep resource files no more than one level deep. section 6.1.2
A reader can validate the body by checking that the file opens, its frontmatter can be separated from the body, and the body is nonempty. Agents discover skills and may activate one to access its workflow and available resources. section 6.2.2 section 6.6


