Skip to content
DevUtils Online

Workflow Automation

nanobot vs yao-meta-skill

nanobot leads by 15.1 · decisive

A · leads

nanobot

97.9

50,147 stars · MIT

nanobot versus yao-meta-skill 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 82.8 for yao-meta-skill.

nanobot has 50,147 GitHub stars to yao-meta-skill's 2,735, a gap of 47,412 (18.34×). Forks are 8,755 for nanobot and 254 for yao-meta-skill. On the log scale used inside this pair, adoption is 100 versus 73, and the fork community is 100 versus 61.

Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.

Both nanobot and yao-meta-skill 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 Workflow Automation, both nanobot (50,147 stars) and yao-meta-skill (2,735 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, yao-meta-skill is open source.

The lead is split. nanobot is furthest ahead on fork community (100 to 61), while yao-meta-skill is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.

nanobot finishes ahead at 97.9 against yao-meta-skill at 82.8, a 15.1 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

nanobot versus yao-meta-skill metrics
Signal nanobot yao-meta-skill
GitHub stars 50,147 2,735
Forks 8,755 254
Open issues 872 3
Adoption 100 73
Activity 100 92
Community 100 61
Issue health 84 96
License 96 96
Self-hosting 100 100
Composite 97.9 82.8

yao-meta-skill

YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, nanobot or yao-meta-skill?

nanobot has more GitHub stars: 50,147 versus 2,735 for yao-meta-skill. The gap is 47,412 stars.

Which was updated more recently, nanobot or yao-meta-skill?

nanobot was pushed more recently: 17 November 2026 versus 09 November 2026 for yao-meta-skill. That is 8 days apart.

Can I self-host both nanobot and yao-meta-skill?

Yes. This catalog marks both nanobot and yao-meta-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, nanobot or yao-meta-skill?

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. yao-meta-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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the nanobot vs yao-meta-skill score?

nanobot scores 97.9 and yao-meta-skill scores 82.8. This page calls that a decisive lead for nanobot.

Related comparisons