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.
Install with Tessl CLI
npx tessl i github:microsoft/azure-skills --skill appinsights-instrumentation82
Quality
73%
Does it follow best practices?
Impact
96%
1.54xAverage score across 3 eval scenarios
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 well-structured skill description with explicit trigger guidance via the 'WHEN:' clause and good keyword coverage for discoverability. The main weakness is that the capability description could be more specific about concrete actions beyond general categories like 'telemetry patterns' and 'SDK setup'. The description successfully differentiates itself through Azure Application Insights-specific terminology.
Suggestions
Expand specificity by listing concrete actions like 'configure custom metrics, track exceptions, set up distributed tracing, implement request correlation'
| 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 | Includes 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 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
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/orchestration document with good progressive disclosure and clear navigation to detailed references. However, it lacks inline actionable examples and validation checkpoints, making it more of a decision tree than a hands-on guide. The content could be more concise by consolidating the 'when to use' sections.
Suggestions
Add a validation step after instrumentation (e.g., 'Verify telemetry is flowing: check Azure Portal > App Insights > Live Metrics within 5 minutes')
Include at least one minimal inline code example for the most common case (e.g., ASP.NET Core SDK initialization) rather than delegating all code to references
Consolidate the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections into a single decision table or flowchart
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., 'When to Use This Skill' vs 'When to Use azure-prepare Instead' sections overlap conceptually). The routing guidance is useful but could be more compact. | 2 / 3 |
Actionability | Provides direction to reference files and general guidance but lacks concrete executable examples inline. The actual code/commands are delegated to referenced files rather than shown directly, making this more of a routing document than actionable instructions. | 2 / 3 |
Workflow Clarity | The workflow has clear steps (collect context → choose auto vs manual → create resource → modify code) but lacks explicit validation checkpoints. No verification steps after creating AppInsights resource or after code modification to confirm successful instrumentation. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to specific guides (AUTO, ASPNETCORE, NODEJS, PYTHON) and SDK references. Navigation is well-organized with a quick reference section at the bottom. | 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.
- 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.