claude-permissions-audit SKILL.md skillA
claude-permissions-audit from jackchuka/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jackchuka/skills/claude-permissions-audit@git:20260604.0da3398Pins git:20260604.0da3398 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jackchuka/skills
- Path
claude-permissions-audit/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260604.0da3398, committed Jun 4, 2026
- First version recorded
- Mar 11, 2026
- Size
- 5,662 bytes
- Repository stars
- 15
- License
- MIT
Review and reorganize Claude Code permission settings across all config files (global settings.json, project settings.local.json, dotfiles copies). Identifies redundancy, misplaced permissions, and lack of read/write organization. Produces a clean layout where global settings are the source of truth and project-local files only contain project-specific overrides. Use this skill whenever the user mentions reviewing permissions, cleaning up settings, auditing allowed tools, reorganizing…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Permissions Audit Review and reorganize Claude Code permission settings so global settings are the source of truth, project-local files stay minimal, and read vs write operations have clear separation. ## When to Use - Reviewing what tools and commands are pre-allowed - Cleaning up accumulated ad-hoc permission entries - After adding a new MCP server and deciding which operations to pre-allow - Ensuring global vs project-local settings are properly split - Periodic hygiene check on permission sprawl ## Phase 1: Discover All Settings Files Scan for every settings file that contributes to the effective permission set. **Locations to check:** - `~/.claude/settings.json` — global settings (source of truth) - `<project>/.claude/settings.json` — project shared settings (committed) - `<project>/.claude/settings.local.json` — project local settings (gitignored) - `~/.claude/.claude/settings.local.json` — home directory project local - Any dotfiles-managed copy (e.g. `home/.claude/settings.json` in a dotfiles repo) Read all of them in parallel. If a file doesn't exist, note it and move on. ## Phase 2: Audit For each permission entry across all files, assess: …
Read the whole file at its exact version.
How to install
mdr add jackchuka/skills/claude-permissions-audit@sha256:de4a4fd3e2a0cf5eThe line at the top of this page pins the label git:20260604.0da3398, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_y6k4tfksmshd7ttf)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 11, 2026 and Jun 4, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260604.0da3398 latest | 2026-06-04 | 0da3398 | 5,662 B | A | view · diff |
| git:20260421.19f33a5 | 2026-04-21 | 19f33a5 | 5,644 B | A | view · diff |
| git:20260321.fb3b945 | 2026-03-21 | fb3b945 | 5,631 B | A | view · diff |
| git:20260311.2835406 | 2026-03-11 | 2835406 | 5,606 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5662 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jackchuka/skills · 15 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y6k4tfksmshd7ttf GET https://markdownregistry.com/api/v1/resolve?ref=jackchuka/skills/claude-permissions-audit GET https://markdownregistry.com/api/v1/blob/de4a4fd3e2a0cf5eeb855ebe343f165d6b3871fe339da2b5ec66a089df6c3ff4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.