RAG-Anything vs Skrun

RAG-Anything is an All-in-One Multimodal Retrieval-Augmented Generation framework from Hong Kong University's Data Science lab that finally breaks RAG out of its text-only box. It ingests PDFs, Office documents, images, tables, charts, and mathematical equations through a unified 5-stage pipeline — parsing, element extraction, knowledge graph construction, multimodal indexing, and hybrid retrieval. Under the hood, it builds a multimodal knowledge graph with automatic entity extraction and cross-modal relationship discovery, then uses vector-graph fusion to combine semantic embeddings with structural relationships. A VLM-Enhanced Query mode integrates visual content directly into LLM responses, so you can ask questions that span a chart and its surrounding text and get a coherent answer. Built on LightRAG, it supports concurrent multi-pipeline architecture for parallel text and multimodal processing. It hit 17,500+ stars on GitHub shortly after release, making it one of the fastest-growing RAG libraries in 2026. For teams building enterprise document intelligence — legal contracts, scientific papers, financial reports — this fills a real gap that vanilla RAG systems have always had. MIT licensed, Python-based, and straightforward to integrate.

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.