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 ./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
Add more specific concrete actions to the capability description, e.g., 'configure custom metrics, set up distributed tracing, add exception 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 | Includes a good range of natural keywords users would say: 'instrument app', 'App Insights SDK', 'telemetry patterns', 'Application Insights', 'instrumentation examples', 'APM best practices'. These cover common variations of how users would phrase requests. | 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-tree document with strong progressive disclosure, directing Claude to the right reference material based on the app's technology stack and hosting environment. Its main weaknesses are the lack of inline executable examples and missing validation/verification steps after instrumentation changes. The content could be tightened by consolidating the 'when to use' sections and removing guidance Claude can infer.
Suggestions
Add at least one inline executable example (e.g., a minimal ASP.NET Core or Node.js instrumentation snippet) so the skill provides immediate actionable guidance without requiring file lookups.
Add explicit validation/verification steps after resource creation and code modification (e.g., 'Verify telemetry is flowing by checking the Application Insights Live Metrics stream' or 'Run the app locally and confirm no SDK initialization errors').
Consolidate the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections into a single concise routing note, since the callout box already covers the key distinction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly 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 callout box about azure-prepare is useful but the dual 'when to use' sections are redundant with it. | 2 / 3 |
Actionability | The skill provides a clear decision tree and references to concrete files (bicep templates, scripts, language-specific guides), but the SKILL.md itself contains no executable code or commands—it delegates everything to referenced files. The guidance is structured but remains at the level of 'see this file' rather than providing copy-paste ready examples inline. | 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. There's no verification step after creating the AppInsights resource or after modifying code (e.g., confirming telemetry is flowing). For an instrumentation workflow involving infrastructure and code changes, missing validation caps this at 2. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The SKILL.md serves as a clear overview/decision tree with well-signaled one-level-deep references to specific guides (auto.md, aspnetcore.md, nodejs.md, python.md), examples (appinsights.bicep), scripts (appinsights.ps1), and SDK references. 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
771a666
- 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.