- Guides
- Tool guides
- Claude Code skills and plugins
Claude Code skills and plugins
A skill is a saved set of instructions Claude Code loads when it needs them. A plugin is a package of skills, agents, hooks and tool connections you install with one command. Start with one skill for the task you explain most often.
We have no affiliate deal with Anthropic or any plugin maker, and nobody paid to appear on this page.
What skills are
A skill is a folder with a SKILL.md file that tells Claude how to do one job. Claude uses it automatically when your request matches the skill's description, or you run it yourself by typing /skill-name 1. Anthropic's rule of thumb: make one when you keep pasting the same instructions, checklist or multi-step procedure into chat.
Skills differ from CLAUDE.md, the project file Claude reads in every session. CLAUDE.md loads in full every time; a skill's body loads only when it is used, so a long procedure costs almost nothing until you need it 1. Anthropic suggests keeping CLAUDE.md under 200 lines and moving workflows such as PR reviews or database migrations into skills 9 10.
Typical skills:
- A checklist: "review my diff and list the risks", run as
/summarize-changes. - A house style: your brand voice, banned words and formatting rules, applied whenever Claude writes copy.
- A procedure: "fix GitHub issue 1234", with the steps to read the issue, change the code, test and open a pull request 8.
Claude Code already ships some as built-in skills, including /code-review, /debug, /batch and /loop 1. The old custom commands in .claude/commands/ still work and now count as skills 1.
Not only Claude Code: skills follow the open Agent Skills standard, which works across several AI tools 1. In the Claude apps, skills are available on Free, Pro, Max, Ultra, Team and Enterprise, with code execution turned on 7. OpenAI's Codex has its own skills too 11.
What plugins are
A plugin is a bundle you install in one step. It can hold skills, subagents (helper agents Claude delegates to), hooks (scripts that run at set moments, such as after every edit) and MCP servers (connections to outside tools) 2.
You don't need a plugin for a single skill. A skill saved in your skills folder already works in every project 2. Plugins make sense when someone else has built a full setup you want, or when you want to hand your own setup to a team with updates.
Plugins come from marketplaces, which are catalogs in a GitHub repository. Claude Code adds Anthropic's official one, claude-plugins-official, the first time you start it in a terminal. Most of its plugins come from partners and tool vendors; Anthropic maintains a smaller set 4. You can browse it on the web at claude.com/marketplace or inside Claude Code with /plugin.
Know the cost: every enabled plugin adds its skill names and descriptions to each message, even when you don't use it, and that counts against your usage 2. Plugins in the official marketplace show a context-cost estimate before you install, and /usage shows what share of your usage each plugin, skill and MCP server took 3 9.
Installing a skill
There are three ways to add a skill: from a plugin, by copying a folder, or by syncing from claude.ai.
From a plugin
Most shared skills come inside plugins. In a Claude Code session, run the install command with the plugin name and marketplace; it opens a details pane so you can review what it adds before anything installs 3:
/plugin install commit-commands@claude-plugins-official
- ReviewThe pane lists the commands, agents, skills, hooks and servers the plugin adds 3.
- Choose a scope"Install for you" covers every project on this computer; project scope turns it on for everyone in the repository; local scope is you, in this repo only 3.
- CheckType
/and look for the new skills under the plugin's name, such as/commit-commands:commit3.
To browse instead, run /plugin with no name and use the Discover tab. In the desktop app, click + next to the prompt box and choose Add plugins 3. For a plugin from another marketplace, add that marketplace first, for example Anthropic's skills collection 4:
/plugin marketplace add anthropics/skills
By copying a folder
If someone shares a skill folder, put it in one of two places 1:
~/.claude/skills/<skill-name>/SKILL.mdfor you, in all projects.claude/skills/<skill-name>/SKILL.mdinside a project; commit it and your team gets it too
Claude Code notices new or edited skills in those folders during the session, with no restart 1.
Synced from claude.ai
Plugins you turn on for your claude.ai account, or that your organization turns on, sync into Claude Code when you sign in with that account. Run /skills to see which skills arrived 3 1.
Safety first: a plugin "can run code with your user privileges", and Anthropic does not review third-party marketplaces 2 4. A skill can also grant itself tool access through its allowed-tools field, so read that line in any skill you didn't write 1.
Writing your own skill
A skill is two parts: a short header that says when to use it, and plain instructions. Anthropic's own example creates a personal skill that summarizes your uncommitted changes. First make the folder 1:
mkdir -p ~/.claude/skills/summarize-changes
Then save this as ~/.claude/skills/summarize-changes/SKILL.md 1:
---
description: Summarizes uncommitted changes and flags anything risky. Use when the user asks what changed, wants a commit message, or asks to review their diff.
---
## Current changes
!`git diff HEAD`
## Instructions
Summarize the changes above in two or three bullet points, then list any risks you notice such as missing error handling, hardcoded values, or tests that need updating. If the diff is empty, say there are no uncommitted changes.
The line starting with ! runs a command and drops its output into the skill before Claude reads it. Test it by asking "What did I change?" or by typing /summarize-changes 1.
A skill for non-code work
The same format works for writing. Make a folder called brand-voice in your skills folder and give its SKILL.md a description such as "Use when writing any customer-facing copy", followed by your tone rules, banned words and two examples of copy you liked. We have recommended this pattern to readers since early 2026: package your brand guidelines once so Claude stops drifting into a generic AI voice.
Rules that make skills work
- Write the description for Claude: it decides when to load the skill from the description, and the description plus
when_to_useis cut off at 1,536 characters 1. - Keep
SKILL.mdunder 500 lines: move reference material into extra files in the same folder and link to them 1. - Pass details with
$ARGUMENTS: in a skill that says "Fix GitHub issue $ARGUMENTS", typing/fix-issue 123fills in 123 1. - Stop automatic use for risky jobs: add
disable-model-invocation: trueto anything with side effects, such as deploys, so it only runs when you type it 8. - Use a hook for must-run checks: skills and CLAUDE.md are guidance Claude can skip, while hooks run every time 8. A reader tip we shared in May 2026 made the same point about type checks: the skill alone will not always trigger.
Tip: turn good work into a skill right after it happens. One creator workflow we covered in July 2026 had Claude Code save each finished video edit as a skill, so the next video reused the same style. Anthropic's skill-creator plugin can draft, improve and test skills for you 6.
Plugins worth installing
Start with Anthropic's own plugins, then add the one integration you use daily. All of these are in the official claude-plugins-official marketplace; descriptions come from its catalog 6.
| Plugin | What it adds | Pick it if you |
|---|---|---|
| Code intelligence (e.g. typescript-lsp, pyright-lsp) | Type errors after each edit and go-to-definition 5 | work in a typed language |
| commit-commands | Commit, push and pull request commands | want git without typing git |
| code-review | Pull request review by several agents, with scoring to cut false alarms | review other people's PRs |
| feature-dev | Agents for exploring the codebase, designing and reviewing a feature | build features end to end |
| security-guidance | Security warnings and review of Claude-written code | ship anything public |
| frontend-design | Guidance for distinctive, production-grade interfaces | build web pages and apps |
| claude-md-management | Audits and updates your CLAUDE.md files | have a CLAUDE.md that grew long |
| skill-creator | Creates, improves and benchmarks skills | plan to write your own |
| github, linear, sentry, figma, notion, slack | Connections to those services | use that tool every day |
| playwright | Browser automation and end-to-end testing, by Microsoft | test web apps in a real browser |
For a typed language, Anthropic recommends a code intelligence plugin first: Claude finds code by symbol instead of reading whole files, which also saves usage. You install the language server separately, for TypeScript with npm install -g typescript-language-server typescript 5 9. Some of Anthropic's plugins, such as code-review and commit-commands, also sit in an older demo marketplace; install them from the official one so you don't end up with two copies 4.
Keep the list short. Two or three plugins you use beat ten that load into every message. The Installed tab in /plugin groups plugins you have not used recently, so you can turn them off 3.
Questions people ask
What is the difference between a skill and a plugin in Claude Code?
A skill is one set of instructions in a SKILL.md file. A plugin is an installable package that can hold several skills plus subagents, hooks and connections to outside tools.
Where do Claude Code skills go?
Personal skills go in ~/.claude/skills/ and work in every project on your computer. Project skills go in .claude/skills/ inside the repository, where you can commit them for your team.
How do I see which skills I have?
Type / in Claude Code to list commands and skills, including plugin skills under the plugin's name. /skills also shows skills synced from claude.ai.
Are Claude Code plugins safe?
Treat them like any software you install. A plugin runs code with your permissions, and Anthropic does not review third-party marketplaces, so read the details pane before installing and prefer the official marketplace.
Do skills work in the Claude app too?
Yes. Skills work in the Claude apps on every plan, including Free, when code execution is on, and they follow an open standard other AI tools also read.
Related
New features, explained the week they ship
195,000 readers get Uncover AI's practical AI briefing. We show you what is new and how to use it in your work.
Sources
- Claude Code skills
- Claude Code plugins overview
- Install and manage plugins
- Anthropic's plugin marketplaces
- Code intelligence plugins
- anthropics/claude-plugins-official on GitHub
- What are skills (Claude Help Center)
- Claude Code best practices
- Claude Code: manage costs effectively
- How Claude remembers your project
- Codex skills and plugins