MarkItDown vs Skrun

MarkItDown is Microsoft's open-source Python utility that converts virtually any file format into clean, LLM-friendly Markdown. It handles PDFs, Word documents, PowerPoint presentations, Excel spreadsheets, HTML, CSV, JSON, XML, ZIP archives, images (with optional vision model descriptions), audio files (with transcription), YouTube URLs, and EPub files in one consistent interface. The key design philosophy is LLM-first: rather than trying to reproduce original formatting for human readers, MarkItDown preserves document structure—headings, lists, tables, links—in a format that language models naturally parse efficiently. It integrates with OpenAI-compatible vision clients for image descriptions and supports speech transcription for audio content. With 108k+ GitHub stars and still gaining nearly 2,000 per day, MarkItDown has become the default document ingestion layer for countless AI pipelines. As agents increasingly need to process real-world enterprise documents, this kind of robust conversion utility becomes critical infrastructure—turning messy business files into clean inputs that Claude or GPT-4o can reason about without token-wasting formatting artifacts.

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.