MinerU2.5 vs Skrun

MinerU2.5 is a 1.2-billion parameter vision-language model purpose-built for high-resolution document parsing. From OpenDataLab, it's the latest version of a project that's accumulated 61.5K GitHub stars — which tells you something about how painful document-to-text has been as a category. The model uses a decoupled vision-language architecture for efficient high-resolution processing with state-of-the-art recognition accuracy across tables, formulas, figures, and mixed-layout documents. The core use case is turning messy PDFs, scanned forms, academic papers, and enterprise documents into clean Markdown or structured JSON that LLMs can actually work with. Earlier MinerU versions were already widely adopted for RAG pipeline preprocessing — 2.5 tightens up accuracy on the edge cases that killed earlier tools: rotated pages, dense tables, multi-column layouts, and multilingual content. At 1.2B parameters it's lightweight enough to run locally without a GPU farm, and the Apache 2.0 license means it integrates cleanly into commercial document pipelines. For anyone building RAG applications, AI research assistants, or document intelligence products, this is the preprocessing layer that removes a persistent pain point.

Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.