A · leads
graphify
97.9
149,362 stars · Apache-2.0
AI Agents
graphify leads by 2.1 · narrow
A · leads
97.9
149,362 stars · Apache-2.0
B
95.8
117,459 stars · MIT
graphify 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. graphify is written mainly in Python; taste-skill is written mainly in JavaScript. The composite score is 97.9 for graphify and 95.8 for taste-skill.
graphify has 149,362 GitHub stars to taste-skill's 117,459, a gap of 31,903 (1.27×). Forks are 14,362 for graphify and 7,858 for taste-skill. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 94.
Push history: graphify was last pushed on 16 November 2026 (1 day ago), and taste-skill was last pushed on 08 November 2026 (8 days ago). Open issues stand at 1,670 for graphify (0.011 per star) and 10 for taste-skill (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
graphify is listed as Apache-2.0, 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. License scores in this pair are 96 for graphify and 96 for taste-skill. This is a procurement signal, not legal advice.
In AI Agents, both graphify (149,362 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: graphify is open source, taste-skill is open source.
The lead is split. graphify is furthest ahead on recent activity (100 to 92), while taste-skill is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
graphify finishes ahead at 97.9 against taste-skill at 95.8, a 2.1 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 | graphify | taste-skill |
|---|---|---|
| GitHub stars | 149,362 | 117,459 |
| Forks | 14,362 | 7,858 |
| Open issues | 1,670 | 10 |
| Adoption | 100 | 98 |
| Activity | 100 | 92 |
| Community | 100 | 94 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 95.8 |
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
graphify has more GitHub stars: 149,362 versus 117,459 for taste-skill. The gap is 31,903 stars.
graphify was pushed more recently: 16 November 2026 versus 08 November 2026 for taste-skill. That is 7 days apart.
Yes. This catalog marks both graphify and taste-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
graphify is listed as Apache-2.0, 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.
graphify scores 97.9 and taste-skill scores 95.8. This page calls that a narrow lead for graphify.