BC azure-gateway-cli
[''多Azure端点路由，按权重与延迟动态分配流量'', ''故障自动切换与熔断保护，单端点异常不影响整体可用性'']。"企业级Azure。Use when 需要SEO优化、关键词分析、排名提升、搜索流量优化时使用。不适用于黑帽SEO手段。适用于独立开发者、企业团队和自动化工作流场景。支持中文交互，无需复杂配置即开即用。
[''多Azure端点路由，按权重与延迟动态分配流量'', ''故障自动切换与熔断保护，单端点异常不影响整体可用性'']。"企业级Azure。Use when…
As a process C 53/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: Missing , or : between flow sequence items at line 10, column 17: description: [''多Azure端点路由，按权重与延迟动态分配流量'', ''故障自动切换与熔断保护，单端点异常不影响整体可用性'']。"企业级A… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 162 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 "edition" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 55 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2147 tokens
- 100Running it twice. No mutating operations
- low 21 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 162: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
The skill is mostly an Azure OpenAI gateway guide, but it has inconsistent purpose text and under-scoped instructions for caching, credentials, command execution, and optional startup persistence.
LLM: suspicious (high) · 2 Aug 2026