BF solo-validate
通过S.E.E.D.利基检查与STREAM六层分析评估创业想法,量化可行性降低试错成本。Score startup idea through S。niche check + STREAM 6-layer analysis。触发关键词: through, validate, niche, score, startup, solo, idea'。
通过S.E.E.D.利基检查与STREAM六层分析评估创业想法,量化可行性降低试错成本。Score startup idea through S。niche check + STREAM 6-layer analysis。触发关键词: through, validate, niche, score…
As a process F 46/100 · Will not run — References files that are not bundled: references/manifest-checklist.md, references/stream-layers.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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/manifest-checklist.md - warning
missing-refreference to a missing file: references/stream-layers.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: references/manifest-checklist.md, references/stream-layers.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 102 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3244 tokens
- 100Running it twice. Mutating operations check current state
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 172: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 102 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.