RAG-Anything vs Skrun

RAG-Anything is an open-source framework from the Hong Kong University of Science and Technology (HKUST) Data Science group that extends Retrieval-Augmented Generation to handle arbitrary document types in a single unified pipeline. While most RAG implementations are text-only and break on PDFs with tables, charts, or mixed layouts, RAG-Anything handles text, images, tables, mathematical formulas, and mixed documents without preprocessing hacks. The framework introduces a universal document parser that preserves semantic structure across formats, a heterogeneous chunking strategy that chunks different modalities independently before linking them, and a cross-modal retriever that can match a text query against an image or table just as naturally as against a text passage. It integrates with LightRAG for graph-based knowledge organization. Trending on Hugging Face today, RAG-Anything addresses one of the most common failure modes practitioners hit when moving RAG from toy demos to real enterprise documents. Legal PDFs with tables, scientific papers with figures, slide decks with mixed layouts — all of these now work out of the box.

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.