A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 14.8 · clear
A · leads
97.9
50,147 stars · MIT
B
83.1
3,827 stars · Apache-2.0
nanobot versus Vibe-Skills is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.9 for nanobot and 83.1 for Vibe-Skills.
nanobot has 50,147 GitHub stars to Vibe-Skills's 3,827, a gap of 46,320 (13.10×). Forks are 8,755 for nanobot and 344 for Vibe-Skills. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 64.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and Vibe-Skills was last pushed on 09 November 2026 (8 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 46 for Vibe-Skills (0.012 per star). Issue-health scores are 84 and 84; activity scores are 100 and 92.
nanobot 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. Vibe-Skills is listed as Apache-2.0, 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. License scores in this pair are 96 for nanobot and 96 for Vibe-Skills. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and Vibe-Skills (3,827 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: nanobot is open source, Vibe-Skills is open source.
nanobot 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 36 points (100 vs 64), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against Vibe-Skills at 83.1, a 14.8 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 | nanobot | Vibe-Skills |
|---|---|---|
| GitHub stars | 50,147 | 3,827 |
| Forks | 8,755 | 344 |
| Open issues | 872 | 46 |
| Adoption | 100 | 76 |
| Activity | 100 | 92 |
| Community | 100 | 64 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 83.1 |
Your lightweight open-source personal agent.
Intelligent Skill routing and workflow orchestration for AI agents — +21.12 pp reward, −29.6% tokens on SkillsBench with DeepSeekV4Flash-VE.
nanobot has more GitHub stars: 50,147 versus 3,827 for Vibe-Skills. The gap is 46,320 stars.
nanobot was pushed more recently: 17 November 2026 versus 09 November 2026 for Vibe-Skills. That is 8 days apart.
Yes. This catalog marks both nanobot and Vibe-Skills as self-hostable. Confirm each project's deploy docs before you plan a migration.
nanobot 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. Vibe-Skills is listed as Apache-2.0, 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.
nanobot scores 97.9 and Vibe-Skills scores 83.1. This page calls that a clear lead for nanobot.