appinsights-instrumentation
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. USE FOR: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices. DO NOT USE FOR: adding App Insights to my app (use azure-prepare), add telemetry to my project (use azure-prepare), add monitoring (use azure-prepare). This skill provides guidance—azure-prepare orchestrates component changes.
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill appinsights-instrumentation84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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-crafted description with excellent trigger term coverage and explicit guidance on when to use (and not use) the skill. The DO NOT USE FOR clause is particularly valuable for preventing conflicts with related skills. The main weakness is that the capability description could be more specific about concrete actions beyond general categories like 'telemetry patterns'.
Suggestions
Enhance specificity by listing concrete actions like 'configure custom metrics, set up distributed tracing, implement exception tracking, configure sampling rates' instead of general categories.
| 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 specific actions like 'configure custom metrics, set up distributed tracing, implement exception tracking'. | 2 / 3 |
Completeness | Clearly answers both what (provides telemetry patterns, SDK setup, configuration references) and when (explicit USE FOR clause with trigger terms). Also includes helpful DO NOT USE FOR guidance to prevent misuse, and clarifies the distinction from azure-prepare skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'instrument app', 'App Insights SDK', 'telemetry patterns', 'what is App Insights', 'Application Insights guidance', 'instrumentation examples', 'APM best practices'. The explicit USE FOR and DO NOT USE FOR clauses provide comprehensive trigger guidance. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally clear niche with explicit boundary definitions. The DO NOT USE FOR clause directly addresses potential conflicts with azure-prepare, and the final sentence clarifies the distinction: 'This skill provides guidance—azure-prepare orchestrates component changes.' | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid workflow guidance with excellent progressive disclosure to detailed reference materials. The main weaknesses are some redundancy in the routing sections and a lack of inline executable examples—the skill relies heavily on external files for concrete implementation details. The decision tree structure is clear and appropriate for a guidance-focused skill.
Suggestions
Consolidate the 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections into a single routing table to reduce redundancy
Add at least one minimal inline code snippet showing basic SDK initialization to improve actionability without requiring navigation to reference files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy between 'When to Use This Skill' and 'When to Use azure-prepare Instead' sections, and the warning box repeats information. However, it generally avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides clear decision trees and references to external files, but lacks inline executable code examples. The guidance is mostly 'see X file' rather than concrete copy-paste ready instructions in the main skill. | 2 / 3 |
Workflow Clarity | Clear multi-step workflow: collect context → determine instrumentation type (auto vs manual) → create resource → modify code. Decision points are explicit with clear branching based on app type and hosting environment. | 3 / 3 |
Progressive Disclosure | Excellent structure with overview in main file and well-signaled one-level-deep references to specific guides (AUTO, ASPNETCORE, NODEJS, PYTHON) and SDK references. Navigation is clear and organized. | 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.
- 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.