mxMigrateToDb

Import local Markdown documents from docs/ into the MCP Knowledge-DB.

29|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/MicrotronX/mxLore --skill mxmigratetodb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxMigrateToDb
Source: https://github.com/MicrotronX/mxLore/tree/main/claude-setup/skills/mxMigrateToDb
Command: npx skills add https://github.com/MicrotronX/mxLore --skill mxmigratetodb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates local Markdown documents from docs/ into the MCP Knowledge-DB, centralizing project knowledge and enabling consistent retention and retrieval.

Core Features & Use Cases

  • Detects document types from filenames (PLAN-, SPEC-, ADR-, session-notes-, workflow-log-, and references) and imports them into the Knowledge-DB.
  • Supports multiple operation modes (dry-run, cleanup, sync, scan, extract-backlog) for safe, staged migrations.
  • Establishes cross-document relations post-import to build a navigable knowledge graph and maintain traceability.

Quick Start

Start the migration by importing all local docs from docs/ into the Knowledge-DB, using optional modes like --dry-run or --sync as appropriate.

Frequently Asked Questions about mxMigrateToDb

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

FAQPage Schema
How do I migrate local Markdown docs to a knowledge database automatically?

To migrate local Markdown docs to a knowledge database automatically, use a batch pipeline that imports files from a docs/ folder, auto-detects document types from filenames, and normalizes status from content before creating entries.

Can I preview a Markdown migration before making permanent changes?

Yes, you can preview a Markdown migration before making permanent changes by running the process in dry-run mode, which scans your local documents and checks for duplicates against the database inventory without writing data.

Does the Markdown migration tool detect different document types like plans and specs?

Yes, the Markdown migration tool detects different document types like plans and specs by parsing filenames. It recognizes patterns for PLAN-, SPEC-, ADR-, session-notes, workflow-logs, and references to categorize imports accurately.

What is the best way to build a navigable knowledge graph from existing project docs?

The best way to build a navigable knowledge graph from existing project docs is to batch import Markdown files and automatically establish cross-document relations post-import, maintaining traceability between plans, specs, and decisions.

How do I avoid duplicate entries when syncing Markdown files to a knowledge base?

To avoid duplicate entries when syncing Markdown files to a knowledge base, the migration pipeline checks your documents against an existing database inventory during the import process and normalizes status from content to ensure consistency.