BF markdown-toolkit-pro
(no description)
专业版面向团队与企业，在免费版单文件生成基础上，扩展多文件站点与目录生成、文档规范 lint 与团队规则集、链接校验与死链检测、多格式导出。规则与免费版兼容，已有校验可直接纳入规则集.
As a process F 33/100 · Will not run — References files that are not bundled: missing.md
IntegrationSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
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: A block sequence may not be used as an implicit map key at line 9, column 1: description: "面向团队的多文件 Markdown 站点与文档规范治理专业工具。核心能力:。可自动提升工作效率。Use when 需要文件处理、文… - 多文件站点与目录（TOC）自动生成 ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 278 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: missing.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - 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: missing.md
- 0Tools and files. 1 referenced file(s) missing: missing.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
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1468 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: 33 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (13 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This Markdown toolkit is broadly aligned with documentation work, but it asks for command execution and file-writing authority without tight scoping or clear user control.
LLM: suspicious (medium) · VirusTotal: · 17 Aug 2026