Migrate Documentation to DevDoc

VerifiedSafe

This skill automates migrating documentation from Mintlify, Docusaurus, GitBook, ReadMe, VuePress, MkDocs, and Sphinx into DevDoc format. It auto-detects the source platform, converts config files and platform-specific components (Accordion, Tabs, Notes, etc.), and generates proper navigation structure. Perfect for standardizing your docs into DevDoc without manual rewriting.

Sby Skills Guide Bot
DocumentationIntermediate
3/2/2026
Claude Code
#docs-migration#devdoc#mdx#content-conversion#navigation

Recommended for

Automated summary

This skill walks through migrating existing documentation (Mintlify, Docusaurus, GitBook, ReadMe, VuePress, MkDocs, Sphinx or a lone README) into the DevDoc format.

Strengths

  • A detection table for each platform's config files (mint.json, sidebars.js, SUMMARY.md, mkdocs.yml, etc.)
  • Explicit component-by-component mappings for Mintlify, Docusaurus and GitBook (hints, tabs, Accordion, CodeGroup and more)
  • Clear post-migration validation steps: run /check-docs, preview with devdoc dev, check component rendering and navigation

Limitations

  • ReadMe, VuePress, MkDocs and Sphinx are only detected by format — no mapping tables are provided for them
  • Assumes the devdoc CLI and the /check-docs command are available
  • Covers configuration and component conversion only, not editorial rewriting or content restructuring
When to use it

Use it when a project is leaving Mintlify, Docusaurus or GitBook for DevDoc and needs its config, navigation and MDX components converted.

When not to use it

Don't use it to bootstrap a DevDoc site from scratch or to migrate to any platform other than DevDoc.

Security analysis

Safe
Quality score85/100

The skill contains only documentation migration guidance and format/component mappings. It does not instruct destructive commands, secret exfiltration, obfuscated payloads, or safety bypasses. The referenced validation commands are normal local documentation tooling.

No concerns found

How this analysis is made

Examples

Migrate from Mintlify
Our docs are built with Mintlify (there's a mint.json at the repo root). Migrate everything to DevDoc: convert the config to docs.json, map the navigation and components, and move the assets.
Migrate from Docusaurus
Convert our Docusaurus site to DevDoc format — turn docusaurus.config.js and sidebars.js into docs.json navigation and rewrite the :::note / :::tip admonitions as DevDoc components.
README-only project
We only have a README.md with no docs platform. Set it up as a DevDoc project: generate docs.json, a theme.json, and the initial navigation structure.

name: migrate-docs description: Migrate documentation from other platforms (Mintlify, Docusaurus, GitBook, README) to DevDoc format

Instructions

When migrating documentation from another platform:

Step 1: Detect Source Format

Identify the documentation source by looking for:

| Platform | Detection Files | |----------|-----------------| | Mintlify | mint.json, .mintlify/ | | Docusaurus | docusaurus.config.js, sidebars.js | | GitBook | SUMMARY.md, .gitbook.yaml | | ReadMe | readme-oas.json, .readme/ | | VuePress | .vuepress/config.js | | MkDocs | mkdocs.yml | | Sphinx | conf.py, index.rst | | README only | README.md (no other docs) |

Step 2: Migration Mappings

Mintlify → DevDoc

mint.json → docs.json
├── name → name
├── logo → (extract to assets/logo/)
├── favicon → favicon
├── colors → theme.json
├── navigation → navigation.tabs + groups
├── topbarLinks → navbar
├── anchors → navigation.global.anchors
└── api → api

Component Mappings:
├── <Accordion> → <Accordion>
├── <AccordionGroup> → <AccordionGroup>
├── <Card> → <Card>
├── <CardGroup> → <CardGroup>
├── <CodeGroup> → <Tabs> with code
├── <Tabs> → <Tabs>
├── <Tab> → <Tab>
├── <Info> → <Info>
├── <Note> → <Note>
├── <Tip> → <Tip>
├── <Warning> → <Warning>
├── <Check> → <Tip> (with check icon)
├── <Steps> → <Steps>
├── <Step> → <Step>
├── <Frame> → (image wrapper, convert to <img>)
├── <ResponseField> → (convert to table)
└── <ParamField> → (convert to table)

Docusaurus → DevDoc

docusaurus.config.js → docs.json
├── title → name
├── favicon → favicon
├── themeConfig.navbar → navbar
├── themeConfig.footer → (extract links to anchors)
└── docs.sidebarPath → navigation

sidebars.js → navigation.tabs[].groups

Component Mappings:
├── :::note → <Note>
├── :::tip → <Tip>
├── :::info → <Info>
├── :::caution → <Warning>
├── :::danger → <Warning>
├── <Tabs> → <Tabs>
├── <TabItem> → <Tab>
└── import/export → (inline or convert to snippets)

GitBook → DevDoc

SUMMARY.md → docs.json navigation
├── # Group → groups[].group
├── * [Page](path.md) → groups[].pages[]
└── Nested items → nested groups

Component Mappings:
├── {% hint style="info" %} → <Info>
├── {% hint style="warning" %} → <Warning>
├── {% hint style="danger" %} → <Warning>
├── {% hint style="success" %} → <Tip>
├── {% tabs %} → <Tabs>
├── {% tab title="X" %} → <Tab title="X">
├── {% code title="X" %} → ```language title="X"
└── {% embed url="X" %} → <iframe> or link

Step 3: Execute Migration

  1. Convert configuration files
  2. Transform MDX/MD content with component mappings
  3. Copy and organize assets
  4. Generate docs.json navigation
  5. Create theme.json from color settings

Step 4: Post-Migration Validation

After migration:

  1. Run /check-docs to verify all links work
  2. Preview with devdoc dev
  3. Check component rendering
  4. Verify navigation structure

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/migrate-documentation-to-devdoc-mm8o52r0/download' --output '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md.part' && mv '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md.part' '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md' && test -s '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/migrate-docs' && cp -R '.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0' '.claude/skills/migrate-docs'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/migrate-documentation-to-devdoc-mm8o52r0'

openskills read 'migrate-documentation-to-devdoc-mm8o52r0'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/migrate-documentation-to-devdoc-mm8o52r0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills