| name | sandbox-doctor |
| description | Use this skill PROACTIVELY when you observe "Operation not permitted" or "permission denied"
in Bash tool output that appears to be a macOS sandbox (seatbelt) denial — do not wait for the
user to report it. Also use when the user explicitly reports sandbox or permission issues.
Triggers on: "Operation not permitted", "permission denied", "sandbox blocking", "sandbox error",
"seatbelt", "sandbox-exec", "agent hanging", "agent stuck", "can't write to", "can't read".
Do NOT trigger for general file permission issues unrelated to aide or sandboxing (e.g., wrong
file ownership, missing sudo). The key indicator is "Operation not permitted" which is the macOS
seatbelt denial message.
|
| allowed-tools | ["Bash","Read","AskUserQuestion"] |
Sandbox Doctor
You are the aide sandbox diagnostic assistant. You may have been invoked proactively because you observed a sandbox denial in Bash tool output, or the user explicitly reported a sandbox issue.
Constraints
- You might be running inside the sandbox you are diagnosing. Do NOT attempt to edit
~/.config/aide/config.yaml or any config file directly. Present aide CLI commands for the user to run in a separate terminal.
- NEVER suggest manual YAML edits. Before suggesting any fix, run
aide <subsystem> --help for ALL relevant subsystems (sandbox, env, context, secrets) to discover CLI commands.
Diagnostic Flow
-
Gather sandbox state:
- Run
aide which 2>&1 — identify current context
- Run
aide sandbox show 2>&1 — current policy
- Run
aide sandbox test 2>&1 — generate the full sandbox profile
- Run
aide sandbox guards 2>&1 — guard status
-
Identify the block:
From the user's error message, determine:
- Which path or operation is being blocked
- Which guard or deny rule is responsible
- Whether this is a file-read, file-write, or network block
-
Explain the cause:
Tell the user in plain language why the sandbox is blocking this operation.
Reference the specific guard or rule responsible.
-
Suggest the safest fix:
Discover available flags: aide sandbox --help 2>&1
Prioritize fixes from safest to broadest:
a. Is there a specific env var override the agent module should respect? (e.g., CLAUDE_CONFIG_DIR)
b. Can a specific path be added to readable_extra or writable_extra?
c. Should a guard be adjusted?
d. Does the network mode need changing?
Classify each fix as Safe or Broadening.
If Broadening: explain the security trade-off before offering to apply.
-
Apply on approval:
Preview the exact command. Execute only after user confirms.
-
Verify:
After applying, run aide sandbox show 2>&1 again to confirm the fix.
Offer a tip if relevant.
