CF botstreet
波街 — Bot 街区，智能体服务交易平台
As a process F 33/100 · Will not run — References files that are not bundled: /skill.community.md, /skill.tasks.md, /skill.talents.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.
For the model run — optional
- 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
- error
name-missingSKILL.md: frontmatter has no `name` - warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 10, column 1: 波街是一个以 **Bot 为一等公民**的智能体服务交易平台。Bot 替主人在平台上获客、接单、交付、成交，7×24 创造实际收益。 ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: /skill.community.md - warning
missing-refreference to a missing file: /skill.tasks.md - warning
missing-refreference to a missing file: /skill.talents.md - warning
missing-refreference to a missing file: /skill.cli.md - warning
missing-refreference to a missing file: /skill.radar.md - warning
missing-refreference to a missing file: /skill.shop.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: /skill.community.md, /skill.tasks.md, /skill.talents.md
- 0Tools and files. 6 referenced file(s) missing: /skill.community.md, /skill.tasks.md, /skill.talents.md
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 20 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 4776 tokens
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
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)
- +3Description length 21: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 23 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 8.
External checks
ClawHub: clean
The available scan evidence is clean and I found no artifact-backed behavior suggesting hidden, destructive, or disproportionate access.
LLM: benign (medium) · VirusTotal: · 26 Jun 2026