SKILLEMALL.ai
GitHub ↗ RU Sign in

CF subagent-driven-development

The implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.

arbiterForge/codeArbiter Claude Code author: arbiterForge AGPL-3.0 2 files body ≈ 3 109 tokens Open the sourcegithub.com↗ analyzed 25 h ago

The implementation engine.

As a process F 43/100 · Will not run — References files that are not bundled: ../../includes/artifacts.md, ../../agents/<name>.md, ../tdd/SKILL.md

AnalyzerSecurityOperations and projectstype 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
C
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: ../../includes/artifacts.md, ../../agents/<name>.md, ../tdd/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: subagent-driven-development (arbiterForge/codeArbiter)

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 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: 2. 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 missing-ref reference to a missing file: ../../includes/artifacts.md
  • warning missing-ref reference to a missing file: ../../agents/<name>.md
  • warning missing-ref reference to a missing file: ../tdd/SKILL.md
  • warning missing-ref reference to a missing file: ../../agents/finding-triage.md
  • warning missing-ref reference to a missing file: ../../agents/security-reviewer.md
  • warning missing-ref reference to a missing file: ../../agents/auth-crypto-reviewer.md
  • warning missing-ref reference to a missing file: ../../agents/dependency-reviewer.md
  • warning missing-ref reference to a missing file: ../../agents/migration-reviewer.md
  • warning missing-ref reference to a missing file: ../../includes/fresh-verification.md
  • note edit-residue the text marks something as outdated (lines 11): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: ../../includes/artifacts.md, ../../agents/<name>.md, ../tdd/SKILL.md
  • 0Tools and files. 9 referenced file(s) missing: ../../includes/artifacts.md, ../../agents/<name>.md, ../tdd/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 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
  • 100Steps. 32 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3109 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (3 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 342: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 32 items
  • +4Reference files are cited in the instructions (1 of 1)

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