About this Skill
Use a Python CLI to parse local files or public document URLs and return Markdown to an agent. The default cloud route uses MinerU services; an optional local engine handles supported PDFs with an existing text layer. Root and Claude-plugin entrypoints describe the same mineru workflow, rather than separate catalog tasks.
Why we picked it
An agent-oriented CLI around MinerU, adding Markdown stdout, machine-readable status, resumable batches and explicit cloud/local modes.
What it helps with
- Extract readable text, tables and formulas for a document workflow.
- Process a folder of documents with resumable batches.
- Return Markdown directly to an agent or write a local knowledge folder.
Workflow
Choose the processing route
Decide whether the input needs cloud OCR or the optional local text-PDF engine.
Parse and inspect status
Run the CLI with --stdout for Markdown or --json for machine-readable status; use --resume for repeated batches.
Check extracted content
Inspect tables, formulas and images against source pages before reusing the Markdown.
Installation and runtime
Install the Skill instructions, then provision the documented runtime dependencies before running a task.
| Command | What it helps with |
|---|---|
python3 scripts/mineru.py paper.pdf --stdout | Return parsed Markdown to the terminal. |
python3 scripts/mineru.py paper.pdf --json | Return machine-readable parsing status. |
python3 scripts/mineru.py --doctor | Check the local environment and optional integrations. |
Scope and practical limits
This is a third-party workflow around MinerU, separate from the already-listed MinerU engine. Cloud OCR and local text parsing are different execution paths.
License and source
The project is distributed under MIT. Agent subscriptions, external services and optional integrations have their own requirements.
Before you use it
- Python 3.8+ for the standard-library CLI; optional local parsing, splitting and integrations need their own extras.
- Default cloud processing transfers documents to MinerU. Tokens, quotas and supported formats depend on the provider and selected route.
- The token-free Agent route and token-based Standard route have different limits. Verify the current provider conditions before large jobs.
Supported agents
Sources & references
Original sources are linked below. Practical starting points are editorial suggestions from SkillHey.
