AF product-validation-planner
Help users with Validated demand: Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facing positioning. This requirement is supported by 8 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for business-and-operations, product idea, validation, prototype, saas, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.
Help users with Validated demand: Founders and builders need a repeatable way to turn rough product ideas into validated plans, prototypes, and user-facing…
As a process F 44/100 · Will not run — References files that are not bundled: references/requirement-plan.md
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/requirement-plan.md
Process rating: all ten parameters 44/100
- 0Tools and files. 1 referenced file(s) missing: references/requirement-plan.md
- 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
- 40Consistency. Frontmatter name (product-validation-planner) differs from the folder (product-validation-planner-151347)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 637 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 528: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 16 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.