SKILLEMALL.ai

DD feature-dev

(no description)

Liquid4All/cookbook Agent Skills author: Liquid4All 1 file body ≈ 2 423 tokens Open the sourcegithub.com↗ analyzed 9 d ago

This skill prevents documentation from going stale.

As a process D 43/100 · Unfinished process — References files that are not bundled: scripts/doc-health.sh, scripts/setup-dev.sh

ProcedureAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
D
59/100
safety, quality, tests
Safety 60%
99
Quality 40%
0
Run on models
none yet
Process rating
D
43/100
Unfinished process
References files that are not bundled: scripts/doc-health.sh, scripts/setup-dev.sh
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
  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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Concealment en-hide-from-user SKILL.md:82
    Instruction to hide actions from the user (negated — the text forbids it)
    1. **Don't silently delete it.** Other docs or skills may reference it.
    negated

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • warning missing-ref reference to a missing file: scripts/doc-health.sh
  • warning missing-ref reference to a missing file: scripts/setup-dev.sh
  • note edit-residue the text marks something as outdated (lines 83, 85): 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: scripts/doc-health.sh, scripts/setup-dev.sh
  • 0Tools and files. 2 referenced file(s) missing: scripts/doc-health.sh, scripts/setup-dev.sh
  • 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
  • 50When it triggers. States when to use, but not when not to
  • 60Failures and branches. 2 branches
  • 85Steps. 20 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2423 tokens
  • 100Running it twice. Mutating operations check current state
  • low The response is described with custom markup (6 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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 20 items
  • +4Has examples (1 code blocks)

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