Menu
Use when launching a persistent Codex goal run with `boondoggle` from a prompt on stdin.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants to run a long or resource-heavy task on another computer so their local machine stays free, the work continues if they close their laptop or lose connection, and the result returns as a reviewable branch in their project. Use this skill also when no offload target exists yet and the user needs help setting one up.
Use for dispatching a command from the current git repo to a remote machine in order to offload work for execution.
Clone GitHub repos on this machine with ghwc: canonical owner/repo casing, shared bare clone, branch-named sibling worktrees under ~/Projects.
Use this skill for any task involving the ambit CLI: creating or destroying private networks, deploying apps to a private network, checking network or router health, listing routers, diagnosing connectivity problems, managing app secrets, or streaming app logs. Trigger phrases include "create a network", "set up ambit", "deploy with ambit", "ambit create", "ambit deploy", "ambit doctor", "check router status", "destroy a network", "managing app secrets", "streaming app logs", and similar.
Use when inspecting state, output, completion, or worktree activity for Codex goal runs launched by Boondoggle.
Use this to check or configure auth and config state on a remote device via a Foolfad transport -- this is `foolfad-configure`.
| name | boondoggle |
| description | Use when launching a persistent Codex goal run with `boondoggle` from a prompt on stdin. |
Use boondoggle when the user wants to hand a prompt to Codex as a goal and let it run from a chosen working tree.
Boondoggle reads the full prompt from stdin. Empty prompts fail.
printf '%s\n' 'Implement the requested change and run tests' | boondoggle
Run it from the repository or directory that should become the Codex working root. Override that root with ROOT when needed:
ROOT=/path/to/repo printf '%s\n' 'Run the migration checks' | boondoggle
Boondoggle starts codex app-server, creates a thread in the selected working directory, sets the stdin prompt as the active goal, and resumes the thread with:
model: gpt-5.5
approvalPolicy: never
sandbox: danger-full-access
It prints progress events from Codex, including thread id, goal status, turn start/completion, and selected message text.
ROOT selects the Codex working directory. It defaults to $PWD.BOONDOGGLE_MODEL overrides the thread model. It defaults to gpt-5.5.BOONDOGGLE_APPROVAL_POLICY overrides the approval policy. It defaults to never; --ask-for-approval is accepted as an alias.BOONDOGGLE_SANDBOX overrides the thread sandbox. It defaults to danger-full-access.BOONDOGGLE_EFFORT sets the reasoning effort when provided; --reasoning-effort is accepted as an alias.BOONDOGGLE_PERSONALITY sets the Codex personality when provided.BOONDOGGLE_SUMMARY sets the summary preference when provided.BOONDOGGLE_THREAD_CONFIG_JSON merges an additional JSON object into the thread/start and thread/resume params. Values in this object override the named defaults.BOONDOGGLE_PROFILE passes top-level --profile-v2 to Codex when provided.BOONDOGGLE_LISTEN passes --listen to codex app-server when provided.GIT_PUBLISH_ON_GOAL_SUCCESS, GIT_PUBLISH_ON_GOAL_FAILURE, and GIT_PUBLISH_ON_UNEXPECTED_EXIT control whether Boondoggle commits and pushes worktree state for those outcomes.GIT_COMMIT_MESSAGE overrides the status commit subject prefix. It defaults to Codex Goal Worktree State.After launching Boondoggle, report:
If the user later asks about progress, use the boondoggle-runs skill when it is available.