generate-thesaurus

Generate controlled vocabulary thesaurus for content domains. Creates comprehensive thesauri with preferred terms, broader/narrower/related terms.

Quality

51%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/generate-thesaurus/SKILL.md

Quality

Discovery

67%

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 description effectively communicates a specialized capability with good specificity and clear domain focus. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill, and could benefit from more natural user-facing keywords beyond technical terminology.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user needs to organize terminology, create a taxonomy, or build term hierarchies for content management'

Include more natural keyword variations users might say: 'taxonomy', 'term hierarchy', 'vocabulary management', 'synonym lists', 'content classification'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generate controlled vocabulary thesaurus', 'Creates comprehensive thesauri with preferred terms, broader/narrower/related terms'. These are specific, domain-appropriate actions.	3 / 3
Completeness	Clearly answers 'what' (generate thesauri with hierarchical term relationships) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes relevant technical terms like 'controlled vocabulary', 'thesaurus', 'preferred terms', 'broader/narrower/related terms', but misses common user variations like 'taxonomy', 'term hierarchy', 'vocabulary management', or simpler phrases users might say.	2 / 3
Distinctiveness Conflict Risk	Highly specialized domain (controlled vocabulary/thesaurus creation) with distinct terminology unlikely to conflict with other skills. The specific mention of 'broader/narrower/related terms' clearly identifies this as information science/taxonomy work.	3 / 3
	Total	10 / 12 Passed

Implementation

35%

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

This skill provides a conceptual framework for thesaurus generation but lacks the concrete, executable guidance needed for Claude to actually perform the task. The workflow describes what should happen without specifying how to implement it - no code for content analysis, term extraction algorithms, or file parsing. The example output is helpful but insufficient without implementation details.

Suggestions

Add executable code for content analysis and term extraction (e.g., Python scripts using NLP libraries or regex patterns for scanning files)

Provide concrete commands or tool calls for reading files from the specified PATH

Include a validation step to verify extracted terms and relationships before final output generation

Add specific examples of input content and the expected extracted terms to make the extraction process concrete

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what broader/narrower terms are with examples that Claude would already understand). The workflow steps could be more condensed.	2 / 3
Actionability	The skill describes what to do conceptually but provides no executable code or concrete commands. 'Analyze content' and 'scan documentation files' are vague instructions without implementation details or tools to use.	1 / 3
Workflow Clarity	Steps are listed in sequence but lack validation checkpoints. There's no guidance on how to verify extracted terms are correct, no error handling, and no feedback loop for refining the thesaurus.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline. For a skill of this complexity, references to example templates or detailed format specifications could be split into separate files.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: dandye/ai-runbooks
Commit: 4d132c7

Reviewed: 16 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.