Skillbooks are just Markdown directories served over HTTP. No proprietary SDK. No platform dependency. The format is designed to work everywhere.
View the Spec on GitHub →The root SKILL.md is a normal skill file. Any agent gets a working skill from it — no special tooling required. Agents that understand the graph follow links, pay per page, and get deep knowledge. SKILL.md can be listed on every existing marketplace — no ecosystem changes needed. This is progressive enhancement for agent skills.
Any agent can read SKILL.md as a standard skill file. Zero integration effort. It just works.
Graph-aware agents follow links into deeper sections. They navigate the knowledge structure and read only what they need.
Full traversal with micropayments and citations. The agent reads deeply, cites every source, and the creator gets paid.
The entire format is built on things that already exist: Markdown, HTTP, and JSON. No new protocols to learn.
Frontmatter with name, description, and metadata. Table of contents with links to every section. Navigation instructions that tell agents how to traverse the graph.
Machine-readable metadata: title, author, version, page count, price. Everything an agent or marketplace needs to index and display the skillbook.
Markdown files, 40–100 lines each. One concept per page. Cross-references link related topics. Every claim cites its source.
Relative links between pages. Agents follow the graph like browsing documentation. No routing layer, no query language — just links.
Skillbooks are HTTP resources. If your tool can fetch a URL, it can use a skillbook.
The skillbook format is developed in the open. Every improvement starts as a conversation.
Open an issue on GitHub to propose format changes, new metadata fields, or tooling improvements.
Fork the spec repo, make your modifications, and submit a pull request. All contributions are reviewed by maintainers.
Join open issues to discuss direction, trade-offs, and priorities. The best ideas come from real-world usage.
Every book ever written is potential inventory. The format is designed to make conversion easy and lock-in impossible.
The goal is a format that outlives any single platform. Markdown + HTTP + micropayments. That's the whole stack.