Define canonical closed enums for protocol classification and taxonomy.
npx skills add https://github.com/jacob-balslev/skills --skill skill-graph-taxonomy
Please help me install this Agent Skill. Skill: skill-graph-taxonomy Source: https://github.com/jacob-balslev/skills/tree/main/skill-graph-taxonomy Command: npx skills add https://github.com/jacob-balslev/skills --skill skill-graph-taxonomy
Defines protocol-level closed enums for scope, category, type, dimensions, verdict tiers, drift_status, relation types, and routing roles to ensure consistent classifications across the Skill Graph ecosystem.
Consult this skill when proposing changes to protocol classifications or performing schema migrations to maintain cross-tool consistency.
High-intent search queries and answers about installing and using this skill.
Protocol taxonomy uses closed enums to define canonical classifications for scope, category, type, and relation types. You need them to enforce classification consistency and ensure interoperability across lint, manifest, router, and audit tools.
To prevent enum drift during schema migrations, consult the canonical closed enum definitions for drift_status and verdict tiers. This ensures proposed changes align with the authoritative reference and maintain cross-tool consistency.
Yes, you can use this to coordinate governance workflows across project boundaries. It establishes a canonical schema for protocol classification that coordinates taxonomy consistently across different domains and project limits.
The best way to establish consistent relation types and routing roles is to define them as canonical closed enums. This approach serves as the authoritative reference for all ecosystem tools, avoiding classification drift.
You should not use closed enums for protocol classification when your schema requires open-ended, extensible categories that change dynamically outside of formal governance workflows, because closed enums enforce strict, predefined values.
sgpropertyanalyticsEnforce canonical enums and classifications across backend and frontend data displays.
axone-protocolExecute Rust project quality gates for format, lint, tests, coverage, schema, and docs.
EmasoftValidate Claude Code plugin manifests, hooks, skills, MCP servers, and marketplace entries.
dandyeDefine Dublin Core-aligned metadata schemas for content assets in JSON-schema, XML, or Markdown with validation rules and mappings.
