How to Disable Claude Skills
You can disable a Claude skill by turning it off in the Customize panel or removing it from a project. Here's what each option does, what persists afterward, and how to record why a skill was retired.
Updated 5 min read
To disable a Claude skill, open Customize, go to the Skills tab, find the skill, and toggle it off or choose Remove. Toggling off keeps the skill installed but stops Claude from using it in new chats. Removing it deletes the skill from your account. Both actions take effect immediately; they do not affect conversations that already used the skill.
Before you disable a skill, it is worth recording why — especially if other people rely on it or if the skill took time to build. Tools like fenbs can hold the approved version of the instructions and the reason it was retired, so the decision is clear to anyone who asks later.
Toggle off versus remove: which to use
Toggling a skill off is a pause. The skill stays in your account and can be re-enabled without reinstalling it. Use this when you are testing whether the skill is causing an issue, or when you want to stop it appearing in the skill picker temporarily.
Removing a skill deletes it. If the skill was created by someone else and shared with you, you can re-enable it through the sharing route; if you created it yourself, you would need to recreate it or restore from a saved copy. Remove a skill when it is genuinely no longer needed, not just inconvenient.
For Claude Code, personal skills live under ~/.claude/skills/ and project skills under .claude/skills/. Removing a project skill means deleting or moving the file; removing a personal skill means removing it from your personal skills folder. Check Claude Code's skills documentation (opens in a new tab) for the exact paths on your platform.
Understanding scope before you disable
A skill's scope determines where it is active. A personal skill applies to your account across projects. A project skill is attached to a specific Claude project and does not affect other projects. An organization-managed skill may be controlled by an admin rather than by you.
If a skill keeps reappearing after you disable it, check whether your organization has provisioned it centrally. In that case, disabling it on your account may have no effect; the setting lives with the organization owner. Ask your admin, or review Anthropic's organization skill management guide (opens in a new tab).
If you want to stop a skill applying in one project but keep it elsewhere, removing it from that project's skill list — rather than toggling it off account-wide — is the more precise action. Keep the scope match between what you disable and the problem you are solving.
What to check before disabling a shared skill
If the skill is shared with or used by colleagues, disabling it on your account affects only your own sessions. It does not remove it from theirs. If you are the owner of a skill that others use, discuss the retirement with them before removing it, because they may depend on its current instructions.
Check whether any active work depends on the skill. A task description that says "run the proposal review skill before submitting" becomes confusing if the skill is gone. Update task notes or project instructions to reflect the change before disabling.
| Action | Effect | When to use it |
|---|---|---|
| Toggle off in Customize | Skill stays installed; no longer appears in the skill picker | Temporary pause, troubleshooting, or testing without the skill |
| Remove from your account | Skill deleted from your account; you must reinstall to use it again | Skill is no longer needed and you do not want it in the picker |
| Remove from a project | Skill no longer active in that project; still available elsewhere | Skill should not run in one project but is still useful in others |
| Ask an org admin | Only option when the skill is provisioned centrally | Organization-managed skills that reappear after toggling |
Recording why a skill was disabled or retired
A skill that was useful once may be useful again. If you retire one because it was producing incorrect output, using an outdated prompt, or no longer matching a changed workflow, record that reason somewhere a future team member can find it.
The reason matters most when the skill had an approved version. "Retired on October 21, 2026: the proposal checklist changed and this version asked for the wrong inputs" is useful. "Deleted" is not. The next person who wants to rebuild a similar skill can avoid the same mistake.
Keep the reasoning behind a retired skill
When you disable a skill for a policy reason or retire an approved prompt, record the decision in fenbs Decisions and rules with the scope, date, and reason. Keep the last approved version of the instructions in Skills and prompts so the next revision has a clear starting point. Connected assistants read the rules first, so the gap the skill filled does not quietly reappear in a new prompt.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account, free for one person with no credit card, and add the project the skill belongs to.
- Before disabling the skill, copy its instructions and save them in Skills and prompts in fenbs with its purpose and any known limitations.
- Record the retirement as a decision in Decisions and rules: who decided, the date, the scope, and why.
- Update any task or project notes that referred to the skill so they reflect the current approach.
- If a replacement skill or prompt is planned, add it as a task so the work is tracked.
fenbs does not manage Claude skill settings for you. Disabling, removing, or restoring a skill still happens in Claude's own interface or in the skill files on your machine. What fenbs provides is a record of the reasoning that survives the change.
For examples of what a skill's instructions might contain, see Claude skills examples. For how to stop Claude from continuing a task it has already started, see how to stop a Claude Code task.