fewer-permission-prompts — Reduce Permission Prompts

• Trigger: /fewer-permission-prompts or keywords "fewer prompts", "too many permissions", "allow list"
• Best for: Frequent operations blocked by permission dialogs, batch allowlisting
• Not for: Commands with uncertain safety, infrequent operations

Overview

fewer-permission-prompts scans your conversation transcripts for common read-only Bash and MCP tool calls, then adds a prioritized allowlist to .claude/settings.json to reduce unnecessary permission prompts.

Trigger Conditions

fewer-permission-prompts auto-triggers when you:

• Complain about too many permission prompts
• Use the /fewer-permission-prompts command

Examples

Example 1: Auto-Analysis

/fewer-permission-prompts

Claude will:

1. Scan recent conversation transcripts
2. Count request frequency per command/tool
3. Filter to read-only operations (safe to allow)
4. Generate prioritized allowlist suggestions
5. Write to settings.json after your confirmation

Example 2: Manual Add

/fewer-permission-prompts Allow npm test, npm run lint, and git status

Safety Principles

• Read-only only — Write, network, and destructive commands still require confirmation
• Least privilege — Allow specific commands, not wildcards
• Project-first — Prefer project-level config so other projects aren't affected

Notes

• Don't add destructive commands like rm, git push, npm publish
• Periodically audit the allowlist and remove stale entries
• Settings in .claude/settings.local.json should not be committed

Related Skills

• update-config — Manually configure permissions and other settings
• security-review — Audit project security configuration