A · leads
edict
89.9
17,077 stars · MIT
Workflow Automation
edict leads by 2.6 · narrow
A · leads
89.9
17,077 stars · MIT
B
87.3
2,735 stars · MIT
edict 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 89.9 for edict and 87.3 for yao-meta-skill.
edict has 17,077 GitHub stars to yao-meta-skill's 2,735, a gap of 14,342 (6.24×). Forks are 1,771 for edict and 254 for yao-meta-skill. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 74.
Push history: edict was last pushed on 28 September 2026 (50 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 15 for edict (0.001 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 96 and 96; activity scores are 58 and 92.
Both edict 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 edict (17,077 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: edict is open source, yao-meta-skill is open source.
The lead is split. edict is furthest ahead on fork community (100 to 74), while yao-meta-skill is furthest ahead on recent activity (92 to 58). Choose the dimension a rollout cannot compromise on.
edict finishes ahead at 89.9 against yao-meta-skill at 87.3, a 2.6 point narrow 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 | edict | yao-meta-skill |
|---|---|---|
| GitHub stars | 17,077 | 2,735 |
| Forks | 1,771 | 254 |
| Open issues | 15 | 3 |
| Adoption | 100 | 81 |
| Activity | 58 | 92 |
| Community | 100 | 74 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.9 | 87.3 |
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails
YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.
edict has more GitHub stars: 17,077 versus 2,735 for yao-meta-skill. The gap is 14,342 stars.
yao-meta-skill was pushed more recently: 09 November 2026 versus 28 September 2026 for edict. That is 42 days apart.
Yes. This catalog marks both edict and yao-meta-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
edict 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.
edict scores 89.9 and yao-meta-skill scores 87.3. This page calls that a narrow lead for edict.