taxonomy-design

Design controlled classification taxonomies with category trees and facet governance.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill taxonomy-design-jacob-balslev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taxonomy-design
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/taxonomy-design
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill taxonomy-design-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build a controlled taxonomy that stays consistent over time so people and agents can reliably browse, find, and assign the right categories.

Core Features & Use Cases

  • Controlled hierarchy design: Create category trees where each child is a true subtype of its parent.
  • Facet and tagging governance: Move cross-cutting dimensions into facets or tags instead of duplicating branches.
  • Drift-aware cleanup: Define assignment rules and eliminate duplicates so the taxonomy doesn’t become a catch-all.

Quick Start

Use the taxonomy-design skill to design a category tree and facet plan for your skill library that prevents mixing incompatible organizing principles.

Frequently Asked Questions about taxonomy-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a controlled vocabulary for a category hierarchy?▼

Designing a controlled vocabulary requires building a category hierarchy where each child node is a true subtype of its parent, applying IS-A substitution checks to ensure consistent classification and reliable item retrieval across the structure.

What is the best way to prevent taxonomy drift in a tagging system?▼

Preventing taxonomy drift requires defining explicit assignment rules and moving cross-cutting dimensions into faceted classifications or tags, eliminating duplicate branches so the tagging system avoids becoming an uncontrolled catch-all.

When do I need faceted classification instead of a single category tree?▼

You need faceted classification when items possess cross-cutting attributes that shouldn't be duplicated across a single category tree, allowing users to filter by multiple independent dimensions rather than navigating one rigid hierarchy.

How do I set up governance rules for synonyms and sibling categories?▼

Setting up governance rules requires defining explicit boundary definitions between sibling categories and establishing controlled vocabulary policies that specify when terms are synonyms versus distinct categories, ensuring consistent item assignment.

Can I use this approach to organize a knowledge graph using SKOS?▼

Organizing a knowledge graph with SKOS principles involves applying controlled taxonomy design to define semantic relations, category hierarchies, and explicit assignment rules that maintain consistent classification boundaries across related concepts.

What are the limitations of relying on a single organizational principle for a product catalog?▼

Relying on a single organizational principle for a product catalog limits browsability when items have multiple valid access points, requiring faceted classification and tagging governance to prevent mixing incompatible hierarchical structures.