Addy Osmani's agent-skills is an open-source collection of engineering workflows for AI coding agents. It helps an agent follow processes such as defining a change, planning small tasks, reviewing code and preparing a release. It is a skills package, not a new model or a standalone coding application.
Start with the official repository and Osmani's own introduction. The commands below come from its documentation. We have not installed the package or executed any of its skills.
Is it 24 or 25 skills?
On October 23, 2026, the repository contained 25 skills/<name>/SKILL.md files. Its README describes 24 lifecycle skills plus the using-agent-skills meta-skill, which helps select a workflow. The companion website still advertised 24 skills when checked, so a headline count alone is not a reliable version marker.
This guide uses the repository snapshot at commit aeac41d. Counts can change; browse the current catalog before installing. Similarly named skill collections from other GitHub owners are separate projects.
Pick a workflow for the problem you have
The pack covers more than writing code. These examples show how its documented skills divide the work:
| Your situation | Relevant skill | Purpose |
|---|---|---|
| The request is vague | interview-me |
Clarify requirements through questions |
| A change needs an agreed definition | spec-driven-development |
Write objectives, structure, constraints and acceptance expectations |
| A specification needs executable steps | planning-and-task-breakdown |
Divide work into small tasks with dependencies |
| A feature should be built in slices | incremental-implementation |
Work through small, verifiable changes |
| An error needs investigation | debugging-and-error-recovery |
Localize the failure before choosing a fix |
| Code needs review | code-review-and-quality |
Apply a structured review process |
| An API boundary needs design | api-and-interface-design |
Define contracts and error behavior |
| A release needs preparation | shipping-and-launch |
Follow the pack's release workflow |
These are instructions for the host agent to follow. Installing them does not demonstrate that the agent followed every step, that a test passed, or that a release is safe. Keep the scope and required evidence appropriate to your own project.
Browse or install with the skills CLI
The repository documents the open skills CLI as a cross-agent installation route. These are terminal commands; npx requires a working Node.js/npm environment and network access.
List the available skills before choosing:
npx skills add addyosmani/agent-skills --list
Install the collection through the CLI's host-selection flow:
npx skills add addyosmani/agent-skills
Or select one documented skill:
npx skills add addyosmani/agent-skills --skill code-review-and-quality
Review the destination and selected host before confirming an installation. Adding the Markdown skills through this route does not necessarily install the short lifecycle command wrappers. The repository documents host-specific integrations separately.
A single-skill copy can omit shared references
The README explicitly warns that a per-skill installation copies skills/<name>/ but does not bring along the repository-level references/ directory. Some supplementary checklist links can therefore be unavailable.
If your chosen workflow needs those checklists, use a whole-repository integration or retain a local repository checkout. The getting-started guide also describes copying needed material into a skill-local references/ directory. Inspect the referenced paths rather than assuming a one-folder copy contains every supporting document.
Install the native Claude Code plugin
For Claude Code, the official README documents a marketplace plugin. Enter these commands inside Claude Code, rather than in your system shell:
/plugin marketplace add addyosmani/agent-skills
/plugin install agent-skills@addy-agent-skills
If marketplace registration fails because GitHub SSH authentication is unavailable, the same README offers an HTTPS registration form:
/plugin marketplace add https://github.com/addyosmani/agent-skills.git
/plugin install agent-skills@addy-agent-skills
Choose the appropriate registration form; there is no need to add both. A marketplace registration and a plugin installation are separate operations. Confirm the plugin is available in the host before trying its commands.
The plugin supplies lifecycle entry points such as /spec, /plan, /build and /review. Where a host command has the same name, the README recommends the namespaced form, for example /agent-skills:review. Do not mistake the host's unrelated built-in command for the package workflow.
Other hosts use different discovery paths
The repository provides setup guides for Cursor, Codex, Gemini CLI, OpenCode, GitHub Copilot and other hosts. Its common core is Markdown, but installation folders, plugin metadata and command invocation differ.
For example, the README places Cursor skills under .cursor/skills/, with short policies in .cursor/rules/. OpenCode uses its own skill discovery locations. Copilot does not inherit Claude Code's short lifecycle wrappers merely because the underlying skills were copied. Follow the setup guide linked from the repository for your actual host and installed version; do not create a .claude/commands/ directory and expect every tool to read it.
The pack uses the MIT license. That license does not supply model access, tool credentials or infrastructure: your host's normal requirements and usage charges still apply.
Use it without importing the contributor setup
The official getting-started guide distinguishes the skill content from the repository's own contributor rules. Do not copy the package's root AGENTS.md or CLAUDE.md over your project's instructions. Those files configure work on agent-skills itself.
Use the host's skill discovery mechanism and invoke a relevant workflow for a bounded task. For instance: “Use code-review-and-quality to review this diff; report findings before editing.” This is an example request, not a result we obtained by running the pack.
If the host already discovers skills from their descriptions, the guide advises against also pasting the using-agent-skills router into an always-on prompt. Duplicating routing instructions can add unnecessary context and competing directions.
When installation appears to do nothing
- The short command is missing: check whether you installed skills only or a native plugin with command wrappers. Use the full skill name supported by your host.
- A checklist path cannot be opened: inspect whether a single-skill copy omitted the shared
references/directory. - Marketplace setup fails with an SSH public-key error: use the documented HTTPS marketplace URL and inspect the Git error before repeating installation.
- The wrong review command runs: select the package's namespaced command where the host supports it.
- The agent ignores the workflow: confirm that the host discovered the intended skill, then ask it to identify the workflow and expected outputs for the task. Installation alone is not proof of activation.
The source review establishes the documented structure and commands, not cross-host runtime compatibility or a measured improvement in code quality. No skills, model calls or review agents were executed for this article.