update-permissions

Update allow/deny command patterns in .claude/settings.json.

2|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/enbiyagoral/.claude --skill update-permissions-enbiyagoral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-permissions
Source: https://github.com/enbiyagoral/.claude/tree/main/.claude/skills/update-permissions
Command: npx skills add https://github.com/enbiyagoral/.claude --skill update-permissions-enbiyagoral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage command-level access by adding or removing permission entries in the .claude/settings.json file to enforce who can run what.

Core Features & Use Cases

  • Modify allow/deny lists for specific command patterns to enforce runtime security.
  • Validate patterns, warn about conflicts, and preserve existing settings for auditability.
  • Review current settings and apply policy changes with safe, document-backed updates.

Quick Start

Provide a permission change by stating allow kubectl delete *.

Frequently Asked Questions about update-permissions

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

FAQPage Schema
How do I manage command-level access permissions in .claude/settings.json?

Command-level access permissions are managed by updating the allow and deny lists in the .claude/settings.json file to enforce runtime security and control who can run what. The system validates patterns and warns about conflicts to preserve existing settings for auditability.

What is the best way to enforce allow and deny patterns for command execution?

The best way to enforce execution patterns is by applying precise allow and deny lists in the .claude/settings.json file. This approach validates wildcard usage, warns about conflicts, and ensures commands are checked against the policy before execution.

Can I use wildcard patterns when configuring access control in Claude settings?

Yes, wildcard patterns can be used when configuring access control in Claude settings. The system specifically validates pattern entries, including wildcard usage, to ensure the allow and deny rules in .claude/settings.json are correctly formatted and applied before execution.

How do I safely add or remove permission entries without losing existing settings?

To safely add or remove permission entries, the system applies document-backed updates to the .claude/settings.json file. This process validates the new allow and deny patterns, warns about potential conflicts, and preserves existing settings for auditability.

Does updating Claude permissions validate conflicting allow and deny rules?

Yes, updating Claude permissions validates conflicting allow and deny rules. When modifying the .claude/settings.json file, the system checks for pattern conflicts, validates wildcard usage, and ensures precise access control is enforced before command execution.