BF kano-model-strategist
Classify product features into Kano categories. Cut waste. Build MDP over MVP. You have 30 features and 6 weeks. Sort them into Kano's six categories (Must-be, Performance, Attractive, Indifferent, Reverse, Questionable) so you ship the ones that earn their place and cut the rest.
Classify product features into Kano categories.
As a process F 66/100 · Will not run — References files that are not bundled: references/kano-classification.md, references/kano-vs-mdpmvp.md, references/experience-rot-checklist.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/kano-classification.md - warning
missing-refreference to a missing file: references/kano-vs-mdpmvp.md - warning
missing-refreference to a missing file: references/experience-rot-checklist.md - warning
missing-refreference to a missing file: references/ceo-pushback-scripts.md - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 66/100
- 0Tools and files. 4 referenced file(s) missing: references/kano-classification.md, references/kano-vs-mdpmvp.md, references/experience-rot-checklist.md
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 26 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2179 tokens
- 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)
- +2Single-language instructions
- +3Description length 282: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.