timctfl · timctfl · Apr 7, 2026 · Apr 7, 2026
diff --git a/skills/adapt-skill/SKILL.md b/skills/adapt-skill/SKILL.md
@@ -10,7 +10,7 @@ license: Apache-2.0
 
 You already have a prompt or skill that works. This skill converts it into the format SkillShelf uses, so other people can find it, download it, and use it with their own AI tools. Paste your prompt, upload a file, or upload a zip, and you get back a complete skill directory ready to share.
 
-Before starting, read `references/conventions-checklist.md` and `references/example-adaptation.md`. The other reference files are specialized. Read `references/calibration-pattern.md` only if the source skill needs a calibration step, and `references/glossary-writing-guide.md` only if the converted skill produces output consumed by other skills. Do not read them upfront.
+Before starting, read `references/conventions-checklist.md` and `references/example-adaptation.md`. Read `references/calibration-pattern.md` only if the source skill needs a calibration step. Do not read it upfront.
 
 ---
 
@@ -104,7 +104,6 @@ Produce:
 
 1. **references/example-output.md.** A complete example of what the skill produces when run with good input. This sets the quality ceiling.
 2. **skillshelf.yaml.** The SkillShelf metadata file. Read `references/skillshelf-yaml-reference.md` for valid field values.
-3. **references/glossary.md.** Only if the skill produces structured output that other skills consume as input. Most skills do not need this. If yours does, read `references/glossary-writing-guide.md` for the full specification.
 
 After sharing the example output, ask the user to review it. Explain that this example is what the AI will aim for when the skill runs, so the quality, tone, and level of detail should match what they'd actually want to use.
 

diff --git a/skills/adapt-skill/references/conventions-checklist.md b/skills/adapt-skill/references/conventions-checklist.md
@@ -66,9 +66,6 @@ Use this checklist during Phase 4 to review a skill against SkillShelf standards
 
 - [ ] References to other skills use natural-language names, not directory names
 - [ ] Primitives are recommended but not required (skill works without them)
-- [ ] If output is consumed by other skills: `references/glossary.md` exists
-- [ ] If output is consumed by other skills: output includes version marker (`<!-- skill-name v0.1 -->`)
-- [ ] If glossary exists: follows the six-section structure (Overview, Document Structure, Section Hierarchy, Handling Missing Input, Field Definitions, Changelog)
 
 ## Edge Cases
 

diff --git a/skills/adapt-skill/references/glossary-writing-guide.md b/skills/adapt-skill/references/glossary-writing-guide.md
diff --git a/skills/adapt-skill/skillshelf.yaml b/skills/adapt-skill/skillshelf.yaml
@@ -39,8 +39,7 @@ output_schema:
   description: >-
     A complete SkillShelf skill directory containing SKILL.md with valid
     frontmatter, references/example-output.md demonstrating ceiling quality,
-    an optional references/glossary.md for skills whose output is consumed
-    downstream, and a skillshelf.yaml metadata sidecar.
+    and a skillshelf.yaml metadata sidecar.
   required_files:
     - SKILL.md
     - skillshelf.yaml

diff --git a/skills/write-skill/SKILL.md b/skills/write-skill/SKILL.md
@@ -10,7 +10,7 @@ license: Apache-2.0
 
 This skill helps users go from "I have an idea for a skill" to a complete, convention-compliant skill directory. It walks through understanding the task, planning the skill, writing and reviewing the SKILL.md, then producing the supporting files.
 
-Before starting, read `references/conventions-checklist.md` and `references/example-output.md`. The other reference files are specialized. Read `references/calibration-pattern.md` only if the Phase 2 plan includes a calibration step, and `references/glossary-writing-guide.md` only if the plan calls for downstream consumption. Do not read them upfront.
+Before starting, read `references/conventions-checklist.md` and `references/example-output.md`. Read `references/calibration-pattern.md` only if the Phase 2 plan includes a calibration step. Do not read it upfront.
 
 ---
 
@@ -89,7 +89,6 @@ Produce:
 
 1. **references/example-output.md.** A complete example of what the skill produces when run with good input. This sets the quality ceiling.
 2. **skillshelf.yaml.** The SkillShelf metadata file. Read `references/skillshelf-yaml-reference.md` for valid field values.
-3. **references/glossary.md.** Only if the skill produces structured output that other skills consume as input. Most skills do not need this. If yours does, read `references/glossary-writing-guide.md` for the full specification.
 
 After sharing the example output, ask the user to review it. Explain that this example is what the AI will aim for when the skill runs, so the quality, tone, and level of detail should match what they'd actually want to use.
 

diff --git a/skills/write-skill/references/conventions-checklist.md b/skills/write-skill/references/conventions-checklist.md
@@ -66,9 +66,6 @@ Use this checklist during Phase 4 to review a skill against SkillShelf standards
 
 - [ ] References to other skills use natural-language names, not directory names
 - [ ] Primitives are recommended but not required (skill works without them)
-- [ ] If output is consumed by other skills: `references/glossary.md` exists
-- [ ] If output is consumed by other skills: output includes version marker (`<!-- skill-name v0.1 -->`)
-- [ ] If glossary exists: follows the six-section structure (Overview, Document Structure, Section Hierarchy, Handling Missing Input, Field Definitions, Changelog)
 
 ## Edge Cases