BC azure-cloud-inspector-pro
Azure巡检员专业版是一个以"日常巡检"为核心视角的Azure CLI辅助工具,面向运维工程师、云架构师、安全工程师、FinOps专员、合规审计员五类角色。针对云上资源"配置漂移无人察觉、公网暴露面长期敞开、RBAC过度授权难发现、成本失控无预警、NSG端口暴露无矩阵、跨订阅巡检低效、巡检结论难分享、历史趋势无对比"八大痛点,构建了风险评分模型、暴露面发现、配置漂移检测、巡检任务模板、巡检报告生成、RBAC深度审计、Cost
Azure巡检员专业版是一个以"日常巡检"为核心视角的Azure…
As a process C 51/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.
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: Unexpected scalar at node end at line 6, column 76: …计、成本管理、NSG暴露矩阵、跨订阅批量、定时调度、趋势对比.。Azure巡检员专业版是一个以"日常巡检"为核心视角的Azure CLI辅助工具,面向运维工" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 215 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 "edition" - note
frontmatter-keyunknown frontmatter key "tools"
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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 70Execution cost. Instruction body is 4364 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 19 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 215: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (23 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: clean
This skill is a broad Azure inspection helper that mainly uses read-only Azure CLI checks, but users should be careful with optional reporting, scheduling, and callback features because they can expose sensitive cloud posture data.
LLM: benign (medium) · VirusTotal: · 28 Aug 2026