skills.rest
seangeng
seangengCOMMUNITY
Explore all skills by this author →
Website𝕏@0xGengGitHub

holydocs-migrate

Migrate documentation from Mintlify, GitBook, Docusaurus, ReadMe, and VuePress to HolyDocs.

Updated Apr 11, 2026
Search Tags:#documentation#readme#docusaurus#migrate#mintlify#vuepress#gitbook
One-click install
npx skills add https://github.com/seangeng/holydocs-skills --skill holydocs-migrate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: holydocs-migrate
Source: https://github.com/seangeng/holydocs-skills/tree/main/holydocs-migrate
Command: npx skills add https://github.com/seangeng/holydocs-skills --skill holydocs-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate documentation from Mintlify, GitBook, Docusaurus, ReadMe, and VuePress to HolyDocs, enabling a unified documentation surface without manual reformatting.

Core Features & Use Cases

  • Platform-agnostic migration: Detects source platforms via common markers and guides users through the end-to-end migration workflow.
  • Dry-run and merge capabilities: Provides a safe preview before applying changes and supports merging into existing HolyDocs projects.
  • Verification & fixes: After migration, runs checks to fix broken links, missing assets, and navigation alignment, ensuring a smooth production-ready result.
  • Open workflow guidance: Includes decision flow for platform detection and step-by-step migration path from source to HolyDocs.

Quick Start

Run holydocs migrate --from <platform> to begin migrating the project.

Frequently Asked Questions about holydocs-migrate

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

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

Documentation migration detects source platforms via marker files like mint.json, docusaurus.config.js, .gitbook.yaml, and readme.yaml, then guides you through an end-to-end conversion workflow to HolyDocs.

Can I preview my documentation migration before applying changes?▼

Yes, you can perform a dry-run to safely preview the documentation migration before executing the full conversion, ensuring no unintended changes are applied to your project.

Does the migration tool support merging converted documentation into an existing project?▼

Yes, the migration workflow supports optional merging, allowing you to integrate converted documentation directly into existing HolyDocs projects without manual reformatting.

What is the best way to fix broken links and missing assets after migrating docs?▼

After migration, the tool runs verification checks to automatically fix broken links, missing assets, and navigation alignment, ensuring a smooth, production-ready documentation output.

How do I start migrating my GitBook or Readme documentation?▼

To start migrating GitBook or Readme documentation, run the migrate command with the source platform flag; the tool recognizes marker files like .gitbook.yaml and readme.yaml to begin the workflow.

Related Skills

Explore More Content & Communication Skills→
lengo0951lengo0951

ck:deploy

Automate software deployment across platforms using config files and documentation.

Community
Advanced
CERTCCCERTCC
21

build-docs

Validate markdown documentation with strict mkdocs build checks.

Official
Intermediate
JongsixJongsix

moai-docs-generation

Generate technical documentation from source code and API definitions.

Community
Advanced
iankikuiankiku
18

voice

Define personal writing voice guidelines in Markdown files for AI-generated content.

Community
Basic