BF clawddocs
(no description)
"When a user asks about SkillHub, first identify what they need:" 1.
As a process F 23/100 · Will not run — References files that are not bundled: assets/clawddocs_template
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: Missing , or : between flow sequence items at line 11, column 17: description: [''知识管理领域的专业化AI辅助工具'']。"SkillHub文档专家,带决策树导航,快速定位答案。SkillHub docume… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 204 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: assets/clawddocs_template - 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 "tools" - note
frontmatter-keyunknown frontmatter key "pricing_tier"
Process rating: all ten parameters 23/100
Will not run. References files that are not bundled: assets/clawddocs_template
- 0Tools and files. 1 referenced file(s) missing: assets/clawddocs_template
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (clawddocs) differs from the folder (docs-toolkit)
- 85Steps. 32 steps, 2 vague phrases
- 100Execution cost. Instruction body is 1520 tokens
- low 13 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: 24 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This skill is mostly a documentation helper, but it asks for command/write capability and includes an unclear script-running instruction that is not well scoped or explained.
LLM: suspicious (high) · 25 Aug 2026