docs-from-docslisted

Import existing documentation from Mintlify, GitBook, Docusaurus, Nextra, or VitePress into a clean docs-output/<name>/ folder ready for Docsbook. Preserves structure and content; normalises platform-specific syntax to plain Markdown. Use when migrating away from another docs platform.
Docsbook-io/docs-skills · ★ 1 · AI & Automation · score 75

Install: claude install-skill Docsbook-io/docs-skills

# docs-from-docs — Import from another docs platform This skill is the executor — read the source platform, mirror its structure, normalise the syntax, and publish. Because you are migrating an existing docs site, the folder structure is already there: reproduce it faithfully (its nav → the sub-header). The one enrichment worth adding is a `faq.md` / `use-cases` page if the source lacks one — it kills evaluation objections and feeds the AEO layer. ## Workflow 0. **Name the project — don't invent it.** Take the name from the source repo name, the existing docs site's brand (`<title>` / `og:site_name`), or the platform config's title field. Use it for the `docs-output/<name>/` folder and the workspace display name. If none is readable, ask the user — never use a placeholder. 1. **Identify the platform.** Read the repo root for the marker file: | Marker | Platform | |---|---| | `mint.json` / `docs.json` | Mintlify | | `SUMMARY.md` at root | GitBook | | `docusaurus.config.js` / `.ts` | Docusaurus | | `theme.config.tsx` + Next.js | Nextra | | `.vitepress/config.*` | VitePress | | `astro.config.*` + `@astrojs/starlight` | Starlight | 2. **Read the navigation.** Each platform stores nav differently — `mint.json#navigation`, `SUMMARY.md`, `docusaurus.config.js#sidebars`, `.vitepress/config.ts#themeConfig.sidebar`. Build a flat list of `{label, sourcePath}` entries in display order. 3. **Copy and normalise pages.** For every entry, read the source `.md` /