BC docker-essentials
|-。涵盖容器生命周期、镜像管理、Compose、网络、数据卷、系统管理等Docker核心操作。Docker核心操作指南，覆盖容器生命周期的完整管理流程。Use when 需要数据分析、报表生成、统计洞察、数据可视化时使用。不适用于实时流数据处理。适用于独立开发者、企业团队和自动化工作流场景。支持中文交互，无需复杂配置即开即用。 功能涵盖: essentials。
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: |-。涵盖容器生命周期、镜像管理、Compose、网络、数据卷、系统管理等Docker核心操作。Docker核心操作指南，覆盖容器生命周期的完整管理流程。Use at line 11, column 16: description: |-。涵盖容器生命周期、镜像管理、Compose、网络、数据卷、系统管理等Docker核心操作。Docker核心操作指南，覆盖容器生… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 183 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - 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 51/100
- 0Result and completion. Does not say what the result is
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2614 tokens
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 183: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (21 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
This is mostly a Docker command guide, but it grants execution-oriented authority while its trigger text is partly unrelated and several destructive Docker operations are under-scoped.
LLM: suspicious (high) · 22 Aug 2026