# Permission Tuner

Analyze permission prompts and auto mode denials, then generate permission rules and...

- Repository: https://github.com/rohitg00/pro-workflow (2940 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-09-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rohitg00/pro-workflow --skill permission-tuner -g -a claude-code -y`
Codex: `npx skills add rohitg00/pro-workflow --skill permission-tuner -g -a codex -y`
Cursor: `npx skills add rohitg00/pro-workflow --skill permission-tuner -g -a cursor -y`
Gemini CLI: `npx skills add rohitg00/pro-workflow --skill permission-tuner -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rohitg00/pro-workflow`

## Description

Analyze permission prompts and auto mode denials, then generate permission rules and autoMode entries that cut prompt fatigue. Use when prompts keep interrupting, auto mode falls back to prompting, or after sessions with many denials.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Permission Tuner

Reduce permission prompts by fixing their causes, not by piling up rules.

## Trigger

Use when:
- Permission prompts interrupt flow repeatedly
- Auto mode keeps blocking routine work or falls back to prompting everything
- Starting a new project and want to configure permissions

## How Prompts Happen

- Rules resolve first: deny > ask > allow. A matching ask rule prompts even in auto mode, and a PreToolUse hook returning `allow` cannot override it.
- In auto mode, anything no rule resolves goes to a classifier. After 3 blocks in a row or 20 in a session, auto mode pauses and prompts for everything until you approve one.
- Auto mode drops broad allow rules: `Bash(*)`, wildcarded interpreters like `Bash(node *)`, package-manager run commands, `Agent`, and `Monitor`.
- Hooks that exit 2 on harmless commands count as denials and push the session toward that fallback.

## Workflow

### Step 1: Gather data

Rules merge across scopes, so check every file that exists, not only the user file. `/permissions` shows the rules Claude Code actually loaded, and `claude auto-mode config` shows the effective `autoMode` (the classifier ignores `autoMode` in `.claude/settings.local.json`).

```bash
for f in ~/.claude/settings.json .claude/settings.json .claude/settings.local.json; do
  [ -f "$f" ] && jq --arg f "$f" '{file: $f, mode: .permissions.defaultMode, allow: (.permissions.allow|length), ask: (.permissions.ask|length), deny: (.permissions.deny|length), autoMode: (.autoMode != null)}' "$f"
done
claude auto-mode config
ls -t ~/.claude/projects/*/*.jsonl | head -20 | xargs grep -ho '"toolDenialKind":"[^"]*"' | sort | uniq -c | sort -rn
```

`toolDenialKind` values seen in transcripts (undocumented, may change): `permission-rule` (rule or hook), `automode-blocked` (classifier), `automode-parsing-error` and `automode-unavailable` (no verdict, not tunable), `user-rejected` (you said no).

### Step 2: Pick the right fix

The rest: https://github.com/rohitg00/pro-workflow/blob/HEAD/skills/permission-tuner/SKILL.md