القائمة
Diagnose nono sandbox denials and choose safe remediation when Goose is running inside nono.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose and resolve permission denials when opencode runs inside a nono security sandbox. Use this when a tool call, shell command, or file operation fails with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors, or when an outbound network request fails because the host is not on the sandbox allowlist (connection refused, timeout, or proxy/TLS errors).
Diagnose and resolve permission denials when Codex runs inside a nono security sandbox. Use this when a Bash command, apply_patch, or MCP tool fails with "sandbox-exec: sandbox_apply: Operation not permitted", "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied output. Do not merely report the failure: explain it is a nono OS sandbox boundary, avoid TCC/chmod/sudo advice, and offer the two fixes: restart once with nono run --allow, or draft a persistent profile in ~/.config/nono/profile-drafts for nono profile promote.
Understands nono security sandbox constraints. Use when running inside a nono sandbox, when tool operations fail with permission errors, or when the user asks about sandbox capabilities.
Understands nono security sandbox constraints for GitHub Copilot CLI. Use when running inside a nono sandbox, when operations fail with permission errors, or when a tool use is denied.
Diagnose and resolve permission denials when Pi Coding Agent runs inside a nono security sandbox. Use this when a tool call, shell command, file operation, extension, package install, or provider request fails with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors.
Diagnose and resolve permission denials when Hermes Agent runs inside a nono security sandbox. Use when terminal, file, browser, MCP, plugin, or skill operations fail with "Operation not permitted", "Permission denied", EACCES, EPERM, landlock, or sandbox-denied errors.
| name | nono-sandbox |
| description | Diagnose nono sandbox denials and choose safe remediation when Goose is running inside nono. |
Use this skill when a Goose command, extension, MCP server, hook, recipe, or shell action fails with a permission, sandbox, filesystem, keychain, process, launch-service, or network denial.
Goose permissions and MCP approvals do not override nono. If the OS sandbox denies access, retrying with a Goose-level approval will not help unless the nono profile already permits that capability.
$TMPDIR, or /tmp/goose-$UID.~/.agents/plugins.~/.config/goose, ~/.local/share/goose, or ~/.local/state/goose.Ask the user before suggesting a profile expansion that grants access to:
~/.agents/plugins/<plugin-name> and project .agents/plugins/<plugin-name>.<plugin-name>:<skill-name>.extensions key.