Skill comparison
Compare agent skills before installing.
Comparing 4 skills
Use this as a shortlist, then open the skill detail page before adopting.
Decision summary
To Tickets is the strongest overall pick here because it has a 100/100 readiness score and fits GitHub automation.
Strongest overall
To Tickets
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Fastest prototype
To Tickets
Best first install candidate based on install readiness and adoption.
Freshest repo
Vercel React Best Practices
Most recent maintenance signal among this shortlist.
| Signal | mneme Architectural governance for this project. Use this skill when the user asks about project decisions, architectural constraints, or wants to enforce / record / review decisions. Also use whenever Claude Code is about to make a non-trivial edit and the project has a `.mneme/` directory — check relevant decisions first. | Vercel React Best Practices React and Next.js performance guidance for writing, reviewing, and refactoring production UI code. | Code Review Review a branch or diff against repository standards and the originating spec in two independent analysis passes. | To Tickets Break a plan, spec, or conversation into independently actionable tracer-bullet tickets with explicit blocking relationships. |
|---|---|---|---|---|
| Quality | 59/100 Promising | 100/100 Excellent | 100/100 Excellent | 100/100 Excellent |
| Decision verdict | 58/100 Prototype first Prototype with this skill first; keep a fallback candidate ready. | 100/100 Production-ready Use this as a leading candidate, then validate the README and install path in your own agent stack. | 100/100 Production-ready Use this as a leading candidate, then validate the README and install path in your own agent stack. | 100/100 Production-ready Use this as a leading candidate, then validate the README and install path in your own agent stack. |
| Adoption | 17 stars Verified outcomes are shown on each skill page | 30K stars Verified outcomes are shown on each skill page | 169K stars Verified outcomes are shown on each skill page | 177K stars Verified outcomes are shown on each skill page |
| Freshness | Aug 21, 2026 | Aug 23, 2026 | Jul 13, 2026 | Jul 17, 2026 |
| Use-case fit | ||||
| Workflow fit | ||||
| Platform hints | Claude Code | Codex, Claude Code, Cursor, React, Next.js | Claude Code, Codex, Cursor, OpenAI Agents | Claude Code, Codex, Cursor, OpenAI Agents |
| Warnings | Low GitHub adoption signal · No OpenAgentSkill engagement data yet | No OpenAgentSkill engagement data yet | No OpenAgentSkill engagement data yet | May write local files or publish multiple issues and labels to an external tracker. · No OpenAgentSkill engagement data yet |
| Best for | Coding agents workflows · Claude Code teams · builders willing to evaluate younger projects | Browser automation workflows · Claude Code teams · teams that value GitHub adoption signals | Coding agents workflows · Claude Code teams · teams that value GitHub adoption signals | GitHub automation workflows · Claude Code teams · teams that value GitHub adoption signals |
| Not ideal for | teams that need a vendor-supported SLA · production agents without a repository review | teams that need a vendor-supported SLA · high-compliance environments without internal security review | teams that need a vendor-supported SLA · high-compliance environments without internal security review | teams that need a vendor-supported SLA · production agents without a repository review |
| OpenAgentSkill engagement | 0 views 0 install copies | 0 views 0 install copies | 0 views 0 install copies | 0 views 0 install copies |
| Install | $ npx skills add MnemeHQ/mneme --skill mneme | $ npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices | $ npx skills add mattpocock/skills --skill code-review | $ npx skills add mattpocock/skills --skill to-tickets |