BC azure-infra-free
Azure Infra Free 是 Azure Infra 技能的免费精简版，通过本地 Azure CLI（az 命令） 提供 Azure 资源的只读查询能力。支持基础的资源清单查询与简单的健康检查， 不包含写操作、安全审计、成本分析等高级功能. 核心能力： - 资源清单查询：资源组、虚拟机、存储账户、虚拟网络等基础资源的列举 - 简单健康检查：查看虚拟机电源状态、查询失败的活动日志 - 只读优先：所有操作默认只读，不执行任何写操作或破坏性变更 适用场景： - 快速盘点订阅内的虚拟机与存储资源 - 查看虚拟机...
Azure Infra Free 是 Azure Infra 技能的免费精简版，通过本地 Azure CLI（az 命令） 提供 Azure 资源的只读查询能力。支持基础的资源清单查询与简单的健康检查， 不包含写操作、安全审计、成本分析等高级功能.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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
description-long-hermesdescription is 262 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - 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 "homepage"
Process rating: all ten parameters 55/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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2138 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 25 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
- +2Single-language instructions
- +3Description length 262: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.