generate-taxonomy

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

Install with Tessl CLI

npx tessl i github:dandye/ai-runbooks --skill generate-taxonomy

What are skills?

Review — 33%

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/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 identifies a specific domain (hierarchical classification) but is too brief and lacks explicit trigger guidance. It fails to tell Claude when to use this skill and doesn't include enough natural user terms or concrete action examples to reliably distinguish it from other organizational skills.

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 would say: 'taxonomy', 'categories', 'nested structure', 'tree structure', 'categorize', 'organize into groups'.

List additional concrete actions: 'design multi-level taxonomies, define category relationships, create tag hierarchies, structure content catalogs'.

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 specific examples of what operations can be performed.	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. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'hierarchical', 'classification', 'parent-child', 'categorical', and 'content organization', but misses common user terms like 'taxonomy', 'categories', 'tree structure', 'nested categories', or 'organize content'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'hierarchical classification' and 'parent-child categorical structures' provides some specificity, but 'content organization' is generic and could overlap with other organizational or taxonomy-related 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 Claude to actually perform the task. The workflow describes what to do at a high level but never shows how to do it - no code for content analysis, no example taxonomy structures, no specific tools or methods for clustering or term extraction.

Suggestions

Add concrete code examples for content analysis (e.g., using embeddings for clustering, TF-IDF for keyword extraction)

Include a complete example taxonomy output showing the expected YAML/markdown structure with sample categories

Add validation checkpoints with specific criteria (e.g., 'Verify no category has more than 7 children' or 'Check that 90% of documents can be classified')

Provide specific tools or scripts for the clustering and term extraction steps rather than abstract descriptions

Dimension	Reasoning	Score
Conciseness	Reasonably efficient but includes some unnecessary explanation like defining what hierarchical vs faceted means. The Quick Reference section adds minimal value given the content above it.	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

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