Config permit
Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.
npx -y skills add JasonWarrenUK/goblin-mode --skill config-permitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
{{ 𝚫𝚫𝚫 }} Grant a permission rule globally or for the current project
SKILL.md
1.7 KB, as published. Nobody here has run it
Add the permission rule to permissions.allow at the requested scope. Replaces the former config-permit-global / config-permit-project pair; the JSON handling lives in a script so the array append, dedupe and sync are one deterministic command — do not hand-edit the settings files as a fallback.
Steps
-
Both arguments are required. If
$scopeis notglobalorproject, or$ruleis empty, ask rather than guessing — a permission grant is not a place for inference. -
Run:
python3 ~/.claude/library/scripts/config_permit.py $scope "$rule"- global edits
~/.claude/settings.local.jsonc(comments preserved) and runs the settings-sync hook automatically. - project edits
.claude/settings.local.jsonin the current project, creating it if absent.
- global edits
-
Report the script's output verbatim: added, already present, or the error. On exit 2, surface the message and stop — if the script could not find the
allowarray, tell the user the file needs a look rather than editing it yourself.