permitcrab

Review permitcrab permissions: blocks for anti-patterns - overly broad regexes, missing anchors, permissions declared but no body step requires them. Use when the user asks to audit, lint, or validate permissions, review a skill's permissions block, or check a plugin for over-permissioned or unnecessary permission declarations.

Diagnose permitcrab install health - script presence, version drift, hook wiring, common misconfigurations. Use when permitcrab isn't working as expected, the user asks to debug, troubleshoot, verify, or validate permitcrab, after upgrading the plugin, or to check status of a fresh install. Read-only; reports issues but does not fix them.

Install or reinstall permitcrab's runtime scripts to ~/.permitcrab/ so other plugins can reference them via a stable path. Use when the user asks to install, reinstall, fix, repair, or bootstrap permitcrab, or after a plugin upgrade. Idempotent. Distinct from permitcrab:setup, which declares permissions in a target SKILL.md.

Test harness invoked by permitcrab:setup to verify that a candidate permissions block produces the intended approve / passthrough / deny outcomes. Replays each case in test-plan.json against the same resolver script that the live PermissionRequest hook runs, passing this skill's own directory as the resolver's explicit skill-dir argument. Not for general use; setup writes the test plan and permissions block into this skill before invoking it.

Use when the user asks to set up permissions for a system, repo, plugin, or skill, when they want to whitelist or allowlist a command, auto-approve a tool call, tighten or narrow existing permissions, or stop being prompted about something a skill always does. Distinct from permitcrab:install, which sets up the plugin itself.

3 hooks across 3 events