permission-tuner

Analyzes permission denial patterns and generates alwaysAllow and alwaysDeny rules for Claude settings.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill permission-tuner-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permission-tuner
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/permission-tuner
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill permission-tuner-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repeated permission prompts interrupt your workflow and slow down AI-assisted sessions. This Skill analyzes which tools and commands you approve or deny most often and generates targeted permission rules so safe operations run without prompts while dangerous ones stay blocked. ## Core Features & Use Cases - Pattern Analysis: Scans current permission settings in .claude/settings.json and ~/.claude/settings.json to identify frequently approved tools. - Risk-Tiered Rule Generation: Groups rules into safe allow-list candidates (Read, Glob, Grep, read-only git commands), medium-risk ask candidates (Edit, Write, git commit), and high-risk deny candidates (rm -rf, git push --force, git reset --hard). - Approval-First Workflow: Presents all proposed rules for user review before applying them, with an estimate of prompts saved per session. - Use Case: After a long coding session where you manually approved dozens of git status and npm test prompts, run this Skill to auto-approve those read-only and test commands while keeping destructive operations blocked. ## Quick Start Ask the assistant to analyze my recent permission approvals and generate optimized allow and deny rules for my Claude settings.

Frequently Asked Questions about permission-tuner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce permission prompts in Claude Code?

Analyze which tools you approve most often, then add safe read-only operations like Read, Glob, Grep, and git status to the allow list in .claude/settings.json. Keep destructive commands like rm -rf and git push --force in the deny list.

What commands are safe to auto-approve in Claude settings?

Read-only operations are safe candidates: Read, Glob, Grep, git status, git diff, git log, npm test, npm run lint, and npm run typecheck. These have no side effects on files or remote systems.

Which commands should stay in the deny list?

Keep destructive and irreversible commands denied: rm -rf, git push --force, git reset --hard, and any command using --force or --no-verify. These can delete data or overwrite remote history without recovery.

Does the permission tuner apply rules automatically?

No. The Skill presents all recommended rules grouped by risk level for your review first. Rules are only applied after you explicitly approve them, and destructive operations always remain in the deny list.

Where are Claude permission rules stored?

Permission rules live in the permissions section of .claude/settings.json at the project level and ~/.claude/settings.json at the user level. The Skill checks both files when analyzing your current configuration.