agent-skills
Production-grade engineering skills library for AI coding agents
Expert verdict
Ship
3-1The Panel's Take
agent-skills is a structured library of 20 production-grade engineering skills for AI coding agents, published by Addy Osmani (former Google Chrome DevTools lead, author of Essential JavaScript Design Patterns). It provides a complete spec-to-ship workflow via 7 slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship) that work across Claude Code, Cursor, Gemini CLI, Windsurf, and GitHub Copilot — any agent that supports CLAUDE.md or equivalent configuration files. The library includes three specialist personas that activate on demand: a security auditor (checks for injection vulnerabilities, hardcoded secrets, OWASP Top 10), a code reviewer (focuses on maintainability, complexity, and test coverage), and a test engineer (generates unit, integration, and edge-case tests). Four reference checklists (API design, accessibility, performance, deployment) give agents shared evaluation criteria. Each skill is written as a Markdown instruction file following the CLAUDE.md conventions popularized by the karpathy-skills library. agent-skills accumulated 6,693 GitHub stars in its first trending week, outpacing most comparable skill collections. Osmani's framing — treating agent skills as a first-class engineering asset rather than ad-hoc prompts — resonates with teams trying to standardize how they use AI coding tools. The library is MIT-licensed and designed to be forked and extended.
Share this verdict
agent-skills verdict: SHIP 🚀 3 ships · 1 skip from the expert panel Full review: shiporskip.io/tool/agent-skills-addyosmani-production-engineering-slash-commands-claude-cursor-2026
Weekly AI Tool Verdicts
Get the next verdict in your inbox
7 critics review a new AI tool every day. Weekly digest — free.
Similar Products
Compare agent-skills with Others
Looking for agent-skills alternatives?
Compare agent-skills with every other Developer Tools tool reviewed by our panel.
See all Developer Tools alternativesEmbed this verdict
Tool makers can add a live ShipOrSkip badge to their site. Badge loads track impressions; clicks route back to this review.
<a href="https://shiporskip.io/api/badge-click/agent-skills-addyosmani-production-engineering-slash-commands-claude-cursor-2026" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/agent-skills-addyosmani-production-engineering-slash-commands-claude-cursor-2026" alt="agent-skills Ship verdict on ShipOrSkip" width="360" height="90" /></a>[](https://shiporskip.io/api/badge-click/agent-skills-addyosmani-production-engineering-slash-commands-claude-cursor-2026)<iframe src="https://shiporskip.io/embed/agent-skills-addyosmani-production-engineering-slash-commands-claude-cursor-2026" title="agent-skills ShipOrSkip verdict" width="360" height="260" style="border:0;border-radius:16px;max-width:100%;" loading="lazy"></iframe>The reviews
“Having security audits, test generation, and spec creation as first-class slash commands changes how you think about agent-assisted development. The cross-tool compatibility (Claude, Cursor, Gemini) means you can standardize across a team with mixed tool preferences. Fork it, customize the checklists, and you have a company playbook.”
“This is well-packaged prompt engineering, not a fundamentally new capability. The value depends entirely on the underlying agent following instructions reliably — which varies wildly across tools and models. Teams that haven't established basic code review processes will use this as a crutch rather than building genuine engineering discipline.”
“The real innovation here is treating agent behavior as versionable, shareable code. The next step is organizations maintaining their own agent-skills forks as living engineering standards — the CLAUDE.md pattern is becoming a de facto org-level configuration layer for how teams interact with AI.”
“The /spec and /plan commands are genuinely useful for non-engineers who need to communicate feature requirements to an AI agent. Clear structured specs reduce the back-and-forth of vague prompts — this could be the bridge between product thinking and implementation.”