Latitude for Claude Code vs Skrun

Latitude is an observability platform specifically tuned for Claude Code usage. It captures every turn an agent runs — the prompts, tool calls, bash output, files touched, system prompt, and the tool schemas Claude Code composes at runtime — then surfaces it as cost breakdowns per prompt, per session, and per workspace. The platform routes Claude Code traffic through Latitude's instrumentation layer, giving engineering teams real visibility into what their AI coding agent is actually doing versus what they expect it to do. Teams can trace expensive tool-call chains, spot runaway loops, identify which slash-commands are budget-efficient, and attribute costs to specific tasks or repos without wading through raw OpenTelemetry traces. In a world where Claude Code rate limits and API costs are a real engineering budget concern, Latitude fills a genuine observability gap. It launched on Product Hunt today with 150 votes and complements Claude Code's native OpenTelemetry support by adding a human-readable interface and cost attribution dashboard that raw traces simply don't give you.

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.