SKILLEMALL.ai

CC codex-handoff

Orchestrate read-only Codex research in any mode, or one to eight Codex agents to implement approved plans from Claude Code or Codex CLI.

PaulRBerg/agent-skills Claude Code author: PaulRBerg MIT 9 files · 2 scripts body ≈ 5 944 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Orchestrate read-only Codex research in any mode, or one to eight Codex agents to implement approved plans from Claude Code or Codex CLI.

As a process C 61/100 · Has gaps — weak spots: result and completion, progress reporting

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5944 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "skill-dependencies"

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5944 tokens
  • 85Steps. 50 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (8 tags): a typed call is more reliable

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 137: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 50 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (2 of 3)

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