A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 16.5 · decisive
A · leads
97.4
112,653 stars · MIT
B
80.9
2,735 stars · MIT
Agent-Reach 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.4 for Agent-Reach and 80.9 for yao-meta-skill.
Agent-Reach has 112,653 GitHub stars to yao-meta-skill's 2,735, a gap of 109,918 (41.19×). Forks are 10,094 for Agent-Reach and 254 for yao-meta-skill. On the log scale used inside this pair, adoption is 100 versus 68, and the fork community is 100 versus 60.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 96 and 96; activity scores are 92 and 92.
Both Agent-Reach 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 Agent-Reach (112,653 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: Agent-Reach is open source, yao-meta-skill is open source.
Agent-Reach is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 40 points (100 vs 60), and the tightest is self-hosting at 0 points (100 vs 100).
Agent-Reach finishes ahead at 97.4 against yao-meta-skill at 80.9, a 16.5 point decisive 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 | Agent-Reach | yao-meta-skill |
|---|---|---|
| GitHub stars | 112,653 | 2,735 |
| Forks | 10,094 | 254 |
| Open issues | 133 | 3 |
| Adoption | 100 | 68 |
| Activity | 92 | 92 |
| Community | 100 | 60 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 80.9 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.
Agent-Reach has more GitHub stars: 112,653 versus 2,735 for yao-meta-skill. The gap is 109,918 stars.
yao-meta-skill was pushed more recently: 09 November 2026 versus 08 November 2026 for Agent-Reach. That is 1 days apart.
Yes. This catalog marks both Agent-Reach and yao-meta-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
Agent-Reach 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.
Agent-Reach scores 97.4 and yao-meta-skill scores 80.9. This page calls that a decisive lead for Agent-Reach.