analyze-permissions

Analyze Claude permission entries and propose consolidated wildcard patterns.

127|21|Updated Jan 11, 2016
One-click install
npx skills add https://github.com/haacked/dotfiles --skill analyze-permissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-permissions
Source: https://github.com/haacked/dotfiles/tree/main/ai/skills/analyze-permissions
Command: npx skills add https://github.com/haacked/dotfiles --skill analyze-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This Skill helps manage and consolidate permission patterns across local and shared Claude configuration, reducing noise and improving safety.

Core Features & Use Cases

  • Analyze entries in settings.local.json and identify which are already covered by broader wildcards in settings.json
  • Propose consolidated wildcard patterns (e.g., Bash(kubectl:) or Bash(docker:)) to reduce redundancy
  • Produce a structured report with safety considerations and suggested actions for apply/cleanup

Quick Start

Use the analyze-permissions skill to read your local and shared configuration files and generate a report of potential consolidations.

Frequently Asked Questions about analyze-permissions

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

FAQPage Schema
How do I consolidate Claude permission patterns in settings.json?

Consolidate Claude permission patterns by cross-referencing local and shared JSON configuration files to identify redundant entries covered by broader wildcards, outputting a structured safety report with suggested cleanup actions.

What are safe wildcard patterns for Bash permissions?

Safe wildcard patterns for Bash permissions consolidate specific commands into broader prefixes like Bash(kubectl:*) or Bash(docker:*), reducing configuration noise while maintaining operational safety boundaries.

How do I identify redundant permission entries in settings.local.json?

Identify redundant permission entries by parsing settings.local.json with jq and cross-referencing its patterns against broader wildcards in settings.json to find entries already covered by existing rules.

Do I need jq to analyze permission files?

You need jq and a POSIX shell to analyze permission files, because the Skill parses JSON configuration data and cross-references wildcard patterns by executing jq queries within shell scripts.

Can I merge local and shared permission configurations automatically?

You cannot merge configurations automatically; the Skill analyzes local and shared permission files and outputs a structured report with proposed consolidation patterns and safety considerations for manual apply or cleanup.