A
book-to-skill
90.9
38,245 stars · MIT
AI Agents
Open WebUI leads by 8.2 · clear
A
90.9
38,245 stars · MIT
B · leads
99.1
158,922 stars · MIT
book-to-skill versus Open WebUI is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. book-to-skill is written mainly in Python; Open WebUI is written mainly in Svelte. The composite score is 90.9 for book-to-skill and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to book-to-skill's 38,245, a gap of 120,677 (4.16×). Forks are 4,066 for book-to-skill and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 83 versus 100.
Push history: book-to-skill was last pushed on 08 November 2026 (8 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 37 for book-to-skill (0.001 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 96 and 96; activity scores are 92 and 100.
Both book-to-skill and Open WebUI are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both book-to-skill (38,245 stars) and Open WebUI (158,922 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: book-to-skill is open source, Open WebUI is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 17 points (83 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against book-to-skill at 90.9, a 8.2 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | book-to-skill | Open WebUI |
|---|---|---|
| GitHub stars | 38,245 | 158,922 |
| Forks | 4,066 | 23,097 |
| Open issues | 37 | 208 |
| Adoption | 88 | 100 |
| Activity | 92 | 100 |
| Community | 83 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 99.1 |
Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work.
Open WebUI is a self-hosted chat interface for local and remote language models, including Ollama. It adds users, documents, and tools around the model endpoint.
Open WebUI has more GitHub stars: 158,922 versus 38,245 for book-to-skill. The gap is 120,677 stars.
Open WebUI was pushed more recently: 17 November 2026 versus 08 November 2026 for book-to-skill. That is 8 days apart.
Yes. This catalog marks both book-to-skill and Open WebUI as self-hostable. Confirm each project's deploy docs before you plan a migration.
book-to-skill is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Open WebUI is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Open WebUI scores 99.1 and book-to-skill scores 90.9. This page calls that a clear lead for Open WebUI.