[Feature Request] Add wildcard support for Skill permissions (Skill(*))
Resolved 💬 3 comments Opened Dec 28, 2025 by 0xnfrith Closed Jan 1, 2026
Bug Description
Feature Request: Skill(*) wildcard permission
Problem: Each skill in .claude/skills/ requires an individual permission entry like Skill(neon), Skill(stripe). For projects with many skills, this is tedious and must be updated whenever a new skill is added.
Request: Support wildcard pattern Skill() or Skill(*) in settings.json to auto-approve all project skills at once.
Example:
{
"permissions": {
"allow": ["Skill(*)"]
}
}
Rationale: Other permission types support wildcards (Bash(git:), Read(.claude/skills/*)). Skills should follow the same pattern for consistency.
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.0.76
- Feedback ID: 21d93f52-b4f1-4dbd-bd88-ccfc0d8d5fb5
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