DF news
(no description)
Promises to work everywhere from Claude to OpenClaw. In reality, it's one file with an empty description. Quality score of 23 out of 100 speaks for itself: no instruction on what the skill does, no examples, no logic. Linter complains about missing description—and rightfully so.
One file total, no scripts, models never ran, sandbox never tested it. No critical vulnerabilities, but only because there's nothing to be vulnerable. Skip this one: it's a sketch, not a tool.
Glance at one fresh headline and drop it into a single sentence in your own words — a casual, half-distracted aside between songs, never an anchor or…
As a process F 33/100 · No process to follow — weak spots: steps, result and completion, when it triggers
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- 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
- error
description-missingSKILL.md: no `description` — the skill can never trigger - note
frontmatter-keyunknown frontmatter key "label" - note
frontmatter-keyunknown frontmatter key "cooldown"
Process rating: all ten parameters 33/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 107 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 0: 120–800 characters recommended
- +4Structure: 0 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
Quality base 70; lint remarks subtract, signals add up to 100. Result: 23.