authoring-skills

To write concise SKILL.md files, keep frontmatter minimal and focus the body on non-obvious decisions and project-specific gotchas. Move verbose guidance into separate reference files loaded on demand to minimize token usage.

Progressive disclosure in markdown documentation moves verbose guidance, data, and reference material into separate files loaded on demand. This keeps the main SKILL.md body concise while preserving detailed domain knowledge for when it is needed.

SKILL.md frontmatter must include a name and description, while the body content should remain concise and focused on non-obvious decisions. Use references, scripts, and assets only when needed to support progressive disclosure.

Structure skill documentation using a recommended file layout of SKILL.md plus optional state, reference, and assets. This layout ensures consistent discovery, review, and iteration when organizing skill documentation across a repository.

Yes, this skill writing standard includes a publishing checklist and evaluation guidance to support iterative refinement and quality control. It helps ensure frontmatter is minimal, the body is concise, and references are used appropriately.

You should move reference material out of a SKILL.md file when it contains verbose guidance or data that bloats the body. Apply progressive disclosure patterns to load these separate reference files on demand only when needed.