Hermes Agent vs Skrun

Hermes Agent is NousResearch's open-source AI assistant built around a closed-loop learning architecture — the agent doesn't just execute tasks, it synthesizes new skills from complex interactions, self-improves those skills during use, and maintains a deepening model of the user across sessions. With 115,000+ GitHub stars, it has become one of the most-adopted autonomous agent projects in the open-source ecosystem. The system runs on 200+ models via OpenRouter, Nous Portal, NVIDIA NIM, and others, with tool-based provider switching that requires zero code changes. Users can interact via a terminal interface or through Telegram, Discord, Slack, WhatsApp, or Signal — all from a single gateway process. Built-in cron scheduling enables fully unattended workflows, and the agent can spawn isolated subagents for parallel workstreams. What sets Hermes apart from typical agent frameworks is the memory layer: it captures observations via five session hooks, stores them in SQLite with FTS5 search, and uses a Chroma vector database for semantic retrieval — cutting context costs by ~10x versus naive approaches. The result is an agent that genuinely accumulates expertise over time rather than starting from scratch each session.

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.