BF audio-stream-upload
(no description)
降低并发数至2-3个，并在请求间添加适当延迟。专业版支持自动限流检测与退避重试.
As a process F 33/100 · Will not run — References files that are not bundled: references/style.md, assets/output.json
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Block scalar header includes extra characters: |-。企业级音频上传工具，支持批量上传、自定义编码、多质量预设、分片上传与元数据管理。音频流上传专业版 at line 12, column 16: description: |-。企业级音频上传工具，支持批量上传、自定义编码、多质量预设、分片上传与元数据管理。音频流上传专业版 —— 面向企业团队与专业创作… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 254 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: references/style.md - warning
missing-refreference to a missing file: assets/output.json - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "summary_zh" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: references/style.md, assets/output.json
- 0Tools and files. 2 referenced file(s) missing: references/style.md, assets/output.json
- 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
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3599 tokens
- 100Running it twice. No mutating operations
- low 18 top-level sections: this looks like several domains in one skill
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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 45 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: suspicious
This appears to be an audio upload skill, but it needs review because it can batch-send local audio files, metadata, and API keys to a third-party service while declaring broader triggers and tool authority than necessary.
LLM: suspicious (high) · 2 Aug 2026