Disabled plugin still appears in available skills and can be invoked

[ChrisGamboa]

Bug

A plugin explicitly disabled in user-level settings (~/.claude/settings.json) is still listed in the available skills system reminder and can be invoked by the assistant.

Steps to Reproduce

1. Disable a plugin in ~/.claude/settings.json:

   {
     "enabledPlugins": {
       "code-review@claude-plugins-official": false
     }
   }

2. Start a conversation and ask for a code review.
3. The disabled code-review skill still appears in the <system-reminder> skills list.
4. The assistant invokes the skill despite it being disabled.

Expected Behavior

• Disabled plugins should not appear in the available skills list injected into system reminders.
• If a disabled skill is somehow invoked, the Skill tool should reject the call.

Actual Behavior

• The disabled plugin appears in the skills list as if it were enabled.
• The assistant invokes it without any guardrail preventing execution.

Notes

User-level settings should take precedence over project-level settings. The enabledPlugins: false directive at the user level was ignored entirely.

[github-actions]

Found 3 possible duplicate issues:

1. Plugin hooks (SessionStart) fire even when plugin is disabled in settings #41919
2. [BUG] Plugin enable/disable ignored - all skills loaded regardless of settings #13344
3. Cannot uninstall plugin: enabledPlugins false ignored, plugin re-installs every session #28554

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #41919.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.