Feature request: enable/disable individual skills via settings.json and session flags

Currently, Claude Code reads all SKILL.md files found under .claude/skills/ and activates them based on their description: trigger. There is no way to toggle individual skills on or off without physically removing or renaming the file.

Proposed — persistent toggle in settings.json

{
  "disabledSkills": ["worktree-setup"]
}

This would allow teams to ship a set of skills in a repo but let individual developers or CI environments opt out of specific ones without modifying tracked files.

Proposed — session-scoped toggle via CLI flag

claude --disable-skill worktree-setup
claude --enable-skill worktree-setup  # re-enable one disabled in settings.json

Or as a slash command mid-session:

/skill disable worktree-setup
/skill enable worktree-setup
/skill list

Use cases

• A repo has 5 skills installed. A developer wants to disable one that conflicts with their workflow without removing it from the repo or touching .claude/skills/
• CI pipeline wants to run with a minimal skill set without modifying tracked files
• A developer temporarily disables a skill for one session while debugging, without affecting teammates