azure-observability
Azure Observability Services including Azure Monitor, Application Insights, Log Analytics, Alerts, and Workbooks. Provides metrics, APM, distributed tracing, KQL queries, and interactive reports. USE FOR: Azure Monitor, Application Insights, Log Analytics, Alerts, Workbooks, metrics, APM, distributed tracing, KQL queries, interactive reports, observability, monitoring dashboards. DO NOT USE FOR: instrumenting apps with App Insights SDK (use appinsights-instrumentation), querying Kusto/ADX clusters (use azure-kusto), cost analysis (use azure-cost-optimization).
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-observability95
Does it follow best practices?
Validation for skill structure
Discovery
100%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 an excellent skill description that follows best practices. It provides specific capabilities, comprehensive trigger terms, explicit usage guidance with both positive and negative triggers, and clear differentiation from related skills. The third-person voice is used correctly throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'metrics, APM, distributed tracing, KQL queries, and interactive reports' along with specific Azure services (Monitor, Application Insights, Log Analytics, Alerts, Workbooks). | 3 / 3 |
Completeness | Clearly answers both what (Azure observability services with specific capabilities) and when with explicit 'USE FOR:' triggers. Additionally includes 'DO NOT USE FOR:' guidance which helps Claude distinguish when to select other skills instead. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Azure Monitor', 'Application Insights', 'Log Analytics', 'KQL queries', 'observability', 'monitoring dashboards', 'APM', 'distributed tracing' - these are all terms users naturally use when working with Azure observability. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear boundaries. The 'DO NOT USE FOR:' section explicitly differentiates from related skills (appinsights-instrumentation, azure-kusto, azure-cost-optimization), minimizing conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted reference skill that efficiently covers Azure observability services with actionable commands and queries. The table-based organization and clear SDK/documentation references demonstrate excellent progressive disclosure. The main weakness is the lack of explicit workflows for common monitoring scenarios (e.g., 'how to investigate a production issue' or 'how to set up alerting').
Suggestions
Add a brief workflow section for common scenarios like 'Investigating production errors' with sequenced steps (check App Insights → query logs → review metrics)
Include validation steps for alert configuration to ensure alerts are properly triggered before relying on them in production
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding explanations of concepts Claude already knows. Every section serves a clear purpose without padding. | 3 / 3 |
Actionability | Provides fully executable CLI commands, complete KQL queries, and specific MCP tool commands with exact syntax. All examples are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The content is well-organized as a reference but lacks explicit workflow sequences for common monitoring tasks. No validation checkpoints or feedback loops for operations like setting up alerts or configuring monitoring. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview tables, well-signaled one-level-deep references to SDK guides and external documentation, and appropriate separation of concerns (setup directed to separate skill, deep docs linked externally). | 3 / 3 |
Total | 11 / 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.