Three delivery modes share the same use cases and validation, so the choice is about your agent, not about capability — the skill file needs no protocol integration at all. distill_watch is the one worth knowing about: it returns the delta between two snapshots rather than both snapshots.
A Go tool with four operations, offered as a skill file, a CLI and an MCP server over stdio. It compresses command output against an explicit question, diffs two snapshots, distills raw payloads, and finds relevant repository code.
- distill_batch — full command output compressed down to answer one explicit question
- distill_watch — two consecutive snapshots compared, returning only the relevant delta
- distill_mcp_output — raw payloads distilled, or another tool called and its result distilled in one step
- search_code — relevant repository code located and returned as compact matches
- The same four operations reachable as a CLI subcommand or through a skill file, not only over MCP
- Provider configuration for Ollama or any OpenAI-compatible endpoint, with an interactive setup screen
Go 1.26 or later to build, or a prebuilt binary from the releases installer. Runs as an MCP server over stdio. You configure an LLM provider first — Ollama or an OpenAI-compatible endpoint — through the setup UI or a config file.
One command — curl -fsSL https://raw.githubusercontent.com/jcastilloa/context-distill/master/scripts/install.sh | sh