SKILLEMALL.ai

BD appinsights-instrumentation

Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.

microsoft/azure-skills Agent Skills author: microsoft 12 files · 1 script body ≈ 842 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Guidance for instrumenting webapps with Azure Application Insights.

As a process D 44/100 · Unfinished process — References files that are not bundled: examples/appinsights.bicep

ProcedureAzureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: examples/appinsights.bicep
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: appinsights-instrumentation (microsoft/skills)

How to improve

  1. 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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: examples/appinsights.bicep

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: examples/appinsights.bicep
  • 0Tools and files. 1 referenced file(s) missing: examples/appinsights.bicep
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 20 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 842 tokens

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
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 303: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 20 items
  • +4Reference files are cited in the instructions (5 of 5)
  • +3All 1 scripts are documented
  • +1License stated

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