AF product-scoper
When the user wants to define their MVP scope, decide what features to include or exclude, create a product positioning statement, or cut a feature list down to essentials. Also use when the user mentions "定义MVP", "产品范围", "功能清单", "产品定位", "MVP scope", "feature cut", "what to build first", "minimum viable product". For finding opportunities, see opportunity-finder. For competitor analysis, see competitor-teardown. For generating a development plan from the scope, see build-planner.
When the user wants to define their MVP scope, decide what features to include or exclude, create a product positioning statement, or cut a feature list down…
As a process F 59/100 · Will not run — References files that are not bundled: ../../examples/scope-document.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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../examples/scope-document.md
Process rating: all ten parameters 59/100
- 0Tools and files. 1 referenced file(s) missing: ../../examples/scope-document.md
- 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
- 40Consistency. Frontmatter name (product-scoper) differs from the folder (niche-product-scoper)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 18 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Execution cost. Instruction body is 970 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
- +4Description does not say when NOT to use the skill (false activations)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 484: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.