kb-migrate

Migrate project knowledge bases to the current roster schema with human approval gates.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill kb-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-migrate
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/kb-migrate
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill kb-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually migrating a project knowledge base to a new schema is time-consuming, error-prone, and often leads to broken links, inconsistent frontmatter, or lost content if not done carefully. This Skill eliminates those risks by providing a structured, validated migration workflow.

Core Features & Use Cases

  • 5-Phase Human-Gated Workflow: Runs sequential audit, cleanup, reorganization, frontmatter migration, and verification steps, with explicit human approval required before each phase proceeds to prevent unintended changes.
  • Idempotent Execution: Running the Skill multiple times on the same KB produces no additional changes, so you can safely re-run it if needed without risking duplicate work or corruption.
  • Use Case: Your team has an existing project KB with outdated frontmatter, broken links, and unstructured files. Use this Skill to safely upgrade it to the current roster schema while preserving all existing content and ensuring no broken references remain.

Quick Start

Use the kb-migrate skill to migrate your project's existing knowledge base to the current roster schema.

Frequently Asked Questions about kb-migrate

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

FAQPage Schema
How do I migrate a knowledge base to a new schema without breaking links?

Schema migration for a knowledge base requires a structured workflow with frontmatter standardization, link validation, and post-migration verification to ensure zero broken references and no data loss.

What is an idempotent knowledge base schema upgrade?

An idempotent knowledge base schema upgrade ensures that running the migration process multiple times on the same files produces no additional changes, preventing duplicate work or content corruption during structural cleanup and reorganization.

How do I standardize frontmatter and fix broken links in an existing project knowledge base?

To standardize frontmatter and fix broken links in an existing project knowledge base, apply a sequential workflow covering audit, cleanup, reorganization, and frontmatter migration, followed by strict verification checks.

Can I automate knowledge base migration while requiring manual approval at each step?

Yes, you can automate knowledge base migration with mandatory human approval gates at every workflow phase, ensuring explicit human review is required before the audit, cleanup, reorganization, frontmatter migration, and verification steps proceed.

What are the limitations of manual schema migration for project knowledge bases?

Manual schema migration for project knowledge bases is time-consuming, error-prone, and often leads to broken links, inconsistent frontmatter, or lost content if not executed carefully through a validated, structured workflow.

Does the kb-migrate Skill work for teams with pre-existing unstructured knowledge bases?

Yes, kb-migrate is designed specifically for teams with pre-existing knowledge bases requiring structural cleanup, applying a 5-phase human-gated workflow to safely upgrade unstructured files to the current roster schema.