SKILLEMALL.ai

CF skill-author

The authoring gate for new skills. Routed to when the user invokes /new-skill "<gap>". Five gated phases — gap evidence, scope, authoring, self-review against the v2 house style, routing integration. A new skill is not written until an existing one is proven not to cover the gap, and not shipped until it carries gated phases, hard rules, and a routing entry. Every authored skill matches the v2 format (frontmatter name+description,

arbiterForge/codeArbiter Agent Skills author: arbiterForge AGPL-3.0 2 files body ≈ 2 405 tokens Open the sourcegithub.com analyzed 25 h ago

The authoring gate for new skills.

As a process F 46/100 · Will not run — References files that are not bundled: ../INDEX.md, ../commit-gate/SKILL.md, ../tdd/SKILL.md

AnalyzerSoftware developmentAI and agentsData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: ../INDEX.md, ../commit-gate/SKILL.md, ../tdd/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
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: skill-author (arbiterForge/codeArbiter)

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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../INDEX.md
  • warning missing-ref reference to a missing file: ../commit-gate/SKILL.md
  • warning missing-ref reference to a missing file: ../tdd/SKILL.md
  • warning missing-ref reference to a missing file: ../<name>/SKILL.md
  • warning missing-ref reference to a missing file: ../../agents/<name>.md
  • warning missing-ref reference to a missing file: ../<name>
  • note edit-residue the text marks something as outdated (lines 67, 102): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: ../INDEX.md, ../commit-gate/SKILL.md, ../tdd/SKILL.md
  • 0Tools and files. 6 referenced file(s) missing: ../INDEX.md, ../commit-gate/SKILL.md, ../tdd/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 9 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2405 tokens
  • 100Progress reporting. Reports progress
  • 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 (22 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 434: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 42 items
  • +4Reference files are cited in the instructions (1 of 1)

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