migrate-docs

Migrate Mintlify, Docusaurus, GitBook, and ReadMe documentation into DevDoc format.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/brainfish-ai/devdoc --skill migrate-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-docs
Source: https://github.com/brainfish-ai/devdoc/tree/main/public-apis/meta/.claude/skills/migrate-docs
Command: npx skills add https://github.com/brainfish-ai/devdoc --skill migrate-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating documentation between platforms is error-prone and time-consuming. This skill standardizes and accelerates the process by translating Mintlify, Docusaurus, GitBook, and ReadMe docs into the DevDoc schema, preserving structure and content.

Core Features & Use Cases

  • Platform detection and source format identification to guide migration.
  • End-to-end mappings from Mintlify, Docusaurus, GitBook, and ReadMe to DevDoc structures, including navigation, metadata, and content.
  • Asset and content migration with optional reference materials and on-demand asset integration.
  • Validation and preview steps via built-in checks and local DevDoc preview.

Quick Start

Invoke the migrate-docs skill with a path to your source documentation and run the migration workflow. Example: set SOURCE_DIR=/path/to/docs and execute the migration command through the DevDoc CLI, then review the generated docs.json and theme.json before importing.

Frequently Asked Questions about migrate-docs

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

FAQPage Schema
How do I migrate documentation from Docusaurus or Mintlify to DevDoc?▼

To migrate documentation from Docusaurus or Mintlify to DevDoc, the skill detects the source format and applies end-to-end platform mappings to generate DevDoc-compatible artifacts like docs.json and theme.json.

What is the best way to convert GitBook or ReadMe docs into DevDoc format?▼

The best way to convert GitBook or ReadMe docs into DevDoc format is using a migration skill that standardizes structure, navigation, metadata, and content translation to preserve your original documentation.

Can I preview my migrated documentation before importing it into DevDoc?▼

Yes, you can preview migrated documentation before importing it into DevDoc. The migration process includes built-in validation checks and supports a local DevDoc preview step to verify the output.

How does documentation migration handle navigation and metadata mapping?▼

Documentation migration handles navigation and metadata mapping by applying end-to-end platform-specific mappings that translate source structures directly into the DevDoc schema, preserving the original content hierarchy.

What files are generated when migrating docs to DevDoc?▼

When migrating docs to DevDoc, the process generates DevDoc-compatible artifacts such as docs.json and theme.json, which contain the standardized navigation, metadata, and theme configurations for import.