Audit Permissions
- 42 installs
- 1 repo stars
- Updated May 26, 2026
- camacho/ai-skills
audit-permissions is a Claude skill that analyzes permission audit logs and recommends safe allow-list changes to reduce permission prompts.
About
This skill analyzes Claude Code permission audit logs and recommends allow-list changes to reduce permission prompts. It runs a TypeScript analyzer, presents a report, and offers to merge only safe patterns into permissions.allow while never modifying permissions.deny. It also flags security warnings and suppresses recommendations that carry danger-level flags. A developer uses it when reviewing how often they get prompted and optimizing the allow-list. It matters because it tightens permission configuration without silently approving risky commands.
- Analyzes permission audit logs and recommends allow-list changes
- Report and reset modes, with security warnings and suppressed dangerous recommendations
- Merges safe rules into permissions.allow without touching permissions.deny
Audit Permissions by the numbers
- 42 all-time installs (skills.sh)
- Ranked #1,398 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
audit-permissions capabilities & compatibility
- Capabilities
- permission audit · security audit · config review
- Use cases
- security audit
What audit-permissions says it does
Analyze permission audit logs and recommend allow-list changes.
Never touch keys outside `permissions.allow`. Never touch `permissions.deny`.
npx skills add https://github.com/camacho/ai-skills --skill audit-permissionsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 42 |
|---|---|
| repo stars | ★ 1 |
| Last updated | May 26, 2026 |
| Repository | camacho/ai-skills ↗ |
What it does
Analyze Claude permission audit logs and recommend safe allow-list additions while flagging dangerous patterns.
Who is it for?
Users of the ai-env setup who want to reduce permission prompts by tuning permissions.allow safely
Skip if: Projects without the ai-env repo and permission-audit hook, which will hit file-not-found errors
When should I use this skill?
reviewing permission prompt frequency, optimizing the allow-list, or resetting the audit log
What you get
Safe allow-list additions merged into permissions.allow with dangerous patterns flagged and suppressed
- permission audit report
- recommended safe allow-list rules
By the numbers
- 2 modes (report, reset)
- safe rules merged only into permissions.allow
Files
Audit Permissions
Analyze permission audit logs and recommend allow-list changes. Wraps the TypeScript analyzer in ai-env.
Args Routing
- No args / empty: run report (default)
- Args contain "reset" or "clear": archive log and start fresh
Report Mode (default)
1. Generate Report
node --import tsx /Users/patrickcamacho/projects/camacho/ai-env/src/tools/permission-analyzer.tsPresent the full markdown output to the user.
2. Recommended Allow Rules
If the section has entries:
1. Read ~/.claude/settings.json, extract permissions.allow (default []) 2. Compute new patterns not already present (case-sensitive exact match) 3. Show before/after diff of ONLY permissions.allow 4. Ask: "Apply these N safe rules to settings.json?" (plain text y/n — works on all surfaces) 5. If approved: merge, deduplicate, sort alphabetically, write back with 2-space indent 6. Never touch keys outside permissions.allow. Never touch permissions.deny. 7. Confirm what was added
3. Security Warnings
If present: show each pattern with flags and sample commands. Ask: "Add any of these despite the flags? (list numbers, or 'none')"
4. Suppressed Recommendations
List for awareness. Do NOT offer to add — these have danger-level flags.
Done
Summarize: what was added, how many permission prompts should be reduced.
Reset Mode
/Users/patrickcamacho/projects/camacho/ai-env/.claude/hooks/audit-permissions-reset.shFresh log starts automatically on next tool call.
Prerequisites
| Requirement | Check |
|---|---|
| ai-env repo | /Users/patrickcamacho/projects/camacho/ai-env exists (ai-env specific — other projects will see file-not-found errors) |
| Dependencies | pnpm install completed in ai-env |
| Audit hook | permission-audit-log.sh in ~/.claude/settings.json PreToolUse |
Troubleshooting
| Symptom | Fix |
|---|---|
| "No audit data found" | Hook not installed or no un-allowed prompts recorded yet |
| Analyzer crashes | Run pnpm install in ai-env repo |
| Stale recommendations | /audit-permissions reset, accumulate fresh data, re-run |
| settings.json parse error | Validate: jq . ~/.claude/settings.json |
Related skills
Entra App RegistrationCorrectly register an application in Microsoft Entra ID, configure OAuth 2.0 flows, request the right API permissions, and generate working MSAL authentication snippets484k1.3kAzure ComplianceRun automated Azure compliance scans, security posture checks, and Key Vault expiration audits before deploying.484k1.3k
Openclaw Secure Linux CloudDeploy and harden an OpenClaw agent instance on a Linux cloud server following battle-tested security defaults.270k72
Better Auth Best PracticesCorrectly configure Better Auth for secure authentication with database adapters, sessions, OAuth, email/password, and plugins in TypeScript projects.80.9k206
Firebase Security Rules AuditorAutomatically audit Firebase Firestore security rules for bypass vulnerabilities and logic gaps before deploying.80.4k397
Audit WebsiteRun comprehensive audits that surface SEO, performance, security, technical, and content issues with LLM-optimized reports and health scores.65.6k85FAQ
Does it touch permissions.deny?
No. It only merges safe patterns into permissions.allow and never touches permissions.deny or other keys.
What happens to dangerous patterns?
They are shown as security warnings or suppressed if they carry danger-level flags, never added automatically.