Dojo
Section-level Agent Skills CLI and MCP server that streams only the context an agent needs
Why This Was Built
Agent Skills load as whole files, so an agent that needs one procedure pays for the entire document in context. The same skills also scatter across per-harness folders and separate machines, where they drift and are maintained by hand.
The Architectural Answer
Dojo indexes each skill's headings, streams a single section on demand, resolves dependencies in order, and bi-directionally reconciles the canonical .agents/skills store with every active harness. A linked personal registry carries the same skills between a laptop and a cloud VM.
Key Features & Architecture
Technical Specifications
- Primary Languages
- Go
- Frameworks & Tooling
- Go standard libraryyaml.v3
- Architecture & Execution Model
- Single static binary, stdio JSON-RPC 2.0 MCP server, BM25 plus reciprocal rank fusion search, digest-verified catalog cache
- Licensing Model
- Apache-2.0 (permissive)
- Release & Lineage
- Active release cycle since 2026 · Maintained by @JadMadi
Frequently Asked Questions
Do I need to rewrite my existing skills?
No. Dojo reads the standard SKILL.md format with YAML frontmatter, and `dojo sync` imports skills it finds in supported harness folders before projecting them back out.
Which coding agents does Dojo support?
Antigravity (Desktop and CLI), Claude Code, Cursor, Windsurf, OpenCode, and Sila, with .agents/skills as the canonical store.
What does the MCP server expose?
Eight tools: dojo_find, dojo_toc, dojo_load, dojo_run, dojo_learn, dojo_doctor, dojo_sync, and dojo_profile, all over stdio JSON-RPC 2.0.
Is Dojo related to KungFu?
Dojo began as a fork of the Apache-2.0 KungFu CLI by Daniela Petruzalek and is now independently maintained. Upstream credit is recorded in CREDITS.md.