minerupress

Convert MinerU parsing artifacts into chapter-split MkDocs Material book sites.

56|11|Updated May 16, 2026
One-click install
npx skills add https://github.com/aronnaxlin/minerupress --skill minerupress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minerupress
Source: https://github.com/aronnaxlin/minerupress/tree/main/skills/minerupress
Command: npx skills add https://github.com/aronnaxlin/minerupress --skill minerupress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MineruPress eliminates the manual, error-prone work of converting scattered MinerU JSON/text and images into a clean, chapter-split MkDocs Material book site.

Core Features & Use Cases

  • Workflow from MinerU results to chapters: Exports MinerU output into docs/chapters/ and docs/images/ suitable for immediate deployment.
  • Config-driven chapter boundary quality: Uses titles, aliases, and regex patterns (plus an optional headings inspection step) to reliably derive chapter boundaries.
  • Three source modes for different starting points: Supports uploaded_result (local results), official_api (PDF-to-cloud parsing), and local_toolchain (PDF-to-local MinerU CLI), without bundling MinerU.

Quick Start

Ask the AI to help you create a book workspace, set one source mode in book.yml, and run minerupress export book.yml to generate MkDocs Material chapters.

Frequently Asked Questions about minerupress

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

FAQPage Schema
How do I convert MinerU output into a chapter-split MkDocs Material publishing site?

You can convert MinerU output into a chapter-split MkDocs Material site by configuring a book workspace in book.yml and running minerupress export to generate deterministic docs/chapters and docs/images structures.

What is the best way to structure scattered MinerU parsing artifacts into a book?

Structuring scattered MinerU JSON and text artifacts into a book requires config-driven chapter boundaries, using titles, aliases, and regex patterns to reliably derive chapters from the parsed inputs.

Can I use a local MinerU CLI with MkDocs Material for PDF publishing workflows?

Yes, local_toolchain source mode supports using a separately installed local MinerU CLI to parse PDFs before configuring book.yml and exporting the results to MkDocs Material.

Do I need to install MinerU to use the official API for cloud parsing in my publishing workflow?

No, you do not need to install MinerU locally to use the official_api source mode, which handles PDF-to-cloud parsing directly without bundling the MinerU software into your workflow.

How does headings inspection improve chapter boundary configuration for PDF outputs?

Headings inspection is an optional step that verifies config-driven chapter boundaries derived from titles, aliases, and regex patterns, ensuring accurate chapter splitting before generating MkDocs Material files.

Why does mkdocs build --strict fail after exporting MinerU results to chapters?

mkdocs build --strict failure indicates production verification issues in the exported MkDocs Material site, requiring you to fix configuration or content errors in book.yml and the generated docs/chapters directory.