SKILLEMALL.ai

CF azure-monitor

Expert knowledge for Azure Monitor development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring Log Analytics, Application Insights, Container/VM Insights, autoscale alerts, or OpenTelemetry/Prometheus, and other Azure Monitor related development tasks. Not for Azure Network Watcher (use azure-network-watcher), Azure Service Health (use azure-service-health), Azure Defender For Cloud (use azure-defender-for-cloud), Cost Management (use azure-cost-management).

MicrosoftDocs/Agent-Skills Agent Skills author: MicrosoftDocs CC-BY-4.0 4 files body ≈ 9 739 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Expert knowledge for Azure Monitor development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas…

As a process F 32/100 · No process to follow — References files that are not bundled: security.md

IntegrationAzureKubernetesInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
97
Quality 40%
65
Run on models
none yet
Process rating
F
32/100
No process to follow
References files that are not bundled: security.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
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 · 3

✓ No critical or high findings

Medium and low: 3
  • low Secrets in code secret-high-entropy-token configuration.md:796
    High-entropy token-like string (may be an id, hash or a credential)
    | Understand Enri…ogs table schema in Azure Monitor | https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/enri…ogs |
  • low Secrets in code secret-high-entropy-token configuration.md:1131
    High-entropy token-like string (may be an id, hash or a credential)
    | Analyze Rapi…ies logs | https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/rapi…ies |
  • low Secrets in code secret-high-entropy-token configuration.md:1191
    High-entropy token-like string (may be an id, hash or a credential)
    | Use Wind…ogs table for diagnostics | https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/wind…ogs |

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 9739 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: security.md
  • note edit-residue the text marks something as outdated (lines 95, 223): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 32/100

Will not run. References files that are not bundled: security.md
  • 0Tools and files. 1 referenced file(s) missing: security.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 11 mutating operations with no state check
  • 40Execution cost. Instruction body is 9739 tokens: crowds the task out of the window
  • 50Steps. 2 steps
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 617: enough signal without eating the budget
  • +4Structure: 9 headings

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.