AF amg-check-storage-account
Run only when the user explicitly asks for a fleet-wide Azure Storage Account health check — pulse check for availability, latency, transactions, and error rates across all accounts, then deep-dives into the top 7 most interesting accounts with metrics (E2E latency, server latency, capacity, ingress/egress) and resource logs. Tracks known issues across sessions via persistent report. On first run, auto-discovers datasource UID and prompts for subscription ID.
As a process F 73/100 · Will not run — References files that are not bundled: ${CLAUDE_SKILL_DIR}/reference/analysis-patterns.md, ${CLAUDE_SKILL_DIR}/reference/deep-dive-queries.md, ${CLAUDE_SKILL_DIR}/reference/error-handling.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ${CLAUDE_SKILL_DIR}/reference/analysis-patterns.md - warning
missing-refreference to a missing file: ${CLAUDE_SKILL_DIR}/reference/deep-dive-queries.md - warning
missing-refreference to a missing file: ${CLAUDE_SKILL_DIR}/reference/error-handling.md - note
frontmatter-keyunknown frontmatter key "effort"
Process rating: all ten parameters 73/100
- 0Tools and files. 3 referenced file(s) missing: ${CLAUDE_SKILL_DIR}/reference/analysis-patterns.md, ${CLAUDE_SKILL_DIR}/reference/deep-dive-queries.md, ${CLAUDE_SKILL_DIR}/reference/error-handling.md
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 59 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 12 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3955 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 14 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)
- +1No license
- +2Single-language instructions
- +3Description length 463: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 59 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.