A · leads
Huginn
96.2
50,561 stars · MIT
Workflow Automation
Huginn leads by 12.7 · clear
A · leads
96.2
50,561 stars · MIT
B
83.5
2,735 stars · MIT
Huginn 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. Huginn is written mainly in Ruby; yao-meta-skill is written mainly in Python. The composite score is 96.2 for Huginn and 83.5 for yao-meta-skill.
Huginn has 50,561 GitHub stars to yao-meta-skill's 2,735, a gap of 47,826 (18.49×). Forks are 4,356 for Huginn 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 66.
Push history: Huginn was last pushed on 09 November 2026 (8 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 692 for Huginn (0.014 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 84 and 96; activity scores are 92 and 92.
Both Huginn 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 Huginn (50,561 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: Huginn is open source, yao-meta-skill is open source.
The lead is split. Huginn is furthest ahead on fork community (100 to 66), while yao-meta-skill is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against yao-meta-skill at 83.5, a 12.7 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 | Huginn | yao-meta-skill |
|---|---|---|
| GitHub stars | 50,561 | 2,735 |
| Forks | 4,356 | 254 |
| Open issues | 692 | 3 |
| Adoption | 100 | 73 |
| Activity | 92 | 92 |
| Community | 100 | 66 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.2 | 83.5 |
Huginn is a self-hosted agent system that watches the web and triggers actions from events. It predates the current wave of LLM agents and is closer to a personal IFTTT you run yourself.
YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.
Huginn has more GitHub stars: 50,561 versus 2,735 for yao-meta-skill. The gap is 47,826 stars.
Both were last pushed on 09 November 2026.
Yes. This catalog marks both Huginn and yao-meta-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
Huginn 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.
Huginn scores 96.2 and yao-meta-skill scores 83.5. This page calls that a clear lead for Huginn.