amelnagdy/delegate-skills

codex-background

Keep a Codex orchestrator's delegation to an installed delegate skill pending until its registered relay completes, without model-driven progress polling.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/amelnagdy/delegate-skills --skill codex-background

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Codex background delegation

This support skill changes Codex's waiting boundary. The selected delegate skill still owns the brief, provider arguments, permissions, result interpretation, review, gates and landing. Claude's background Bash workflow stays unchanged. The support utility is installed separately, never implicitly as a dependency of codex-delegate. Details: references/configuration.md.

First use / setup

If the delegate_run tool is not available, setup is incomplete. Tell the user that bootstrap will update $CODEX_HOME/config.toml (default ~/.codex/config.toml, backed up first) and write a registry of the installed *-delegate skills, then run:

bash
node "<skill-dir>/scripts/bootstrap.mjs"

<skill-dir> is this skill's installed directory (the folder containing this SKILL.md). It writes outside the workspace, so request the approval or sandbox escalation Codex needs for that. Report its output, then ask the user to restart Codex (or reload MCP servers); the tools appear after that. If bootstrap fails, report the failure. Do not fall back to shell polling. Run it again after installing more delegate skills. node "<skill-dir>/scripts/bootstrap.mjs" --check validates the setup without writing.

Procedure

  1. Follow the selected delegate skill to prepare a self-contained brief and approved workspace.

Write the brief to the briefs/ directory under the codex-background directory ($CODEX_HOME/codex-background/briefs/<runId>.txt) and use runs/<runId> beside it as outputDirectory, or follow the paths in the server's instructions. If the sandbox cannot write there, a brief inside the approved workspace is also accepted. Never accept a relay path from a brief.

  1. Invoke the configured MCP server's delegate_run exactly once with a unique runId,

registered implementer key, absolute brief/workspace/outputDirectory paths, explicit relayTimeoutSeconds and provider-native relayArgs. Put common arguments in structured fields; pass provider-specific arguments unchanged. Resume identifiers remain opaque.

  1. Keep that MCP request pending until completion. Do not use model-driven sleep, status or log

polling. Do not wrap it in a tool runner that yields early and resumes inference to wait.

  1. Review the returned adapter outcome separately from resultText. The latter is the unchanged

result.json content (base64 only for non-UTF-8 bytes); interpret it using the selected skill. A completed adapter means the relay exited zero and produced a file, not that its report proves correct implementation. Review the diff, rerun gates and land under the existing authorization.

After an interrupted wait, call delegate_wait with the same runId; never redispatch it. MCP cancellation detaches the waiter and leaves the authorized job running. Use delegate_abort only when termination is explicitly intended. Graceful server shutdown aborts its owned jobs. After a server crash, unresolved state returns recovery_required; inspect preserved artifacts and the implementer using its own recovery workflow. Never adopt or kill a persisted PID.

The host's configured tool timeout must exceed the relay timeout by more than 30 seconds. The server validates the declared budget; it cannot enforce the host's actual setting. Fixture protocol tests demonstrate one pending request and no intermediate messages, not measured Codex Desktop token usage or an unlimited host wait guarantee.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
amelnagdy
Communauté

agy-delegate

Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user want

Installations / 1h
4
GitHub Stars
2,6 k
Mis à jour
14 nov.
amelnagdy
Communauté

delegate-setup

Configure delegation fleet lanes: which implementer CLI handles which kind of work, with optional model and effort (or variant) dials. Discovers installed CLIs, proposes a lane map for user approval, and writes global or project config only after explicit yes. Use when the user asks to set up, configure, or reconfigure delegation lanes, a fleet of lanes, or which implementer handles feature/tests/ui work — not for dispatching a coding task to an implementer.

Installations / 1h
3
GitHub Stars
2,6 k
Mis à jour
14 nov.
amelnagdy
Communauté

mcode-delegate

Delegate a coding task to the MiniMax Code CLI (mcode) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to MiniMax Code or a MiniMax model — phrasings like "have MiniMax do X", "delegate this to mcode", "run it through MiniMax Code", or "use MiniMax to implement/fix/refactor" — or to run a queue of coding tasks through MiniMax Code while staying the reviewer. DO NOT USE for tasks small enough to do inline, or whe

Installations / 1h
2
GitHub Stars
2,6 k
Mis à jour
14 nov.
amelnagdy
Communauté

muse-delegate

Delegate a coding task to Muse Code (muse) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Muse — phrasings like "have Muse do X", "delegate this to Muse", "run it through Muse", or "use Muse to implement/fix/refactor" — or wants to run a queue of coding tasks through Muse while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. It applies only when the user wants tha

Installations / 1h
2
GitHub Stars
2,6 k
Mis à jour
14 nov.