spec-loop-write-glossary

Create or update a project glossary in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires project glossary work. This skill is mandatory for AsciiDoc project glossaries unless the user explicitly opts out for the current project or session.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/spec-loop-write-glossary/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-bounded but relies almost entirely on an external glossary-format.md file that is missing from the bundle, leaving it light on actionable detail. Structure is minimal yet appropriate for a short skill, aside from the broken reference.

Suggestions

Add the missing glossary-format.md to the bundle (or inline the essential format rules) so the 'read and apply it' instruction has a real target.

Include at least a minimal concrete example of a glossary entry or the AsciiDoc glossary structure inline so the skill is actionable without the external file.

Add light section headers (e.g., 'When to use', 'How to apply') to give the short body explicit structure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every line states a boundary or a directed action.	5 / 5
Actionability	Concrete guidance is minimal — the operative instruction is 'read [glossary-format.md] and apply it' and 'read and apply AGENTS.md', delegating all specific steps to external sources rather than providing executable direction.	2 / 5
Workflow Clarity	The sequence (read glossary-format.md, apply it, read AGENTS.md) is clear for a simple single-purpose skill, though the actual work is hidden behind 'apply it' with no checkpoints.	4 / 5
Progressive Disclosure	The body signals a one-level-deep reference to glossary-format.md, but that file is not present in the bundle, so the reference is broken and navigation to the actual format detail fails.	3 / 5
	Total	14 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states both what the skill does and when to use it, with a well-scoped niche that minimizes conflict risk. Trigger terms are explicit but somewhat domain-jargon-heavy and could use more natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain ('Spec Loop AsciiDoc glossary format') and two concrete actions ('Create or update'), but does not enumerate the fuller set of glossary operations, so coverage is not comprehensive.	3 / 5
Completeness	It explicitly answers 'what' ('Create or update a project glossary in the Spec Loop AsciiDoc glossary format') and 'when' ('Use when the user, project instructions, or spec-loop-plan-task already requires project glossary work') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Relevant keywords ('project glossary', 'AsciiDoc glossary', 'spec-loop-plan-task') appear with an explicit 'Use when...' trigger, but the terms are niche and lack common synonyms or file-extension variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	The narrow 'Spec Loop AsciiDoc glossary format' niche with explicit non-AsciiDoc exclusion gives it distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: dpolivaev/spec-loop
Path: skills/spec-loop-write-glossary/SKILL.md
Commit: 27df5cc

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.