generate-taxonomy

Develop hierarchical classification systems. Creates parent-child categorical structures for content organization.

Quality

33%

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-taxonomy/SKILL.md

Quality

Discovery

32%

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 provides a reasonable explanation of what the skill does but fails to include explicit trigger guidance for when to use it. The language is somewhat technical and could benefit from more natural user terms and concrete examples of use cases.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user needs to create taxonomies, organize content into categories, build nested category trees, or design classification hierarchies.'

Include more natural trigger terms users might say: 'taxonomy', 'categories', 'nested categories', 'tree structure', 'content hierarchy', 'tagging system'.

Add specific concrete actions beyond 'creates structures', such as 'design multi-level taxonomies, define category relationships, map content to classification nodes'.

Dimension	Reasoning	Score
Specificity	Names the domain (hierarchical classification systems) and describes the action (creates parent-child categorical structures), but lacks multiple concrete actions or examples of what this entails in practice.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'hierarchical', 'classification', 'parent-child', 'categorical', but misses common user language like 'taxonomy', 'categories', 'organize content', 'nested categories', or 'tree structure'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'hierarchical classification' and 'parent-child structures' provides some distinction, but 'content organization' is generic enough to potentially overlap with other organizational or categorization skills.	2 / 3
	Total	7 / 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 reasonable conceptual framework for taxonomy generation but lacks the concrete, executable guidance needed for actionability. The workflow describes what to do at a high level but not how to actually accomplish each step. The absence of code examples, specific commands, or sample outputs significantly limits its practical utility.

Suggestions

Add concrete code examples for content analysis and term extraction (e.g., using NLP libraries or specific file parsing approaches)

Include a sample taxonomy output in YAML or markdown format showing the expected structure

Add validation checkpoints between steps (e.g., 'Review extracted terms before proceeding to structure design')

Provide specific criteria or heuristics for deciding hierarchy depth and category boundaries

Dimension	Reasoning	Score
Conciseness	Reasonably efficient but includes some unnecessary explanation like defining what hierarchical vs faceted means. The inputs section with defaults is useful but could be tighter.	2 / 3
Actionability	Entirely abstract with no concrete code, commands, or executable examples. Steps like 'Cluster documents by similarity' and 'Extract common tags' provide no actual implementation guidance.	1 / 3
Workflow Clarity	Steps are listed in sequence but lack validation checkpoints. No feedback loops for verifying taxonomy quality or iterating on structure. Missing concrete criteria for when each step is complete.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline. For a skill of this complexity, examples of taxonomy outputs or detailed facet definitions could be split into referenced 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.