Skip to main content
Guide10 min read·Updated September 14, 2026
🧩

How to Update, Disable and Remove Claude Code Skills (2026)

B

A. Frans

Published September 14, 2026

Agent SkillsClaude CodePluginsSkill ManagementTutorial

Installing a Claude Code skill takes one command. Getting rid of one takes a different command depending on where the skill came from, and the wrong choice either does nothing or wipes a plugin's data folder you meant to keep.

Two mistakes come up constantly. Deleting a folder under ~/.claude/skills/ to remove a plugin skill does nothing, because the plugin still loads it. Removing a whole marketplace to get rid of one skill takes every plugin from that marketplace with it. Both come from the same gap: skills in Claude Code have five possible origins, and each one has its own off switch.

This guide covers all of them, checked against the official Claude Code skills docs and the plugins reference as of September 2026 (Claude Code v2.1.270).

Step 1: work out where the skill came from

Everything else depends on this. Run /skills inside Claude Code. You can type to filter the list by name, description, or source, so the origin shows up without digging through folders.

OriginWhere it livesHow it's invokedDisableUpdateRemove
Personal~/.claude/skills/<name>/SKILL.md/nameFrontmatter or skillOverridesEdit or pull the filesDelete the folder
Project.claude/skills/<name>/SKILL.md in the repo/nameFrontmatter or skillOverridesEdit or pull the filesDelete the folder
PluginInside an installed plugin/plugin-name:skill-name/plugin disableclaude plugin updateclaude plugin uninstall
BundledShips with Claude Code/nameskillOverrides or disableBundledSkillsUpdates with Claude CodeCan only be hidden
Synced from claude.ai~/.claude/skills/synced//anthropic-skills:<name> when shadowedTurn it off on claude.aiSyncs automaticallyTurn it off on claude.ai
There's also an enterprise location inside the managed settings directory (for example /etc/claude-code/.claude/skills/ on Linux). If a skill lives there, only an administrator can remove it.

The namespace is the fastest tell. A skill that shows up as /superpowers:brainstorming came from a plugin. A bare /deploy is personal, project, or bundled.

Two more things /skills gives you. Press t to sort by token count, which is how you find the skill quietly eating context. And /context has a Skills row showing how much of your context window the skill listing takes after the budget is applied.

Step 2: disable a skill without deleting it

Disabling is the safer move when you're not sure you'll miss a skill. There are four levels, from lightest to heaviest.

Stop Claude from triggering it on its own

Add this to the skill's frontmatter:

---
name: deploy
description: Deploy the app to staging
disable-model-invocation: true
---

The skill disappears from Claude's context entirely. You can still run it by typing /deploy. Put this on anything with side effects (deploys, database migrations, sending messages). You should be the one who decides when those fire.

Don't confuse it with user-invocable: false. That hides the skill from your / menu but Claude can still call it. The docs are explicit that it doesn't stop Claude from invoking the skill.

Hide it without editing the file

Editing a SKILL.md that's checked into a team repo means a pull request for what is a personal preference. The skillOverrides setting exists for this. In /skills, highlight a skill, press Space to cycle its state, then Esc to save. Claude Code writes the result to .claude/settings.local.json, which stays on your machine.

ValueClaude sees itIn your / menu
"on"Name and descriptionYes
"name-only"Name onlyYes
"user-invocable-only"HiddenYes
"off"HiddenHidden
You can also write it by hand:
{
  "skillOverrides": {
    "legacy-context": "name-only",
    "deploy": "off"
  }
}

One catch trips people up: plugin skills ignore skillOverrides. The docs say so directly. If the skill has a plugin: prefix, skip to the plugin section below.

Block it with a permission rule

Permission rules are the hard stop. Add a deny rule through /permissions:

Skill(deploy *)

Skill(name) matches exactly, and Skill(name *) matches the skill with any arguments. A bare Skill deny rule blocks every skill at once, which is useful in a locked-down environment and miserable anywhere else.

Turn off a whole plugin

Inside a session:

/plugin disable superpowers@claude-plugins-official

From your shell:

claude plugin disable superpowers --scope user

You can also open /plugin, go to the Installed tab, and toggle it there. Under the hood this flips the plugin's entry in the enabledPlugins setting to false. Since a recent change, claude plugin disable refuses to run when another enabled plugin depends on the target, and prints the chain you'd need to disable instead.

Bundled skills

Claude Code ships its own skills. You can't uninstall them, but you can hide one with a skillOverrides entry set to "off", or hide all of them with "disableBundledSkills": true in settings (or the CLAUDE_CODE_DISABLE_BUNDLED_SKILLS=1 environment variable). Built-in commands like /init stay typable either way.

Step 3: update skills

Plugin skills

Most skills people install now arrive as plugins. Superpowers, for example, installs with /plugin install superpowers@claude-plugins-official according to its README. To update one plugin:

claude plugin update superpowers

Passing the bare plugin name works in current versions. Older builds needed the full plugin@marketplace form, so use that if the short one fails.

A plugin can only update to what its marketplace knows about. Refresh the marketplace first:

/plugin marketplace update claude-plugins-official

Leave the name off claude plugin marketplace update in your shell and it refreshes every marketplace you've added.

Auto-update

