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.
63
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/plugins/azure-skills/skills/appinsights-instrumentation/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Azure Application Insights instrumentation) and includes an explicit WHEN clause with relevant trigger terms. The main weakness is that the 'what' portion could be more specific about the concrete actions or patterns it covers, staying somewhat at the category level rather than listing specific capabilities like custom metrics, distributed tracing, or exception tracking.
Suggestions
Expand the capability list with more concrete actions, e.g., 'configure custom metrics, set up distributed tracing, add exception tracking, configure sampling and filtering' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Application Insights) and some actions (telemetry patterns, SDK setup, configuration references), but doesn't list multiple concrete actions like 'configure custom metrics, set up distributed tracing, add exception tracking'. | 2 / 3 |
Completeness | Clearly answers both 'what' (guidance for instrumenting webapps with Azure Application Insights, telemetry patterns, SDK setup, configuration references) and 'when' with an explicit WHEN clause listing trigger scenarios. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'instrument app', 'App Insights SDK', 'telemetry patterns', 'Application Insights', 'instrumentation examples', 'APM best practices'. These are terms a developer would naturally use when seeking this guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Azure Application Insights instrumentation, which is a clear niche. The trigger terms like 'App Insights SDK', 'Application Insights guidance' are distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions well as a routing/decision document that directs Claude to the right reference material based on the user's context. Its progressive disclosure is its strongest aspect, with clear links to platform-specific guides and examples. However, the body itself lacks concrete executable examples and validation checkpoints, relying heavily on referenced files that weren't provided for evaluation.
Suggestions
Add at least one inline code snippet (e.g., a minimal Azure CLI command or a one-liner SDK setup) so the skill body itself is actionable without requiring file lookups.
Add explicit validation steps after resource creation (e.g., 'Verify the resource exists: `az monitor app-insights component show ...`') and after code modification (e.g., 'Run the app and confirm telemetry appears in the Azure portal').
Consolidate the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections into a single compact decision block or merge with the callout box to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like 'When to Use This Skill' vs 'When to Use azure-prepare Instead' which could be condensed. The 'Collect context information' section explains process steps that are somewhat verbose for Claude. The callout box about azure-prepare is useful but the dual 'when to use' sections are redundant with it. | 2 / 3 |
Actionability | The skill provides structured guidance and references to specific files (bicep templates, scripts, language-specific guides), but the body itself contains no executable code or concrete commands. It relies entirely on referenced files for actual implementation details, making the skill itself more of a routing document than an actionable guide. | 2 / 3 |
Workflow Clarity | The workflow has a reasonable sequence (collect context → decide auto vs manual → create resource → modify code), but lacks explicit validation checkpoints. For an operation that modifies infrastructure and application code, there are no verification steps (e.g., confirm resource creation succeeded, validate telemetry is flowing). The decision tree between auto-instrument and manual is clear, however. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a clear overview/routing document with well-signaled one-level-deep references to specific guides (auto.md, aspnetcore.md, nodejs.md, python.md), examples (appinsights.bicep), scripts (appinsights.ps1), and SDK references. Navigation is easy and organized by platform and approach. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/azure-skills
- Commit
d02fd24
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.