AI tool comparison
agent-skills vs Claude How To
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
agent-skills
Production-grade engineering skills library for AI coding agents
75%
Panel ship
—
Community
Free
Entry
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.
Developer Tools
Claude How To
The missing practical guide to mastering Claude Code
75%
Panel ship
—
Community
Free
Entry
Claude How To fills the gap between Anthropic's feature documentation and what developers actually need to build real workflows with Claude Code. Where official docs describe what features exist, this repository shows how to combine slash commands, memory, subagents, hooks, and MCP servers into automated pipelines for code review, deployment, and documentation generation. The guide contains 10 tutorial modules with Mermaid diagrams, copy-paste configuration templates, and a progressive learning roadmap totaling 11–13 hours of structured content. Each module includes interactive self-assessment quizzes, and the entire guide is actively maintained to track Claude Code releases—currently synced to v2.2.0. Over 25 hook event types are documented with working examples, and there's a complete CLI reference for headless automation in CI/CD pipelines. Built by luongnv89 and released with an MIT license, Claude How To climbed to 18k stars in its first week—mostly organically through HN and X shares from developers frustrated with scattered official documentation. It represents the kind of community-built learning infrastructure that often outlasts the tools it documents.
Reviewer scorecard
“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.”
“The hook event documentation alone is worth bookmarking—25+ events with working examples is something the official docs simply don't have. The CLI headless automation reference for CI/CD is genuinely useful and hard to find elsewhere.”
“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.”
“Community documentation guides have a well-documented half-life: they go stale fast and create confusion when they drift from the actual tool behavior. The promise to 'sync with every Claude Code release' is optimistic given it's a one-person side project. Anthropic's own docs will eventually improve, making this redundant.”
“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 fact that a community guide to using an AI tool hit 18k stars in a week tells you everything about the documentation debt the AI industry has accumulated. Claude How To is a symptom of a real problem—and a useful one while the official ecosystem catches up.”
“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.”
“The structured learning path with time estimates is a thoughtful design choice—most technical guides dump everything on you at once. Knowing upfront that advanced MCP configuration takes 5 hours lets you plan your learning rather than falling into a rabbit hole.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.