generate-taxonomy

$npx mdskill add dandye/ai-runbooks/generate-taxonomy

Build hierarchical content structures for organized knowledge bases.

  • Organizes documents into parent-child categories using similarity clustering.
  • Integrates with content repositories via the PATH input parameter.
  • Decides structure by analyzing keywords and applying business alignment rules.
  • Delivers output as defined categorical hierarchies or faceted dimensions.

SKILL.md

.github/skills/generate-taxonomyView on GitHub ↗
---
name: generate-taxonomy
description: Develop hierarchical classification systems. Creates parent-child categorical structures for content organization.
required_roles:
  scribe: roles/scribe.editor
personas: [information-architect, taxonomist, knowledge-manager]
---

# Generate Taxonomy Skill

Develop a hierarchical classification system or taxonomy for a knowledge base or content repository. This skill creates parent-child categorical structures to organize content effectively.

## Inputs

- `PATH` - The content source to analyze (e.g., "/knowledge-base")
- `FACETED` - (Optional) Boolean, whether to create a faceted classification (multiple dimensions) (default: false)
- `BUSINESS_ALIGNMENT` - (Optional) Boolean, whether to align with specific business goals/terminology (default: true)
- `USER_TESTING` - (Optional) Boolean, whether to include user validation methodologies in the output (default: false)

## Workflow

### Step 1: Content Analysis & Term Extraction

Analyze the content at `PATH` to identify key topics, subjects, and categories.
- Cluster documents by similarity.
- Extract common tags and keywords.

### Step 2: Structure Design

Organize the extracted concepts into a hierarchy.
- **Hierarchical**: Define Broader Terms (Parent) and Narrower Terms (Child).
- **Faceted** (if enabled): Define dimensions (e.g., Topic, Format, Audience, Region).

### Step 3: Business & User Alignment

- Align terms with business vocabulary (if `BUSINESS_ALIGNMENT` is true).
- If `USER_TESTING` is true, generate a plan for card sorting or tree testing to validate the structure.

### Step 4: Taxonomy Definition

Output the defined taxonomy.

## Required Outputs

A `TAXONOMY_DEFINITION` document (e.g., in markdown or YAML format) containing:
- **Taxonomy Tree**: Visual or indented list of categories.
- **Facets** (if requested): Definitions of classification dimensions.
- **Rules**: Guidelines for applying the taxonomy.
- **Testing Plan** (if requested): Methodologies for validation.

## Quick Reference

- **Purpose**: Systematically classify content for retrieval optimization.
- **Types**: Hierarchical (Tree) vs. Faceted (Matrix).

More from dandye/ai-runbooks

SkillDescription
analyze-content-gapsIdentify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.
audit-contentComprehensive content quality and maintenance assessment. Evaluates documentation quality, relevance, maintenance needs, and provides actionable recommendations.
check-duplicates"Check for duplicate or similar cases. Use before deep analysis to avoid investigating the same incident twice. Takes a CASE_ID and returns list of similar cases."
close-case-artifact"Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause."
cluster-documentsAutomated content similarity and grouping analysis. Groups related documents by topic, purpose, or content similarity.
confirm-action"Ask the user to confirm before taking a significant action. Use before containment, remediation, or other impactful operations to ensure analyst approval. Presents options and waits for response."
correlate-ioc"Check for existing SIEM alerts and case management entries related to IOCs. Use to understand if an indicator has triggered previous alerts or is part of ongoing investigations. Takes IOC list and returns related alerts and cases."
deep-dive-ioc"Perform exhaustive analysis of a critical IOC. Use when an IOC needs Tier 2+ investigation beyond basic enrichment - includes GTI pivoting, deep SIEM searches, correlation with related entities, and threat attribution. For escalated IOCs requiring comprehensive investigation."
design-metadata-schemaDesign comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.
document-in-case"Add a comment to a case to document findings, actions, or recommendations. Use to maintain audit trail during investigations. Requires CASE_ID and comment text."