Extend Claude with skills - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Skills extend what Claude can do. Create a SKILL.md file with instructions, and Claude adds it to its toolkit. Claude uses skills when relevant, or you can invoke one directly with /skill-name .
Create a skill when you keep pasting the same instructions, checklist, or multi-step procedure into chat, or when a section of CLAUDE.md has grown into a procedure rather than a fact. Unlike CLAUDE.md content, a skill’s body loads only when it’s used, so long reference material costs almost nothing until you need it. For built-in commands like /help and /compact , and bundled skills like /debug and /code-review , see the commands reference .
Custom commands have been merged into skills. Your existing .claude/commands/ files keep working. Claude can invoke them without you typing the command. Edit a command to stop Claude from invoking it on its own, or convert a command that needs more than one file to a skill: Stop Claude from invoking a command on its own : add disable-model-invocation: true to the command file’s frontmatter Add supporting files such as scripts : convert the command to a skill.
For example, move .claude/commands/deploy.md to .claude/skills/deploy/SKILL.md . The folder name becomes the command , so you still type /deploy . Claude Code skills follow the Agent Skills open standard, which works across multiple AI tools. Claude Code extends the standard with additional features like invocation control , subagent execution , and dynamic context injection . See Using skill frontmatter outside Claude Code for which frontmatter fields are part of the standard and which are Claude Code extensions.
Bundled skills Claude Code includes a set of bundled skills, such as /doctor , /code-review , /batch , /debug , /loop , and /claude-api . Bundled skills are prompt-based: they give Claude detailed instructions and let it orchestrate the work using its tools. Most built-in commands instead execute fixed logic directly. You invoke a bundled skill by typing / followed by the skill name. Claude invokes some bundled skills automatically when relevant.
Most bundled skills are available in every session. A few depend on a specific feature: /workflow-authoring , for example, is available only when dynamic workflows are enabled. To turn bundled skills off, use the disableBundledSkills setting. The /doctor setup checkup stays typable when disableBundledSkills is on. To hide it, set the DISABLE_DOCTOR_COMMAND environment variable or a skillOverrides entry of "doctor": "off" .
Bundled skills are listed alongside built-in commands in the commands reference , marked Skill in the Purpose column. Check your setup with /doctor Run /doctor at the Claude Code prompt for a setup checkup that diagnoses issues and can fix them. Claude reports its findings first and asks for confirmation before changing anything. The checkup covers these areas: Installation health : duplicate or leftover installs, PATH problems, unparseable settings files, and whether a newer version is available on your release channel Extensions : unused skills, MCP servers, and plugins compared with their context cost, and slow hooks CLAUDE.md files : local CLAUDE.md files that duplicate checked-in ones, checked-in CLAUDE.md content Claude could derive from the codebase , and the always-loaded guidance that remains, which Claude offers to migrate into skills and nested CLAUDE.md files that load on demand Permissions : an offer to make auto mode your default permission mode and to pre-approve read-only commands that you frequently deny Usage : on a Pro, Max, Ultra, Team, or Enterprise plan, the changes /usage recommends to lower your plan usage, measured over the last 7 days.
Claude proposes the changes it can make itself and reports the rest as advice, such as a command for you to run. The usage check requires Claude Code v2.1.305 or later, and /doctor leaves it out while Remote Control is connected. For read-only installation diagnostics without starting a session, run claude doctor in your terminal instead. To audit your instructions rather than your setup, run /doctor prompt-audit at the Claude Code prompt.
Claude checks your CLAUDE.md files, skills, and other configuration for outdated or conflicting instructions instead of running the checkup. The prompt-audit subcommand requires Claude Code v2.1.283 or later. Run and verify your app Three bundled skills work together to launch your app and confirm changes against the running app instead of tests alone: Skill Purpose /run Launch and drive your app to see a change working /verify Build and run your app to confirm a code change does what it should, without falling back to tests or type checks /run-skill-generator Teach /run and /verify how to build and launch your project /run and /verify work without setup.
They infer the launch from your project type (CLI, server, TUI, browser-driven) and from what’s in your README, package.json , or Makefile . That inference gets unreliable for projects that need anything beyond a standard launch: a database, an env file, a graphical session, a multi-step build. /run-skill-generator records the recipe instead. It gets your app running from a clean environment, captures what worked (the install commands, the env vars, the launch script), and commits it as a per-project skill at .claude/skills/run-<name>/ .
After that, /run , /verify , and any other agent in the repo follow the recorded recipe instead of rediscovering it. Run /run-skill-generator once per project, and again if the build or launch process changes. /verify can also record its own recipe. When it has to build and drive your app without a recorded recipe, it writes what worked to .claude/skills/verify/SKILL.md at the repo root, or in the touched package directory in a monorepo, so later runs and other agents follow the same steps.
At the repo root, the recorded skill replaces the bundled /verify . Claude edits the recorded file only when it steered a run wrong, such as a command that failed or a missing step, so you can commit the file without per-session diffs. Run your checks before each commit When a session starts with a skill named verify or simplify in place, Claude Code’s commit instructions tell Claude to run it right before each commit, except for changes to docs or tests.
This requires Claude Code v2.1.286 or later. Claude gets that instruction when these conditions hold at the start of the session: Location : the skill loads from the enterprise, personal, project, or additional-directory location , or from a .claude/commands/ file with that name. The recipe that /verify records at your repo root is a project skill, so it counts. The bundled /verify and /simplify , plugin skills, and skills from your claude.ai account don’t count.
Invocation : Claude can invoke the skill. If you’ve stopped Claude from invoking it , for example with disable-model-invocation: true , Claude doesn’t get the instruction. Git instructions : you haven’t turned off includeGitInstructions . Turning it off removes this instruction together with the rest of the built-in commit and PR instructions. Work on Claude API projects The bundled /claude-api skill loads Claude API and Managed Agents reference material for your project’s language.
Claude also activates it automatically when your code imports anthropic or @anthropic-ai/sdk . To start one of the skill’s workflows, type a subcommand after the skill name at the Claude Code prompt, for example /claude-api migrate . The table lists what each subcommand does and the earliest Claude Code version that includes it. migrate and managed-agents-onboard predate v2.1.221, the oldest version the table tracks.
Subcommand What it does Minimum version migrate Update your existing C
The rest of this page is on the live site.