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 ./plugin/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 concrete actions beyond general categories like 'telemetry patterns' and 'SDK setup'. Overall it performs well for skill selection purposes.
Suggestions
Expand the capability description 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 | Includes a strong set of natural keywords users would say: 'instrument app', 'App Insights SDK', 'telemetry patterns', 'Application Insights', 'instrumentation examples', 'APM best practices'. Good coverage of common variations and natural phrasing. | 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 app's technology stack and hosting environment. Its progressive disclosure is strong with clear navigation to detailed guides. However, it lacks validation checkpoints for what are potentially destructive infrastructure and code changes, and the main body itself contains no executable examples, relying entirely on referenced files for concrete guidance.
Suggestions
Add validation/verification steps after resource creation (e.g., 'Verify the App Insights resource was created: `az monitor app-insights component show ...`') and after code modification (e.g., 'Run the app locally and confirm telemetry appears in the portal').
Include at least one inline executable code snippet or command (e.g., the Azure CLI command to create an App Insights resource) so the main skill body has concrete actionable content rather than purely delegating.
Consolidate the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections with the callout box to reduce redundancy and improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary sections like 'When to Use This Skill' vs 'When to Use azure-prepare Instead' which are somewhat redundant with the callout box. The 'Collect context information' section explains things Claude could infer. However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides a decision tree and references to concrete files (Bicep templates, PowerShell scripts, language-specific guides), but the main body itself lacks executable code or commands. It delegates all concrete guidance to referenced files, 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 should be verification steps (e.g., confirm resource creation succeeded, validate telemetry is flowing). | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to specific guides (auto.md, aspnetcore.md, nodejs.md, python.md), SDK references, Bicep examples, and scripts. Navigation is easy and references are clearly organized by use case. | 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/github-copilot-for-azure
- Commit
a46a937
- 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.