brain-taxonomist

Route new brain content to the correct directory and page type using the active schema pack.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill brain-taxonomist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-taxonomist
Source: https://github.com/weiping/gbrain-cn/tree/main/skills/brain-taxonomist
Command: npx skills add https://github.com/weiping/gbrain-cn --skill brain-taxonomist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

brain-taxonomist prevents misfiling by determining the correct directory path for every new brain write using the currently active schema pack, so your knowledge base stays consistent over time.

Core Features & Use Cases

  • Schema-driven routing (no hardcoded paths): Uses the ACTIVE schema pack via gbrain schema show --json to pick the canonical path prefix and relevant page type.
  • Deterministic, reproducible decisions: Recommends the same filing path for the same content to avoid drift and inconsistent organization.
  • Ambiguity handling via user prompting: Surfaces unclear cases for EIIRP Phase 2/Phase 3 rather than silently choosing the closest directory.
  • Periodic taxonomy drift detection: Supports review of orphaned/outgrown pages through schema review-orphans and health checks with gbrain doctor.

Quick Start

Ask the brain-taxonomist skill to recommend where a new brain page should be filed according to your active schema pack.

Frequently Asked Questions about brain-taxonomist

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

FAQPage Schema
How do I prevent taxonomy drift when filing new content into a knowledge graph?

To prevent taxonomy drift, you need deterministic schema routing for new content. This skill validates new pages against the active schema pack's canonical path prefixes and page types, ensuring every write is reproducibly filed in the correct directory.

What is the best way to bulk import pages into a multi-tenant knowledge base without misclassification?

The best way to avoid misclassification during bulk imports is to apply a primary subject type router. This skill processes bulk imports by routing each entry to a person, organization, temporal event, concept, media, or source data directory based on the active schema.

Can I use per-source overrides to change the filing directory for specific content imports?

Yes, you can use per-source overrides alongside the active schema pack. This allows you to customize the routing path for specific imports while maintaining deterministic classification for the primary subject types being filed.

How do I detect orphaned or outgrown pages causing taxonomy drift in my knowledge base?

You can detect taxonomy drift and orphaned pages by running periodic health checks. This skill supports reviewing outgrown content through schema review-orphans and health validation commands to maintain knowledge base consistency.