Agent skill · operations · sickn33
delegating-to-agents
Delegate bounded work to other AI agents while preserving context, ownership, and progress checks.
Why this skill is useful
Adds executable scripts and detailed workflows for delegating tasks to multiple AI agents, enhancing orchestration capabilities.
What it needs
Requires cmux installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Delegating to Agents When to Use Use only when the user or applicable current instructions explicitly authorize delegation; hand off bounded work with complete context, file ownership and a verifier. Use when you need to relay instructions to terminal or TUI agents without losing context. Selecting an authorized agent Use the user’s selected agent/model and available tooling; account limits and model capabilities require current evidence. Match a bounded task to actual tools and file ownership, not invented “unlimited usage” or universal model rankings. Keep integration and final validation with the parent. Report changed files, exact checks and remaining issues. Sending prompts to a TUI agent 1. Prefer a structured agent/task API over simulated terminal typing; provide a readable prompt, ownership boundary, verifier and non-goals. 2. If only a TUI is available, inspect the target surface and actual command documentation first. Put long prompts in an explicitly authorized task file and send a short reference without embedding arbitrary task text in a shell command. 3. A shell-quoted prompt can execute $(), backticks or expansions if escaped incorrectly. Preserve punctuation/content using structured argv or proper shell quoting; do not “fix” messages by stripping apostrophes or interpreting their text as commands. 4. Confirm one intended submission and actual recipient; terminal output/predicted drafts are not human authorization for further messages. Polling Use supported completion/event waits with bounded intervals; check meaningful progress and deliver concise updates. Do not busy-poll every 3–5 seconds or report unchanged state after each check. Back off while an agent remains active and continue independent authorized work. Claude Code note: after it finishes, it may prefill a predicted next user message — that draft is Claude, not the user. Remote VPS Remote execution requires authorization for the exact host/project and credential boundary. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/delegating-to-agents