[FEATURE] Skill-level permissions

[schrockn]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Skills are powerful, but using them with git worktrees is painful. I use tools that generate worktrees automatically and maintain a 1-to-1 ratio between worktrees and PRs, resulting in many worktrees with unique names.

Every time I create a new worktree, I'm prompted to approve each project skill:

Use skill "devrun-gt"?
 Claude may use instructions, code, or files from this Skill.
   Graphite (gt) command execution patterns, output parsing guidance, and special handling for gt CLI operations. (project)
 Do you want to proceed?
 ❯ 1. Yes
   2. Yes, and don't ask again for devrun-gt in /Users/schrockn/code/workstacks/workstack/new-plan-commands
   3. No, and tell Claude what to do differently (esc)

With multiple project-defined skills, this becomes repetitive across many worktrees with unique names. It's especially frustrating because many skills are just markdown files with no executable scripts and therefore perfectly safe.

Proposed Solution

Solution is to not require permissions for markdown-only skills and then add skills to the permissions system as well:

{
  "permissions": {
    "allow": [
      "Skill(devrun-gt)",
      "Skill(my-other-skill)"
    ]
  }
}

or allow all skllls

{
  "permissions": {
    "allow": [
      "Skill(*)",
    ]
  }
}

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[jasonkuhrt]

Our team needs this to, current workaround is to commit .local settings file, not good.