CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

troubleshoot-observability

Coordinate Azure observability troubleshooting for application or agent health, runtime failures, operational latency, telemetry, monitoring, alerts, evidence-backed fixes and recovery. Use for an end-to-end observability investigation or explicit instrumentation, collection or alerting guidance. Not general resource/app/agent creation, model deployment, RBAC, cost or coding. Conceptual questions need no journey; explicit specialist requests stay direct. Actions require applicable approval.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/azure-observability/skills/troubleshoot-observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a disciplined, token-efficient routing overview with a genuinely useful need-to-instruction table and correct, existing references. Its weakness is actionability: beyond the routing table, the guidance is largely abstract policy language with no commands, examples, or concrete walk-throughs, leaving execution detail entirely to the referenced files, and the reference tree nests two levels deep via the investigation sub-bundle.

Suggestions

Add one short concrete worked example to the body (e.g. a sample user report like 'My API is slow' traced through the intent gate to one table row and its reference) so the routing policy is grounded in an executable pattern rather than abstract prose.

Consolidate the repeated availability/dependency rules ('never download or install', 'not bundled does not mean unavailable', 'unknown discovery is not confirmed absence') into a single stated rule with the variants as brief sub-points, freeing tokens for actionable detail.

Surface the investigation sub-bundle's second-level references (trace-query-patterns.md, confidence-assessment.md, etc.) as a short annotated list inside the investigation README's entry point in the routing table, so the two-hop structure is visible from the top level.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no concept explanations, no padding — e.g. "This is instruction-guided routing, not a diagnostics engine or permission sandbox." It misses 5 because the standalone-availability and dependency sections restate the same idea several ways ("Never download, install or attempt a mandatory missing sibling-file read" / "Not bundled does not mean unavailable" / "unknown discovery is not confirmed absence"), which could be tightened into one rule.

4 / 5

Actionability

The "Select one path" routing table is concrete and executable (need → specific reference or skill), and fallbacks are named ("On reported rendering failure use its text fallback"). But most other guidance is abstract policy prose — "Retain scope/window, evidence and budgets", "Discover actual operations and access; no guessed tool names" — with no commands, examples, or concrete scenarios, and key execution detail is deferred to reference files; this matches level 3's 'some concrete guidance but incomplete, missing key details' rather than level 4's mostly-executable guidance.

3 / 5

Workflow Clarity

The sequence is clear and ordered — intent gate "On every user turn, before any journey header", then the availability gate "For an admitted task", then the path-selection table covering the full lifecycle through verification and monitoring follow-up — with explicit checkpoints ("Ask for selection; never auto-select rank 1", "Apply next actions at a substantive result or plan review") and fallbacks for failure states. It stops short of 5 because validation feedback loops (what to do when a step's evidence is partial or a handoff is blocked mid-flow) are implied rather than explicitly looped.

4 / 5

Progressive Disclosure

The body is a lean overview with a well-signaled routing table; every referenced path (intent.md, canonical-dependencies.md, investigation/README.md, scope-permissions.md, selection.md, next-actions.md, monitoring-follow-up.md, journey-indicator.md) exists in the bundle, and links are contextual rather than buried. It misses 5 because references are not one level deep: the investigation sub-bundle's README.md chains onward into its own references/ and scripts/ directories (e.g. trace-query-patterns.md, query_prometheus.py), a two-hop structure the top-level anchors treat as less than ideal.

4 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly states what the skill does, when to use it, and what it does not cover, with good natural trigger terms and active conflict-reduction. The main gap is verb-level specificity — capabilities are listed as noun phrases under one coordinating verb — and a few missing Azure-observability synonyms like logs, metrics, and Application Insights.

DimensionReasoningScore

Specificity

The description enumerates several concrete capability areas — "application or agent health, runtime failures, operational latency, telemetry, monitoring, alerts, evidence-backed fixes and recovery" — comparable to the level-4 anchor's list of specific actions. It falls short of 5 because the single verb "Coordinate" carries all the action; the rest are noun phrases, so coverage of what is actually done (query, analyze, propose fixes, verify) is implied rather than stated.

4 / 5

Completeness

Both halves are explicitly answered: what — "Coordinate Azure observability troubleshooting for ... evidence-backed fixes and recovery"; when — "Use for an end-to-end observability investigation or explicit instrumentation, collection or alerting guidance", plus explicit negative boundaries ("Not general resource/app/agent creation, model deployment, RBAC, cost or coding"). This matches the level-5 anchor's clear and explicit what-and-when with concrete trigger phrases; level 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Strong natural terms users would say are present: "runtime failures", "operational latency", "telemetry", "monitoring", "alerts", "health". It misses common Azure-observability synonyms and product names a user would naturally mention — "logs", "metrics", "traces", "Application Insights", "Log Analytics" — so it does not reach the comprehensive synonym coverage of level 5, but clearly exceeds the partial coverage of level 3.

4 / 5

Distinctiveness Conflict Risk

"Azure observability" is a clear niche and the description actively reduces overlap with explicit carve-outs ("Not general resource/app/agent creation, model deployment, RBAC, cost or coding") and routing hints ("Conceptual questions need no journey; explicit specialist requests stay direct"). Minor residual overlap with a general azure-diagnostics skill exists, but triggers are distinct, matching level 5.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/GitHub-Copilot-for-Azure

Path

plugins/azure-observability/skills/troubleshoot-observability/SKILL.md

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.