BF keyword-research
Use when the user asks to "find keywords", "挖词", or "搜什么词"; prioritizes search volume, keyword difficulty, intent, and topic clusters from provided or connected data. Not for competitor-relative coverage gaps — use content-gap-analysis. 关键词研究/内容选题
As a process F 50/100 · Will not run — References files that are not bundled: ../competitor-analysis/SKILL.md, ../../../references/skill-contract.md, ../../../CONNECTORS.md
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.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 247 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../competitor-analysis/SKILL.md - warning
missing-refreference to a missing file: ../../../references/skill-contract.md - warning
missing-refreference to a missing file: ../../../CONNECTORS.md - warning
missing-refreference to a missing file: ../../../scripts/connectors/README.md - warning
missing-refreference to a missing file: ../content-gap-analysis/SKILL.md - warning
missing-refreference to a missing file: ../serp-analysis/SKILL.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 50/100
- 0Tools and files. 6 referenced file(s) missing: ../competitor-analysis/SKILL.md, ../../../references/skill-contract.md, ../../../CONNECTORS.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 24 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1694 tokens
- low The response is described with custom markup (4 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 247: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.