Open /plugin, go to Marketplaces, pick one, and choose Enable auto-update. Anthropic's official marketplace has auto-update on by default. Third-party and local marketplaces start with it off, which is the right default: a third-party update is new code from someone you've trusted once, and it deserves a look before it runs. If you've been auditing skills before installing them (our skill security audit guide walks through it), an auto-update skips that check for every future version.

Auto-updates run in the background within about 10 minutes of startup. When one lands, Claude Code prompts you to run /reload-plugins, or the new version loads on your next launch.

Personal and project skills

These are plain folders, so updating means changing the files. If you cloned a skill from GitHub into ~/.claude/skills/, a git pull inside that folder brings it up to date. The official docs don't prescribe a method here. What they do confirm is that Claude Code watches the skill directories and picks up changes to SKILL.md within the current session, without a restart.

Two exceptions to live reload:

  • If you create a top-level skills directory that didn't exist when the session started, restart so Claude Code can watch it.
  • For a skill folder that is also a plugin, changes to hooks/, .mcp.json, agents/, or output-styles/ need /reload-plugins.

Step 4: remove a skill for good

Personal or project

Delete the folder:

rm -rf ~/.claude/skills/old-skill

It drops out of /skills in the same session. Check both locations if a skill keeps reappearing, because a project copy in .claude/skills/ loads even after you delete the personal one. When both exist with the same name, the personal copy wins and the project copy stays hidden behind it, so deleting the personal one can look like it did nothing.

If you'd rather keep a way back, move the folder somewhere outside the skills directory instead of deleting it.

Plugin

claude plugin uninstall superpowers

The flags matter more than they look:

  • --keep-data preserves the plugin's persistent data folder (~/.claude/plugins/data/{id}/). Without it, the CLI deletes that folder when you uninstall from the last scope where the plugin is installed. The /plugin interface asks first; the CLI does not.
  • --prune removes dependencies that nothing else needs anymore. You can also run claude plugin prune later.
  • --scope user|project|local picks which install to remove when a plugin is installed in more than one place.

claude plugin remove and claude plugin rm are aliases for the same command.

Marketplace

/plugin marketplace remove some-marketplace

Read the warning in the docs before you run this: removing a marketplace from its last remaining scope also uninstalls every plugin you installed from it. Uninstall the single plugin instead if that's all you wanted gone.

Synced from claude.ai

Turn the skill off in your claude.ai account. Claude Code removes it from ~/.claude/skills/synced/ on the next sync. Deleting that folder by hand doesn't stick, because the next sync downloads it again while the skill is still enabled on claude.ai.

Why pruning skills is worth ten minutes

Every enabled skill puts its name and description into a listing Claude reads at the start of a session. By default that listing gets 1% of the context window, and each skill's description (plus its when_to_use text) is capped at 1,536 characters. When the listing overflows, Claude Code drops descriptions from the least-used skills first. Names always stay.

In practice, a pile of forgotten skills makes Claude worse at picking the right one, because the skill you care about may be listed as a bare name with no description to match against. If a skill you rely on has stopped triggering, check this before rewriting its description. Our guide to skills that won't trigger covers the other causes.

Three fixes, in the order worth trying them:

1. Disable or remove skills you haven't used in a month. /skill-doctor (v2.1.252 and later) shows each skill's context cost and how often it gets used, which makes this a quick call. 2. Set low-priority skills to "name-only" so they keep their slot without the description. 3. Raise the budget with "skillListingBudgetFraction": 0.02 in settings. This costs context on every session, so treat it as the last option.

For more on keeping sessions lean, see how to cut Claude Code token costs.

A monthly routine

Open /skills, sort by token count, and ask of each entry whether it fired in the last few weeks. Uninstall plugins you no longer use with --prune. Give personal skills you're unsure about disable-model-invocation: true for a month before deleting them, so a skill you did need comes back with one line. Anything that runs shell commands or touches production should stay manual-only for good.

It takes about ten minutes. The payoff is a skill listing short enough that Claude reads the descriptions that matter.

If you're building skills rather than removing them, Skill Creator from anthropics/skills is the official starting point, and our marketplace explainer covers how plugins get distributed. More developer tooling lives in our full list for developers.

FAQ

How do I see which skills are installed in Claude Code?

Run /skills. It lists every available skill, lets you filter by name, description, or source, and sorts by token count when you press t. Plugin skills show a plugin-name: prefix.

Why didn't deleting the skill folder remove the skill?

The skill probably came from a plugin, from claude.ai sync, or from a second copy in the project's .claude/skills/ directory. Plugin skills need claude plugin uninstall or /plugin disable. Synced skills have to be turned off on claude.ai, or the next sync downloads them again.

Can I disable a skill for myself without changing the team's repo?

Yes. Use skillOverrides through the /skills menu. It saves to .claude/settings.local.json, which is local to your machine, and leaves the shared SKILL.md untouched. This doesn't work for plugin skills.

Does uninstalling a plugin delete its data?

From the CLI, yes, when you uninstall from the last scope where the plugin is installed. Pass --keep-data to keep the persistent data folder. The /plugin interface shows the folder size and asks before deleting.

Do I need to restart Claude Code after changing a skill?

Not for edits to SKILL.md in personal, project, or --add-dir skill folders; Claude Code picks those up mid-session. Plugin changes apply after /reload-plugins or a restart, and a brand-new top-level skills directory needs a restart.

Share this article

📬

Get More AI Tool Guides

New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.