From 7a05447ecbe93880fcf5cc9bacd94d34ae34b27b Mon Sep 17 00:00:00 2001 From: Jonathan Hefner Date: Fri, 6 Mar 2026 16:23:52 -0600 Subject: [PATCH] Add `SKILL.md` filename annotations to code blocks in specification doc 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) --- docs/specification.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/specification.mdx b/docs/specification.mdx index 6286443..32a9e57 100644 --- a/docs/specification.mdx +++ b/docs/specification.mdx @@ -23,7 +23,7 @@ The `SKILL.md` file must contain YAML frontmatter followed by Markdown content. ### Frontmatter (required) -```yaml +```markdown SKILL.md --- name: skill-name description: A description of what this skill does and when to use it. @@ -32,7 +32,7 @@ description: A description of what this skill does and when to use it. **With optional fields:** -```yaml +```markdown SKILL.md --- name: pdf-processing description: Extract PDF text, fill forms, merge files. Use when handling PDFs. @@ -219,7 +219,7 @@ Keep your main `SKILL.md` under 500 lines. Move detailed reference material to s When referencing other files in your skill, use relative paths from the skill root: -```markdown +```markdown SKILL.md See [the reference guide](references/REFERENCE.md) for details. Run the extraction script: