Google ADK vs Skrun

Google Agent Development Kit (ADK) is an open-source Python framework for building, composing, and deploying multi-agent AI systems. It handles the hard parts of agent orchestration — tool use, memory, inter-agent communication, and deployment — with first-class support for Gemini models and Google Cloud, but designed to be model-agnostic. The framework reached 8,200+ GitHub stars within weeks of launch, making it one of the fastest-growing agent infra repos this spring. ADK ships with built-in support for common agent patterns (sequential, parallel, coordinator-worker), a robust tool abstraction layer, and native MCP support. It integrates cleanly with Google's broader AI stack (Vertex AI, Cloud Run) but also works standalone with other model providers. ADK enters a crowded field — LangGraph, CrewAI, and AutoGen all offer overlapping functionality — but Google's official backing, deep Gemini integration, and the framework's quality-of-life improvements (particularly around deployment and state management) have made it an instant reference implementation for many teams.

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.