Skip to content
DevUtils Online

AI Agents

ECC vs taste-skill

ECC leads by 6.6 · narrow

A · leads

ECC

99.1

305,069 stars · MIT

ECC versus taste-skill is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in JavaScript. The composite score is 99.1 for ECC and 92.5 for taste-skill.

ECC has 305,069 GitHub stars to taste-skill's 117,459, a gap of 187,610 (2.60×). Forks are 44,923 for ECC and 7,858 for taste-skill. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 84.

Push history: ECC was last pushed on 17 November 2026 (0 days ago), and taste-skill was last pushed on 08 November 2026 (8 days ago). Open issues stand at 149 for ECC (0.000 per star) and 10 for taste-skill (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.

Both ECC and taste-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 AI Agents, both ECC (305,069 stars) and taste-skill (117,459 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: ECC is open source, taste-skill is open source.

ECC 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 16 points (100 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).

ECC finishes ahead at 99.1 against taste-skill at 92.5, a 6.6 point narrow 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.

ECC versus taste-skill metrics
Signal ECC taste-skill
GitHub stars 305,069 117,459
Forks 44,923 7,858
Open issues 149 10
Adoption 100 92
Activity 100 92
Community 100 84
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 99.1 92.5

ECC

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

Project site · GitHub · Full profile

taste-skill

Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, ECC or taste-skill?

ECC has more GitHub stars: 305,069 versus 117,459 for taste-skill. The gap is 187,610 stars.

Which was updated more recently, ECC or taste-skill?

ECC was pushed more recently: 17 November 2026 versus 08 November 2026 for taste-skill. That is 8 days apart.

Can I self-host both ECC and taste-skill?

Yes. This catalog marks both ECC and taste-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, ECC or taste-skill?

ECC 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. taste-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 ECC vs taste-skill score?

ECC scores 99.1 and taste-skill scores 92.5. This page calls that a narrow lead for ECC.

Related comparisons