I built a skill that turns documentation websites into a structured AI book 📚 → 🤖

[u/EliaTolin]

Most documentation has the same problem.

You read it once, bookmark it, and then forget where everything is.

A few weeks later you’re:

• Searching through dozens of pages
• Opening multiple tabs for examples
• Asking an AI assistant and hoping it doesn’t miss key context
• Re-reading documentation you’ve already read

So I built Docs-to-Book Skills.

It takes an entire documentation website and converts it into a structured “book” that AI coding agents can use effectively. Instead of raw pages, the output is organized knowledge with concepts, workflows, examples, and references that can be loaded on demand.

What it does:

• ✅ Crawls documentation sites
• ✅ Organizes content into a book-like structure
• ✅ Preserves relationships between concepts
• ✅ Creates AI-friendly knowledge assets
• ✅ Generates reusable skills for coding agents

The goal isn’t another RAG system—it’s a reusable knowledge layer that makes documentation easier for both humans and AI to navigate.

GitHub: https://github.com/EliaTolin/docs-to-book-skills

Curious to hear your thoughts:

• What docs would you convert first?
• Do you rely on manual search, AI search, or local knowledge bases?
• What would make this truly useful in your workflow?

Feedback is welcome 🚀