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.
82
73%
Does it follow best practices?
Impact
96%
1.54xAverage score across 3 eval scenarios
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 provides explicit trigger terms via a WHEN clause. The main weakness is that the 'what' portion could be more specific about the concrete actions or patterns it covers, rather than staying at a slightly abstract level with terms like 'telemetry patterns' and 'configuration references'.
Suggestions
Expand the capability description with more concrete actions, e.g., 'configure custom metrics, set up distributed tracing, add exception and dependency tracking, configure sampling and filtering'.
| 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 serves well as a routing/reference hub with excellent progressive disclosure and clear navigation to language-specific guides and resource templates. Its main weaknesses are the lack of inline executable examples and missing validation/verification steps after instrumentation changes. The content could be tightened by condensing the 'when to use' sections and removing guidance Claude can infer.
Suggestions
Add at least one inline executable code snippet (e.g., a minimal ASP.NET Core or Node.js instrumentation example) so the skill provides immediate actionable guidance without requiring file lookups.
Add explicit validation steps after resource creation and code modification (e.g., 'Verify telemetry is flowing by checking the App Insights Live Metrics stream' or 'Run the app locally and confirm traces appear').
Condense the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections into a single compact routing block to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally 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 things Claude could infer. The prerequisite and routing guidance is useful but slightly verbose. | 2 / 3 |
Actionability | Provides decision trees and references to concrete files (Bicep templates, PowerShell scripts, language-specific guides), but the skill itself contains no executable code or commands—it delegates everything to referenced files. The guidance is more directional than copy-paste ready. | 2 / 3 |
Workflow Clarity | The workflow has a clear 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 telemetry is flowing, validate Bicep template, test the instrumented app). | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview that routes to well-organized, one-level-deep references: auto.md, aspnetcore.md, nodejs.md, python.md, SDK references, Bicep examples, and PowerShell scripts. All references are clearly signaled with descriptive labels and organized by decision path. | 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
9d594ab
- 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.