SKILLEMALL.ai

CD agent-coder

Agent skill for coder - invoke with $agent-coder

The skillemall take

Skill promises a coder agent invoked via $agent-coder. Files contain one instruction at 1624 tokens, no scripts. Checks show safety 100, quality 69, process 49. No critical errors, linter passes. Models untested, sandbox skipped.

Middling quality: process runs at half capacity, code quality lags behind. Supports many platforms, but that doesn't offset the low process-score. Install if you need a quick auxiliary agent and don't mind fixing the logic yourself.

ruvnet/claude-flow Agent Skills author: ruvnet MIT 1 file body ≈ 1 624 tokens Open the sourcegithub.com↗ analyzed 35 h ago

Agent skill for coder - invoke with $agent-coder

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 1. 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")

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 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. 1 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 100Steps. 44 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1624 tokens

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)
  • +3Description length 48: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (8 code blocks)

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