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.
79
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/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 and patterns it covers, rather than using somewhat general 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 is well-structured as a routing and reference document with excellent progressive disclosure and clear navigation to detailed guides. However, it lacks concrete executable examples in the main body, relying entirely on referenced files for actionable content. Adding a validation/verification step after instrumentation and including at least one inline code snippet would strengthen it significantly.
Suggestions
Add a verification/validation step at the end of the workflow (e.g., 'Verify telemetry is flowing by checking the Azure Portal Live Metrics or running a test request and confirming it appears in Application Insights')
Include at least one minimal inline code example (e.g., a 3-line ASP.NET Core or Node.js setup snippet) so the skill provides some immediately actionable content without requiring reference file loading
Trim the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections—these are routing concerns that could be condensed into the existing callout box at the top
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary content like explaining when to use this skill vs azure-prepare (which is more routing logic than skill content), and the 'Prerequisites' section stating obvious constraints. The 'Collect context information' section explains things Claude could infer. | 2 / 3 |
Actionability | Provides structured guidance with clear references to specific files (bicep templates, scripts, language-specific guides), but the skill itself contains no executable code or concrete examples—it's entirely a routing/decision document that delegates all actual instructions to referenced files. | 2 / 3 |
Workflow Clarity | The manual instrumentation workflow has a clear two-step sequence (create resource, modify code) with decision points, but lacks validation checkpoints. There's no step to verify the instrumentation is working (e.g., checking telemetry appears in Azure Portal), which is important for a multi-step process involving infrastructure and code changes. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, well-organized reference table with 'When to Load' guidance, SDK quick references with direct links, and explicit instruction to load references on demand. One level deep, clearly signaled. | 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
- jonathan-vella/azure-agentic-infraops
- Commit
ec7b8ff
- 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.