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
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add rohitg00/pro-workflow --skill permission-tuner -a cursor -y
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.
name: permission-tuner
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.
user-invocable: true
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).
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
Symptom
Fix
Prompt on something you always approve
Remove or narrow the ask rule
permission-rule on a harmless command
Fix the hook false positive or narrow the deny rule
Classifier blocks work in your own repos, registries, local services
autoMode only takes effect in ~/.claude/settings.json, managed settings, or --settings. Keep "$defaults" in each list. Check the result with claude auto-mode config and review custom rules with claude auto-mode critique.
Always present changes for user approval before applying
Never write autoMode into project settings
Include estimated prompt savings
How do I install permission-tuner?
Download skills/permission-tuner/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does permission-tuner live?
The publisher keeps it at https://github.com/rohitg00/pro-workflow.
Which agents can use permission-tuner?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.