SKILLEMALL.ai
GitHub ↗ RU Sign in

AC codex-delegate

Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Codex — phrasings like "have Codex do X", "delegate this to Codex", "run it through Codex", or "use Codex to implement/fix/refactor" — or to run a queue of coding tasks through Codex while staying the reviewer. Prefer it over a one-shot Codex forwarder (such as the codex-rescue agent) when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

amElnagdy/delegate-skills Agent Skills author: amElnagdy 6 files · 1 script body ≈ 2 658 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself.

As a process C 60/100 · Has gaps — References files that are not bundled: ../codex-background/references/configuration.md

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
98/100
safety, quality, tests
Safety 60%
100
Quality 40%
95
Run on models
none yet
Process rating
C
60/100
Has gaps
References files that are not bundled: ../codex-background/references/configuration.md
Tools and files w 18
0
Running it twice w 4
30
Result and completion w 14
40
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../codex-background/references/configuration.md

Process rating: all ten parameters 60/100

Will not run. References files that are not bundled: ../codex-background/references/configuration.md
  • 0Tools and files. 1 referenced file(s) missing: ../codex-background/references/configuration.md
  • 30Running it twice. 12 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 21 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2658 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 646: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)
  • +3All 1 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.