spec-loop-write-glossary
Create or update glossary entries in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires a glossary artifact. This skill is mandatory for AsciiDoc glossaries unless the user explicitly opts out for the current project or session.
52
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/spec-loop-write-glossary/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly defines its niche (AsciiDoc glossary entries in the Spec Loop format) and provides explicit trigger conditions. Its main weakness is that the 'what' portion could enumerate more specific actions beyond 'create or update.' The mandatory usage clause and reference to spec-loop-plan-task add helpful disambiguation.
Suggestions
Add more specific concrete actions to the 'what' clause, e.g., 'define terms, add descriptions, format definition lists, update existing entries' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AsciiDoc glossary) and two actions (create or update glossary entries), but doesn't list more specific concrete actions like defining terms, formatting entries, linking cross-references, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (create or update glossary entries in AsciiDoc format) and 'when' (when user/project instructions/spec-loop-plan-task requires a glossary artifact), with explicit trigger guidance and even a mandatory usage clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'glossary', 'glossary entries', 'AsciiDoc', 'spec-loop-plan-task', and 'glossary artifact'. These cover the terms a user or system would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: 'Spec Loop AsciiDoc glossary format' is very specific and unlikely to conflict with other skills. The mention of 'spec-loop-plan-task' and 'AsciiDoc glossaries' creates a narrow, well-defined scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a thin pointer to glossary-format.md with some scope/policy guardrails. It lacks any actionable content of its own—no examples, no concrete steps, no format snippets. While the brevity and reference structure show some awareness of progressive disclosure, the skill body fails to provide enough standalone value to be useful.
Suggestions
Add at least a minimal example of a glossary entry in the expected AsciiDoc format so the skill has standalone actionable content.
Define a brief workflow: e.g., 1. Check if glossary file exists, 2. Read glossary-format.md, 3. Add/update entries, 4. Validate format consistency.
Include a concrete snippet or template showing the expected output structure rather than fully delegating to an external file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but includes some redundant statements (e.g., restating the mandatory nature from the description, and the 'This skill defines the glossary format. It does not decide whether a glossary is required.' line is borderline unnecessary). Could be tighter. | 2 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It entirely delegates to glossary-format.md with 'read and apply it,' offering no executable or specific instructions itself. | 1 / 3 |
Workflow Clarity | There is no clear sequence of steps, no validation checkpoints, and no workflow structure. The content is essentially 'read another file and apply it' with some guardrails, but no process is defined. | 1 / 3 |
Progressive Disclosure | It references glossary-format.md as a one-level-deep reference, which is appropriate progressive disclosure structure. However, since no bundle files were provided, we can't verify the reference exists, and the SKILL.md itself provides almost no overview content to orient the reader before pointing elsewhere. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- dpolivaev/spec-loop
- Commit
90f996e
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.