From 3736fdb995af251d30eca9623f08874c41122e37 Mon Sep 17 00:00:00 2001 From: Jonathan Hefner Date: Fri, 6 Mar 2026 15:44:40 -0600 Subject: [PATCH] Format directory and file names as inline code in specification doc 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) --- docs/specification.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/specification.mdx b/docs/specification.mdx index 34d3a9a..997f4a5 100644 --- a/docs/specification.mdx +++ b/docs/specification.mdx @@ -18,7 +18,7 @@ skill-name/ You can optionally include [additional directories](#optional-directories) such as `scripts/`, `references/`, and `assets/` to support your skill. -## SKILL.md format +## `SKILL.md` format The `SKILL.md` file must contain YAML frontmatter followed by Markdown content. @@ -169,7 +169,7 @@ Note that the agent will load this entire file once it's decided to activate a s ## Optional directories -### scripts/ +### `scripts/` Contains executable code that agents can run. Scripts should: - Be self-contained or clearly document dependencies @@ -178,7 +178,7 @@ Contains executable code that agents can run. Scripts should: Supported languages depend on the agent implementation. Common options include Python, Bash, and JavaScript. -### references/ +### `references/` Contains additional documentation that agents can read when needed: - `REFERENCE.md` - Detailed technical reference @@ -187,7 +187,7 @@ Contains additional documentation that agents can read when needed: Keep individual [reference files](#file-references) focused. Agents load these on demand, so smaller files mean less use of context. -### assets/ +### `assets/` Contains static resources: - Templates (document templates, configuration templates)