skills.rest
tony-zhelonkin
tony-zhelonkinCOMMUNITY
Explore all skills by this author →
𝕏@TonyZhelonkinGitHub

delegate-cli

Delegate bounded implementation, review, and research tasks to local codex and agy CLIs.

1|Updated Nov 20, 2025
Search Tags:#code review#delegation#codex cli#run status#task fan-out#agy cli#capability probing
One-click install
npx skills add https://github.com/tony-zhelonkin/scio --skill delegate-cli-tony-zhelonkin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: delegate-cli
Source: https://github.com/tony-zhelonkin/scio/tree/main/skills/delegate-cli
Command: npx skills add https://github.com/tony-zhelonkin/scio --skill delegate-cli-tony-zhelonkin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Delegating work to peer AI CLIs often fails silently: workers answer without reading the repository, models get refused by outdated CLIs, parallel runs collide, and nobody verifies the result. This Skill provides a disciplined workflow for launching codex and agy workers with scoped prompts, capability probes, run-state tracking, and mandatory post-run review. ## Core Features & Use Cases - Capability probing: probe.sh checks the installed codex version, flag support, web-search mode, and whether sandboxed file reads actually work before a launch. - Managed launches: launch.sh runs codex in the foreground with unit locks, run directories, status snapshots, expected-artifact checks, and classified exit codes for sandbox blocks and model-version gaps. - Run inspection: status.sh reports heartbeat age, activity age, artifact sizes, and exit codes by unit or status file, with a --wait mode for shadowing another run. - Use Case: Fan out two independent code-review units to codex with disjoint write scopes, monitor them via status.sh, then re-run the acceptance tests and inspect every touched file before accepting the result. ## Quick Start Ask the assistant to delegate a bounded implementation task to codex by writing a file-backed prompt with acceptance commands and launching it through the skill's launch.sh script.

Frequently Asked Questions about delegate-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate a coding task to the codex CLI?▼

Write a file-backed prompt stating the task, deliverable, working directory, permission boundaries, and acceptance commands, then run launch.sh with --unit, --workdir, and --prompt. The launcher runs in the foreground and prints the worker's final message after a marker.

When should I use codex versus agy for delegation?▼

Prefer codex for implementation and code review, and agy for web research and very large-context synthesis. Always honor a user's explicitly named tool, and keep fan-out to two or three independent units with disjoint write scopes.

Why does codex exit 0 but produce wrong answers about my repository?▼

An enforced sandbox can block every file tool while codex still exits 0, so the worker answers from the prompt alone without reading the repo. The launcher detects this in the stream and reports exit 32; relaunch with danger-full-access or fix the container policy.

How do I run multiple delegation units in parallel safely?▼

Pass --parallel-ok only when units are truly independent: neither consumes output the other creates, and their write scopes are disjoint. Without it, the launcher refuses to start while another unit holds a live lock, serializing the runs.

What does the 'requires a newer version of Codex' error mean?▼

The server refuses a model by name when the installed codex CLI is too old for it, exiting 1 after launch. The launcher classifies this as exit 33 and prints the installed version; upgrade the CLI or pass --model with one the version serves.

How do I check whether a delegated run is hung or just slow?▼

Run status.sh with the unit name and compare heartbeat age to activity age. A fresh heartbeat with old activity means the supervisor is alive while codex computes; a stale heartbeat means the writer stopped, implicating the launcher, host, or filesystem.

Related Skills

Explore More Software Engineering Skills→
anilcan-karaanilcan-kara

antigravity-cli

Automate Antigravity CLI (agy) installation, configuration, and plugin management.

Community
Intermediate
AlmogMaayanAlmogMaayan

ptp-brainstorming

Turns a change request into one recorded decision capsule with alternatives and assumptions.

Community
Intermediate
tomascuprtomascupr
68

taste

Review git diffs with Codex and validate findings via Claude.

Community
Advanced
autonomy-cloudautonomy-cloud
2

vellum-terminal-sessions

Manage persistent tmux terminal sessions for long-running CLI tasks.

Official
Intermediate