A
book-to-skill
88.6
38,245 stars · MIT
AI Agents
ECC leads by 10.5 · clear
A
88.6
38,245 stars · MIT
B · leads
99.1
305,069 stars · MIT
book-to-skill versus ECC 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; ECC is written mainly in JavaScript. The composite score is 88.6 for book-to-skill and 99.1 for ECC.
ECC has 305,069 GitHub stars to book-to-skill's 38,245, a gap of 266,824 (7.98×). Forks are 4,066 for book-to-skill and 44,923 for ECC. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 78 versus 100.
Push history: book-to-skill was last pushed on 08 November 2026 (8 days ago), and ECC was last pushed on 17 November 2026 (0 days ago). Open issues stand at 37 for book-to-skill (0.001 per star) and 149 for ECC (0.000 per star). Issue-health scores are 96 and 96; activity scores are 92 and 100.
Both book-to-skill and ECC 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 ECC (305,069 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, ECC is open source.
ECC 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 22 points (78 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against book-to-skill at 88.6, a 10.5 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 | ECC |
|---|---|---|
| GitHub stars | 38,245 | 305,069 |
| Forks | 4,066 | 44,923 |
| Open issues | 37 | 149 |
| Adoption | 84 | 100 |
| Activity | 92 | 100 |
| Community | 78 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 99.1 |
Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
ECC has more GitHub stars: 305,069 versus 38,245 for book-to-skill. The gap is 266,824 stars.
ECC 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 ECC 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. ECC 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.
ECC scores 99.1 and book-to-skill scores 88.6. This page calls that a clear lead for ECC.