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.
87
81%
Does it follow best practices?
Impact
96%
1.54xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 well-structured skill description with strong trigger term coverage and explicit 'WHEN' guidance. The main weakness is that the capability description could be more specific about concrete actions (e.g., 'configure custom events, track dependencies, set up availability tests'). Overall, it effectively communicates both purpose and activation conditions.
Suggestions
Expand the capability section with more concrete actions like 'configure custom metrics, track exceptions, set up distributed tracing, monitor dependencies' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Application Insights) and mentions some actions (telemetry patterns, SDK setup, configuration references), but doesn't list multiple concrete specific actions like 'configure custom metrics, track exceptions, set up distributed tracing'. | 2 / 3 |
Completeness | Clearly answers both what (guidance for instrumenting webapps with Azure Application Insights, telemetry patterns, SDK setup, configuration references) AND when (explicit 'WHEN:' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'instrument app', 'App Insights SDK', 'telemetry patterns', 'Application Insights', 'instrumentation examples', 'APM best practices'. These are terms users would naturally use when seeking this guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Azure Application Insights specifically. The combination of 'App Insights', 'Azure', 'telemetry', and 'instrumentation' creates a distinct trigger profile unlikely to conflict with other monitoring or Azure skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured routing/guidance skill that efficiently directs Claude to appropriate resources based on context. Its strengths are excellent progressive disclosure and concise writing. The main weakness is that it's primarily a decision tree pointing to other files rather than containing actionable implementation details itself, and it lacks validation steps for confirming successful instrumentation.
Suggestions
Add a brief validation step after instrumentation (e.g., 'Verify telemetry appears in Azure Portal within 5 minutes' or a test command)
Consider including one minimal inline code example for the most common case (ASP.NET Core) to make the skill more immediately actionable without requiring file lookups
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what App Insights is or how Azure works. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear decision trees and references to concrete examples (bicep files, scripts), but the main content is guidance/routing rather than executable code. The actual implementation details are delegated to reference files. | 2 / 3 |
Workflow Clarity | Steps are listed (collect context → prefer auto-instrument → manually instrument with sub-steps), but lacks explicit validation checkpoints. No feedback loops for verifying instrumentation success or error recovery. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-signaled one-level-deep references to language-specific guides, SDK references, and example files. Navigation is intuitive with organized sections. | 3 / 3 |
Total | 10 / 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/github-copilot-for-azure
- Commit
1f4304b
- 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.