audit-permissions

Analyzes Claude Code credential files across projects for reuse and removal opportunities.

459|37|Updated Mar 29, 2019

Search Tags:#security #audit #permissions #Claude Code #json #scripts #global-config

Ready to run

npx skills add https://github.com/malob/nix-config --skill audit-permissions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-permissions
Source: https://github.com/malob/nix-config/tree/main/configs/claude/plugins/cc-maintenance/skills/audit-permissions
Command: npx skills add https://github.com/malob/nix-config --skill audit-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams audit and harmonize Claude Code permissions across multiple projects by identifying local, project-specific permissions that should be promoted to global configuration and by cleaning up redundancies.

Core Features & Use Cases

Discover project-local Claude Code permissions across repositories and aggregate them by project.
Identify redundant or risky local permissions that are now covered by global settings.
Promote safe permissions to global config and clean local permissions to maintain a minimal, accurate local-permissions baseline.
Use case: An engineering team wants to ensure consistent Claude Code permissions across dozens of services without manually reconciling each repo.

Quick Start

Run the discovery script to locate all settings.local.json files: ./scripts/discover-settings.sh
Generate an aggregated permissions report: ./scripts/extract-permissions.py <paths from discovery>
Clean redundant local permissions using the cleanup script: ./scripts/cleanup-redundant.py --apply

Frequently Asked Questions about audit-permissions

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

FAQPage Schema

How do I audit Claude Code permissions across multiple project settings files?▼

You can audit Claude Code permissions by running Python and shell scripts that discover local settings, parse JSON configurations, and aggregate permissions to identify redundancies and misconfigurations across repositories.

What is the best way to clean up redundant local permissions in Claude Code?▼

The best way to clean up redundant local permissions is to use a controlled workflow that compares project-local settings against global configuration, then applies targeted removals via a cleanup script.

How do I promote safe local Claude Code permissions to global config?▼

You promote safe permissions to global config by aggregating project-local settings into a report, validating them, and migrating the secure permissions to ensure consistent configuration across all services.

Can I identify misconfigurations in settings.local.json files across different repositories?▼

Yes, you can identify misconfigurations in settings.local.json files by executing a discovery shell script that locates all local configurations, followed by an extraction script that parses and validates the JSON permissions.

Does the Claude Code permissions audit workflow require any external dependencies?▼

No, the audit workflow relies entirely on built-in Python scripts and shell commands to parse JSON and discover settings, requiring no external dependencies to aggregate and validate permissions.