claude-permissions

Automate Claude Code permission-rule configuration in .claude/settings.local.json.

23|3|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/Esposter/Esposter --skill claude-permissions-esposter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-permissions
Source: https://github.com/Esposter/Esposter/tree/main/.agents/skills/claude-permissions
Command: npx skills add https://github.com/Esposter/Esposter --skill claude-permissions-esposter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Claude Code permission-rule configurations for the .claude/settings.local.json file to reduce prompts and misconfigurations.

Core Features & Use Cases

  • Defines deterministic rule formats (Tool or Tool(specifier)) and evaluation order (deny → ask → allow).
  • Ensures Bash and PowerShell compatibility by using explicit rules for colon sub-scripts and common command families.
  • Use case: apply and debug permission rules when editing settings.local.json to control allow/deny/ask behavior.

Quick Start

Update your .claude/settings.local.json to follow the Tool(pattern) format and add explicit rules for colon sub-scripts as needed.

Frequently Asked Questions about claude-permissions

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

FAQPage Schema
How do I configure Claude Code permission rules in settings.local.json?▼

To configure Claude Code permission rules, update your .claude/settings.local.json file using the deterministic Tool or Tool(specifier) format to standardize prompt handling and reduce misconfigurations.

What is the evaluation order for allow, deny, and ask permission rules?▼

The evaluation order for permission rules is deny, then ask, then allow. This ensures explicit denials take precedence over subsequent ask or allow decisions during Claude Code execution.

How do I handle permission rules for Bash and PowerShell environments?▼

For Bash and PowerShell compatibility, apply explicit rules for colon sub-scripts and common command families. This ensures deterministic permission handling across both shell environments.

Why do I need explicit per-sub-script coverage for permission rules?▼

Explicit per-sub-script coverage is required to prevent unintended prompt behavior. Standardizing rule formats ensures that specific sub-scripts are properly allowed, denied, or prompted before execution.

Can I use wildcard semantics for Claude Code permission settings?▼

Claude Code permission settings support wildcard semantics within the Tool(specifier) format, allowing you to standardize broad command family permissions while maintaining strict deny to ask to allow evaluation order.