[FEATURE] Allow users to disable built-in skills

Problem

Built-in skills (like /commit-push-pr) cannot be disabled by users. When users have custom plugins that implement the same functionality with project-specific preferences (commit message style, GitHub labels, PR templates, etc.), the built-in skills create confusion and conflict. There's no way to opt out of built-in skills that overlap with custom plugin skills.

Proposed solution

Add a configuration option (e.g., in settings.json or .claude/settings.json) that allows users to disable specific built-in skills by name. For example:

{
  "disabledSkills": ["commit-push-pr"]
}

Disabled skills would not appear in the skill list and would not be invocable via /skill-name.

Alternatives considered

• Naming custom skills to shadow built-in ones — but built-in skills still show up and can be accidentally invoked
• Ignoring built-in skills manually — error-prone and adds cognitive overhead when multiple similar skills exist

Priority

Medium

Category

Configuration and settings