BF technical-seo-checker
Use when the user asks to "check technical SEO"; audits crawlability, indexing, Core Web Vitals, robots.txt, sitemaps, canonicals, redirects, and migrations. Not for on-page tags or content — use on-page-seo-checker. 技术SEO/网站速度
As a process F 57/100 · Will not run — References files that are not bundled: ../../../references/skill-contract.md, ../../../CONNECTORS.md, ../../../SECURITY.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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 227 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - 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: ../../../SECURITY.md - warning
missing-refreference to a missing file: ../../../scripts/connectors/README.md - warning
missing-refreference to a missing file: ../on-page-seo-checker/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 57/100
- 0Tools and files. 5 referenced file(s) missing: ../../../references/skill-contract.md, ../../../CONNECTORS.md, ../../../SECURITY.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 30 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 2770 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (13 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 227: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.