RAG-Anything vs Skrun

RAG-Anything is an all-in-one Retrieval-Augmented Generation framework from HKUST's Data Systems Group that handles multimodal documents through a single unified pipeline. Unlike RAG frameworks that only handle plain text, it natively ingests and retrieves across text, tables, images, scientific figures, and mixed-modality documents without requiring separate preprocessing pipelines for each type. The framework covers the full RAG stack: document parsing, chunking strategies adapted to content type, embedding, vector storage, retrieval ranking, and generation. It's built to handle the kinds of documents that real enterprise workloads throw at you — PDFs with embedded tables, research papers with figures, reports that mix structured and unstructured content. With 16,000+ stars and academic backing from HKUDS (the same group behind LightRAG), it carries credibility beyond typical weekend projects. The key insight is that most RAG failures in production happen at the parsing and modality-handling stage, not the retrieval stage. By making multimodal handling a first-class concern rather than a bolt-on, RAG-Anything aims to close the gap between RAG demos and RAG production deployments.

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.