Add a third example showing a Python version requirement alongside `uv`.
This complements the existing examples (product targeting and system
tool requirements) by demonstrating version-pinned runtime requirements
— the kind of non-obvious constraint that the `compatibility` field is
useful for.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The frontmatter `description` already serves as the page subtitle in
Mintlify, so the "This document defines the Agent Skills format." line
was just restating it.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The directory listing is not exhaustive — skill authors can include
other files and subdirectories beyond those shown. Adding a `...` entry
makes this explicit.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Place the field constraints table immediately after the `Frontmatter`
heading so readers see the reference before the examples. Also remove
"(required)" from the heading, wrap examples in a `<Card>`, and relabel
"With optional fields:" to "Example with optional fields:".
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The fenced code blocks showing `SKILL.md` content were labeled as `yaml`
or plain `markdown`. Changing them to `markdown SKILL.md` adds a
filename hint and more accurately reflects that they contain full
`SKILL.md` snippets (including `---` frontmatter delimiters), not just
raw YAML.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The `####` field headings didn't stand out enough amongst all the code
blocks, making the page hard to scan. Wrapping each field's examples in
a `<Card>` draws a border around them and adds padding, so each
subsection looks more contained instead of bleeding into the next. Also
bolds the example labels within each card.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Show optional directories (`scripts/`, `references/`, `assets/`)
directly in the directory tree with inline annotations, replacing the
separate `<Tip>` block.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Place inline code examples next to the terms they describe (e.g.,
"`a-z`" next to "alphanumeric characters") rather than grouping them at
the end. Also add the word "hyphen" before the code-formatted `-` for
readability.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Wrap `SKILL.md`, `scripts/`, `references/`, and `assets/` headings in
backticks for consistency with the rest of the document, which already
uses inline code formatting for these names in body text.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The example `description` values in what-are-skills.mdx and
specification.mdx only described what the skill does, but omitted
when to use it. This contradicted the spec's own guidance that
description should cover both. Added a "Use when..." clause while
keeping the line short enough to avoid clipping in the rendered
code block on the docs site.
Jonathan HefnerandClaude Opus 4.6
Koichi ITO
