generate-thesaurus
Generate controlled vocabulary thesaurus for content domains. Creates comprehensive thesauri with preferred terms, broader/narrower/related terms.
Install with Tessl CLI
npx tessl i github:dandye/ai-runbooks --skill generate-thesaurus56
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 additional natural language terms users might employ when requesting this type of work.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when building taxonomies, organizing terminology, creating term hierarchies, or standardizing vocabulary for content management'
Include additional natural trigger terms users might say: 'taxonomy', 'term hierarchy', 'synonyms', 'vocabulary management', 'metadata terms', 'subject headings'
| 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', 'synonyms', or 'vocabulary management'. | 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 implement it. The workflow describes what should happen without specifying how to accomplish each step. The example output is helpful but insufficient without corresponding implementation code or specific tool recommendations.
Suggestions
Add executable code or specific commands for content analysis and term extraction (e.g., regex patterns, NLP library usage, or file reading methods)
Include concrete examples of input content and the expected extracted terms to demonstrate the extraction process
Add validation steps to verify extracted terms and relationships are meaningful before generating final output
Specify how to handle edge cases like empty directories, binary files, or content with no identifiable domain terms
| 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, commands, or concrete implementation. 'Analyze content' and 'scan documentation files' are vague directions without specific methods or tools. | 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 for edge cases (empty directories, unsupported file types), and no feedback loop for refinement. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. For a skill of this complexity, references to examples of different output formats or a separate file with term extraction patterns would improve navigation. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 | |
- 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.