skills.rest
beyonai
beyonaiCOMMUNITY
Explore all skills by this author →
GitHub

schema-unify

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

45|11|Updated Mar 17, 2026
Search Tags:#schema#migration#taxonomy#knowledge-management#data-cleanup#gbrain
One-click install
npx skills add https://github.com/beyonai/ByClaw --skill schema-unify-beyonai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schema-unify
Source: https://github.com/beyonai/ByClaw/tree/main/middleware/openclaw/skills/gbrain/references/schema-unify
Command: npx skills add https://github.com/beyonai/ByClaw --skill schema-unify-beyonai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves type proliferation in gbrain systems by consolidating fragmented, noisy page types into a clean, 15-type canonical taxonomy, ensuring data consistency and improved searchability.

Core Features & Use Cases

  • Taxonomy Migration: Automatically maps legacy page types to the gbrain-base-v2 canonical standard.
  • Data Cleanup: Converts redundant concept-redirects into alias rows and edge-shaped pages into proper links.
  • Use Case: When a brain has accumulated hundreds of inconsistent page types over time, this skill provides a safe, dry-run enabled path to unify the schema without losing historical context or breaking existing wikilinks.

Quick Start

Run the schema unification process to migrate your current brain to the canonical v2 taxonomy after verifying the proposed changes with an explanation report.

Frequently Asked Questions about schema-unify

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

FAQPage Schema
How do I migrate legacy page types to a canonical taxonomy without losing historical context?▼

You can migrate legacy page types by remapping them to a canonical v2 structure and consolidating alias rows. This process ensures safe schema evolution without breaking existing wikilinks or losing historical data.

What is the best way to clean up redundant concept-redirects in a large knowledge base?▼

The best way to clean up redundant concept-redirects is to convert them into alias rows and transform edge-shaped pages into proper links. This reduces type proliferation and enforces a DRY/MECE data model.

How does schema migration handle type proliferation in knowledge management systems?▼

Schema migration handles type proliferation by consolidating fragmented, noisy page types into a clean, 15-type canonical taxonomy. This enforces data consistency and improves overall searchability across the knowledge base.

Can I run a dry-run to verify schema unification changes before applying them?▼

Yes, you can run a dry-run enabled path to verify proposed changes. The process generates an explanation report, allowing you to review the schema unification impact before manually submitting the handler.

Is manual submission required to execute the taxonomy migration process?▼

Yes, manual submission of the unify-types handler is required. This ensures safe, non-autopilot schema evolution when migrating your brain to the canonical v2 taxonomy.

Related Skills

Explore More Software Engineering Skills→
SigmacodeatSigmacodeat

schema-unify

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

Community
Advanced
weipingweiping
1

schema-unify

Migrate legacy GBrain page types to the gbrain-base-v2 14-type taxonomy.

Community
Advanced
therealityreporttherealityreport

classify-publisher-patterns

Classify publisher technology and layout patterns into a 15-section taxonomy from HTML.

Community
Intermediate
valithedgevalithedge

generate-import-html

Generate sectioned HTML from authoring-analysis data for AEM Edge Delivery Services.

Community
Intermediate