BD enhance-skill-prompts
Upgrade how an existing SKILL.md instructs, not what it does: freedom, a classification contract, one worked example, an evidence rubric, effort. Use when "enhance this skill's prompts", "upgrade skill authoring", or "apply the prompt playbook".
Upgrade how an existing SKILL.md instructs, not what it does: freedom, a classification contract, one worked example, an evidence rubric, effort. Use when…
As a process D 41/100 · Unfinished process — References files that are not bundled: ../../docs/PROMPT-ENHANCEMENT-PLAYBOOK.md, scripts/validate-skills.mjs
How to improve
- The text references files that are not there: add them or drop the references.
- 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-refreference to a missing file: ../../docs/PROMPT-ENHANCEMENT-PLAYBOOK.md - warning
missing-refreference to a missing file: scripts/validate-skills.mjs - note
frontmatter-keyunknown frontmatter key "effort"
Process rating: all ten parameters 41/100
- 0Tools and files. 2 referenced file(s) missing: ../../docs/PROMPT-ENHANCEMENT-PLAYBOOK.md, scripts/validate-skills.mjs
- 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
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2010 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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
- +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
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 245: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 30 items
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.