book-to-skill vs ragflow
ragflow is much bigger: 92.5k stars against 35.4k. Over the days we have tracked them book-to-skill moved +14.8% and ragflow +7.9%, so book-to-skill is growing faster right now.
book-to-skill leads on setup ease. ragflow does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Converts books and document collections into cross-agent, on-demand 'skills' with per-chapter files so agents answer from real content without dumping entire books into context.
- Stars
- 35.4k
- Tracked growth
- +14.8%
- Maturity
- ●●●●●
- Last commit
- 1d ago
- Language
- Python
- License
- MIT
- Cost to run
- Free, local processing; external model API costs apply
Combines a production-grade RAG engine with agent orchestration and template-based document understanding to provide an agentic context layer for LLMs.
- Stars
- 92.5k
- Tracked growth
- +7.9%
- Maturity
- ●●●●●
- Last commit
- 12m ago
- Language
- Go
- License
- Apache-2.0
- Cost to run
- Your API key (paid LLMs); self-host or use cloud
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | book-to-skill | ragflow |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Whole-skill access | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Validation & rules | ●●●●● Re-ranking & citations |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config file + options | ●●●●● Config files & templates |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Local processing | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● BYO model | ●●●●● Bring-your-own key |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command install | ●●●●● Multi-service deploy |
Which one to pick
Pick book-to-skill if…
Privacy-first — processes documents locally into compact, on-demand agent skills to avoid hallucination and reduce token/token-costs when querying.
- Setup ease: One-command install (4/5 against 1/5)
Pick ragflow if…
Self-hostable — choose RAGFlow when you need a production-ready, agentic RAG platform with template-based ingestion, grounded citations, and configurable LLM/embedding providers.
What people want from each one
virgiliojr94/book-to-skill
- PDF: `pdftotext -layout` interleaves columns on multi-column documents, and the word-based token estimate hides the 26x size blowup 👍 0
- [bug] Interrupted-run reuse accepts missing or corrupted extracted text 👍 0
- [bug] BeautifulSoup HTML/EPUB extraction inserts newlines inside inline headings and code tokens 👍 0
infiniflow/ragflow
Hacker News: RAGFlow is an open-source RAG engine based on OCR and document parsing drew 230 points and 53 comments.
Questions people ask
Is book-to-skill better than ragflow?
book-to-skill leads on setup ease. ragflow does not take any axis by a clear margin. book-to-skill is worth picking when privacy-first — processes documents locally into compact, on-demand agent skills to avoid hallucination and reduce token/token-costs when querying.
Which of book-to-skill and ragflow keeps my code private?
book-to-skill: Local processing (5/5). ragflow: Self-hostable (4/5).
What does each one cost to run?
book-to-skill: Free, local processing; external model API costs apply. ragflow: Your API key (paid LLMs); self-host or use cloud.
Full profiles: virgiliojr94/book-to-skill and infiniflow/ragflow. Everything else in RAG & retrieval.