DD release-notes-drafter
(no description)
The skill promises to generate release notes but has no description—unclear what it actually does. Only one file in the folder, no scripts, under 100 tokens of content. Quality score 28 out of 100, process score 46—both low. No critical errors, but the missing description is a red flag.
It supports many platforms from Claude to DeepSeek, but that doesn't fix the empty core. Skip it. You need a proper description and a working demo first.
Draft release notes from the merged pull requests since the last tag.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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
Process rating: all ten parameters 46/100
- 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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 97 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Step-by-step instructions: 4 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 28.