// Blog
Blog
In-depth articles, tutorials and guides on software engineering topics.
// Blog
Blog
In-depth articles, tutorials and guides on software engineering topics.
TL;DR: Start Claude Code with claude, then type /plugin to browse plugins, or install one by name with /plugin install commit-commands@claude-plugins-official. Pick a scope, and Plugin is now active. means you are done. A skill someone shares with you is just a folder: copy it into ~/.claude/skills/ (on Windows, %USERPROFILE%\.claude\skills). Run any skill by typing / and its name.
The official docs put it simply: "Skills extend what Claude can do. Create a SKILL.md file with instructions, and Claude adds it to its toolkit." A skill is a folder with one SKILL.md file inside. That file has two parts:
--- markers at the top. The description says what the skill does and when to use it. Claude uses it to decide when to apply the skill.The folder name becomes the command you type. A skill in a folder called explain-code runs as /explain-code.
Claude Code always sees each skill's description, so it knows what is available. The full instructions only load when the skill is used. By default, both you and Claude can run any skill: you type /skill-name, or Claude loads it on its own when your request matches the description.
Two more things worth knowing:
.claude/commands/deploy.md and a skill at .claude/skills/deploy/SKILL.md both create /deploy and work the same way.Make a skill when you keep pasting the same instructions, checklist, or multi-step procedure into chat. Save it once, and run it whenever you need it.
It is also cheaper than stuffing everything into CLAUDE.md. In the docs' words: "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."
And if you use MCP: "MCP connects Claude to external services. Skills extend what Claude knows, including how to use those services effectively."
A plugin is a package. It bundles skills, hooks, subagents and MCP servers into a single installable unit. Most plugins come from a marketplace, which is a catalog that lists plugins and where to fetch each one.
Installing a plugin adds its skills (and its agents, hooks and MCP servers) to Claude Code on your machine. That is why installing a plugin is the easiest way to get skills. Plugin skills are namespaced with the plugin name, like /my-plugin:review, so several plugins can live side by side.
Open a terminal in your project and run:
claudeClaude Code adds Anthropic's official marketplace (claude-plugins-official) for you the first time you start an interactive terminal session.
To browse, type this at the Claude Code prompt:
/pluginThe panel opens on the Discover tab, which lists the plugins from your marketplaces. Type to search, then press Enter on a plugin to open its details.
Or install by name. This is the example from the official docs:
/plugin install commit-commands@claude-plugins-officialIt installs commit-commands from Anthropic's official marketplace, which adds commands for committing, pushing and opening pull requests. Inside a session, this command does not install right away: it opens the /plugin panel on that plugin's details so you can review it and choose a scope first.
Read the "Will install" pane first. It lists the commands, agents, skills, hooks, and MCP and LSP servers the plugin adds. The docs warn that a plugin you install "can execute arbitrary code on your machine with your user privileges", and that Anthropic does not review third-party marketplaces. Only install plugins you trust.
| Option in the panel | What it means |
|---|---|
| Install for you (user scope) | You get the plugin in every project on this machine |
| Install for all collaborators on this repository (project scope) | It is enabled for everyone who works in this repository |
| Install for you, in this repo only (local scope) | You get it in this repository only |
Plugin is now active. means you are done. No reload is needed.Run /reload-plugins to apply. means a reload is needed. The panel closes and Claude Code runs that reload for you.To confirm, type / and look for the plugin's skills in the form /<plugin>:<skill>. For commit-commands, /commit-commands:commit appears.
You can also install from your normal terminal (PowerShell, zsh, bash) without opening Claude Code:
claude plugin install <plugin>@<marketplace>On success it prints Successfully installed plugin: <plugin>@<marketplace>.
If someone shares a skill folder with you, copy the whole folder, with its SKILL.md inside, into one of these places:
| Where | Path | Works in |
|---|---|---|
| Personal (Mac / Linux) | ~/.claude/skills/<skill-name>/SKILL.md | All your projects on this machine |
| Personal (Windows) | %USERPROFILE%\.claude\skills\<skill-name>\SKILL.md | All your projects on this machine |
| Project | .claude/skills/<skill-name>/SKILL.md | Sessions in this repository |
On Windows, ~/.claude resolves to %USERPROFILE%\.claude. Paste %USERPROFILE%\.claude\skills into the File Explorer address bar to open the folder, then copy the skill folder in.
To share a skill with your team, put it in the project's .claude/skills/ folder and commit it to version control, so your team gets it too.
If the same skill name exists in both places, the personal one wins. With deploy in both ~/.claude/skills/ and the project's .claude/skills/, /deploy runs the personal one.
/ and pick the skill. Put its name at the start of your message. Folder skills use the folder name (/explain-code). Plugin skills use the plugin name, a colon, then the skill name (/commit-commands:commit)./skills. Type to filter the list by name, description or source. You can also ask Claude: What skills are available?Claude Code picks up skills you add, edit or remove under ~/.claude/skills/ or the project's .claude/skills/ within the current session, without a restart. One exception: if you create a top-level skills folder that did not exist when the session started, run /reload-skills to pick up the skills you put there.
On Mac or Linux:
mkdir -p ~/.claude/skills/explain-codeOn Windows, open %USERPROFILE%\.claude\skills in File Explorer and create a folder named explain-code there.
Create a file named SKILL.md in that folder. Here is our example:
---
description: Explains code in plain English. Use when the user asks what some code does.
---
Explain the code in three short bullet points.
Then show one small example of how to use it.The rules that matter:
--- must be the very first line of the file. Otherwise Claude Code treats the whole file, --- markers included, as skill content.description is recommended, so Claude knows when to use the skill.Test it two ways:
/explain-code.Want help testing a skill properly? The docs point to the skill-creator plugin: /plugin install skill-creator@claude-plugins-official.
On Windows (PowerShell):
The term '/plugin' is not recognized as the name of a cmdletOn Mac (zsh):
zsh: no such file or directory: /pluginYou typed /plugin at your normal terminal prompt. /plugin is a command you type inside a Claude Code session, not at the shell prompt. Run claude, then type /plugin at the Claude Code prompt. Or install straight from the terminal without starting a session:
claude plugin install <plugin>@<marketplace>Marketplace "claude-plugins-official" not foundThe official marketplace is not registered on this machine yet. Add it once, inside Claude Code:
/plugin marketplace add anthropics/claude-plugins-officialClaude Code prints Successfully added marketplace: claude-plugins-official. Then run your install again.
Plugin "commit-commands" not found in marketplace "claude-plugins-official"Your local copy of the marketplace catalog may be out of date. Refresh it, then retry the install:
/plugin marketplace update claude-plugins-officialStill not found? The name is the likeliest problem. Open /plugin, go to Discover, and copy the name from the list.
There is no error message for this one. Check, in order:
The file is named SKILL.md and sits inside its own folder, for example ~/.claude/skills/explain-code/SKILL.md.
The --- is on the very first line. If the frontmatter YAML is malformed, /skill-name still works but Claude cannot match against your description, so it never loads on its own.
You created a brand new skills folder during the session? Run /reload-skills.
Find SKILL.md files whose frontmatter does not parse (needs Claude Code v2.1.233 or later):
claude plugin validate .claude/skillsThat checks project skills. For personal skills:
claude plugin validate ~/.claude/skillsFollowing an old tutorial? The claude-code-plugins marketplace in anthropics/claude-code is deprecated. Skip any step that runs /plugin marketplace add anthropics/claude-code, and install from claude-plugins-official instead.
| Error | Fix |
|---|---|
Unknown command: /install | Use /plugin install <plugin>@<marketplace>. |
error: unknown command 'add' (after claude plugin add <source>) | claude plugin add is not a command. To add a marketplace, run /plugin marketplace add followed by its source inside a Claude Code session. |
/plugin isn't available in this environment. | You are in a non-interactive session, the desktop Code tab or the VS Code panel. Use that surface's own plugin UI. |
Plugin "<name>" not found in any marketplace | Name the marketplace: <plugin>@<marketplace>. |
Skill <name> requires bash (`shell: bash` in frontmatter) but Git Bash was not found | That skill needs Git Bash, which is missing on this Windows machine. |
| Personal skills disappeared | Look in ~/.claude/skills/.trash/. |
New step-by-step guides and coding tutorials, straight to your inbox.
Written by
AamerSoftware engineer and creator of Prograamer — practical tutorials on AI tools, AWS, web development, and career growth for software engineers.
Install the HyperFrames animation skill in Claude Code with two commands, type one prompt, render an MP4 on your own computer, then change it by asking. Plus what it can't do and what it really costs.
Read moreInstall Claude Code on Windows 10 or 11 with the official one-line installer, check it works, sign in, and fix the four errors people hit most.
Read moreMake videos with Claude Code for $0: create motion graphics from one prompt with HyperFrames, or cut your own footage with FFmpeg and local Whisper.
Read more