skills.rest
Sigmacodeat
SigmacodeatCOMMUNITY
Explore all skills by this author →
GitHub

schema-unify

Migrate fragmented page types to a canonical taxonomy with rollback-safe validation.

Updated Jun 20, 2026
Search Tags:#knowledge graph#data modeling#schema migration#taxonomy#gbrain#type unification
One-click install
npx skills add https://github.com/Sigmacodeat/subsumio-web --skill schema-unify-sigmacodeat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schema-unify
Source: https://github.com/Sigmacodeat/subsumio-web/tree/main/server/skills/schema-unify
Command: npx skills add https://github.com/Sigmacodeat/subsumio-web --skill schema-unify-sigmacodeat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented knowledge schemas by consolidating noisy page types into a stable canonical taxonomy while preserving compatibility and rollback paths.

Core Features & Use Cases

  • Schema Migration Planning: Detects pack upgrades, type proliferation, and migration readiness through onboard checks and explanations.
  • Canonical Type Consolidation: Converts legacy page types into canonical categories with aliases, links, preserved legacy metadata, and verification steps.
  • Use Case: A knowledge brain with dozens of inconsistent document and entity types can use this Skill to safely migrate to a standardized schema without losing historical mappings.

Quick Start

Ask the AI to check my brain schema and migrate it to the canonical taxonomy using the schema unification workflow.

Frequently Asked Questions about schema-unify

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

FAQPage Schema
How do I consolidate fragmented knowledge schemas into a canonical taxonomy?▼

Yes, this Skill handles gbrain migrations by detecting pack upgrades and type proliferation through onboard readiness checks. It converts legacy page types into canonical categories with preserved aliases and rollback-safe transformations.

How do I migrate page types without losing historical mappings in my knowledge graph?▼

To migrate page types without losing historical mappings, the Skill applies alias preservation and legacy metadata retention during the schema migration. This ensures historical data remains accessible while transitioning to the canonical taxonomy.

Can I roll back a schema migration if type consolidation fails?▼

Yes, you can roll back a schema migration because the Skill implements rollback-safe transformation handling and schema verification steps. This ensures you can safely revert the canonical taxonomy migration if validation fails.

What is the best way to clean up type proliferation in a knowledge brain?▼

The best way to clean up type proliferation is to run the schema unification workflow, which performs onboard validation and consolidates inconsistent document types into standardized categories. This safely standardizes your knowledge brain schema without losing historical mappings.

Do I need onboard validation before starting a knowledge graph schema migration?▼

Yes, onboard validation is required before starting a knowledge graph schema migration to detect migration readiness and pack upgrades. This pre-migration check ensures your brain is prepared for the controlled migration execution.

Related Skills

Explore More Software Engineering Skills→
beyonaibeyonai
45

schema-unify

Migrate gbrain-base taxonomy to the gbrain-base-v2 canonical structure.

Community
Advanced
pax-kpax-k
6

tag-taxonomy

Enforce canonical tags from _meta/taxonomy.md across Obsidian wiki pages.

Community
Advanced
skyllwtskyllwt
1.6k

check

Validate entity schema, cross-references, and graph/citation consistency in research wikis.

Community
Advanced
Heretek-AIHeretek-AI

workspace-consolidation

Consolidate fragmented triad workspaces into a single canonical codebase.

Official
Advanced