cask
Async via cask, end turn immediately; use only when user explicitly delegates to Codex (ask/@codex/let codex/review); NOT for questions about Codex itself.
When & Why to Use This Skill
The 'cask' skill is a specialized developer tool designed for asynchronous task delegation to Codex. It allows Claude to offload complex requests—such as code reviews or specialized technical queries—to a background process, ensuring the agent can immediately acknowledge the request without blocking the user interface. This skill is essential for optimizing multi-agent workflows and managing long-running computational tasks within an agentic framework.
Use Cases
- Asynchronous Code Review: Seamlessly delegate large-scale code analysis to Codex by using triggers like 'review' or '@codex', allowing the system to process the request in the background.
- Specialized Technical Query Routing: Explicitly hand off deep technical questions to the Codex backend when specialized knowledge or higher-compute resources are required.
- Non-blocking Task Execution: Initiate background scripts or data processing via the 'cask' command, enabling the agent to end its turn immediately while the task continues to run independently.
| name | cask |
|---|---|
| description | Async via cask, end turn immediately; use only when user explicitly delegates to Codex (ask/@codex/let codex/review); NOT for questions about Codex itself. |
| short-description | Ask Codex asynchronously via cask |
Ask Codex (Async)
Send the user’s request to Codex asynchronously.
Execution (MANDATORY)
Bash(cask <<'EOF'
$ARGUMENTS
EOF
, run_in_background=true)
Rules
- After running
cask, say “Codex processing...” and immediately end your turn. - Do not wait for results or check status in the same turn.
Notes
- If it fails, check backend health with
cping.