Can I delete a plugin-managed skill file?

You can delete the file, but the plugin will likely reinstall it on its next run or update. If the plugin behavior depends on that skill, deleting it may break the plugin. Disable or remove the plugin first if you no longer want the skill.

What if the plugin skill conflicts with my instructions?

Add your instructions in a separate skill with a different name. When both are active in a session, Claude applies both. If they conflict, the result depends on the order of activation and how the instructions are worded. Consider whether you need the plugin skill at all, or whether disabling the plugin removes the conflict.

How do I know which plugin locked a specific skill?

In Claude Code, check the .claude/commands/ folder for the file and look at its creation timestamp and content for clues. Check which MCP servers or plugins you have installed and their documentation for the skill files they manage. In Claude.ai, check the list of connected integrations in account settings.

Will fenbs skills override a plugin-managed skill?

fenbs skills are read by the connected assistant as part of the session context. They do not override a plugin skill but run alongside it. The assistant combines both sets of instructions. If you want one to take precedence, state that explicitly in your fenbs skill text.

Claude Skills Locked by a Plugin: What to Check

What to do when a Claude skill is managed by a plugin, where you can safely make edits, and how to keep your intended instructions accessible in fenbs.

June 15, 2026Updated October 21, 20265 min read

When a Claude skill is locked by a plugin, it means the plugin installed or manages that skill file and the Claude interface prevents direct editing through the standard skill settings. The skill is still active and readable; the lock prevents accidental changes to instructions that the plugin depends on. fenbs keeps the instructions you actually want applied in a separate Skills and prompts entry that any connected assistant can read, so a locked plugin skill does not leave you without a working set of instructions.

Plugin-managed skill files appear most often in Claude Code, where MCP servers and extensions can install command files in the .claude/commands/ folder or manage project-level instructions. In Claude.ai, a skill added by an integrated third-party service may show as read-only. The lock is not an error; it is expected behavior for skills the plugin is responsible for maintaining.

Find the skill file the plugin manages

In Claude Code, plugin-managed skill files typically live in the .claude/commands/ folder of your project. Open that folder and look for files you did not create. The filename matches the slash command name. Read the file to understand what the plugin installed: it may be a review step, a code generation template or an integration-specific workflow.

In Claude.ai, a locked skill in a Project settings panel was added by a connected integration. Check the list of connected apps in your Claude.ai account settings to identify which integration added it. The app's own settings or documentation will describe what the skill does and whether it can be customized.

For more on how skill files work in Claude Code, see claude skills files. For broader plugin behavior in Claude Code, see claude code plugins and the comparison in claude code plugins vs skills vs subagents.

Where you can make changes

Even when a skill file is locked, there are usually places to add your own instructions. In Claude Code, create a separate command file in .claude/commands/ with a different name. Your command file is yours to edit; the plugin-managed file is not. If the plugin's skill and your skill cover overlapping territory, activate them in the right order or combine your instructions into a follow-up prompt.

In Claude.ai, you can add your own skills to a Project alongside any integration-managed ones. Add a new skill in the Project settings with a different name. Both skills are active in conversations within that Project. If the plugin skill produces output you want to supplement or override, your skill can provide additional or corrective instructions.

Check whether the plugin or integration offers a configuration file or settings panel for customizing its managed skill. Many plugins expose a configuration layer specifically for this purpose rather than expecting users to edit the skill file directly.

When not to edit the plugin skill file

Even if you can technically edit a plugin-managed skill file outside the Claude interface, doing so can cause problems. The plugin may overwrite your changes on its next update or sync. Conflicting instructions between the plugin's original intent and your edits can produce confusing behavior. If you need the plugin skill to behave differently, contact the plugin author or check the plugin's configuration options rather than editing the file directly.

If you need a permanent record of the instructions you intended, keep them somewhere the plugin cannot overwrite. That is exactly what fenbs Skills and prompts is for: your approved instruction text lives there, and any connected assistant reads it at the start of each session regardless of what a plugin manages.

How fenbs helps

Keep your intended instructions in fenbs

When a plugin manages a skill file and you cannot edit it directly, store the instructions you want to apply in fenbs Skills and prompts. A connected assistant reads your fenbs skills at the start of each session alongside any plugin-managed skills. If a plugin update overwrites a file you relied on, your fenbs record is unaffected. Record customization decisions in Decisions and rules so the next person knows what was intentional.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

How to track what each plugin manages

Keep a short record of which plugins manage which skill files, and what each one does. When a session produces unexpected behavior, that record tells you where to look first. A plugin skill that interacts with a skill you wrote can produce results that are hard to debug without knowing which instruction came from where.

Treat a plugin-managed skill as you would treat a dependency: note its version, check the plugin documentation when something changes, and test after updates. An update to the plugin can change the skill content without any action on your part.

How to do this with fenbs

Create a free account and add a project for the work where plugin skills are active.
Add the instructions you want to apply -- the ones you cannot put in the locked skill file -- to fenbs Skills and prompts with a clear name.
Connect Claude Code or Claude.ai to fenbs over MCP from /integrations. The connected assistant reads your fenbs skills at the start of each session.
Record which plugin manages which skill in Decisions and rules: the plugin name, the skill file path, and what the skill does. This is the record you reach for when a session behaves unexpectedly after a plugin update.
After a plugin update, check the managed skill file for changes. Update your fenbs record if the content changed significantly.

When the lock is unexpected

If a skill you created yourself is showing as locked and you do not know which plugin is managing it, check for recently installed plugins or extensions. An MCP server you added may have written a skill file with the same name as one you created. Check the plugin's documentation to confirm whether it writes skill files and which paths it uses. See claude skills not showing up for related troubleshooting steps, and how to create a Claude skill for how to create skills that are clearly yours.