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

78%

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 ./.github/plugins/azure-observability/skills/troubleshoot-observability/SKILL.md

The canonical home for this skill is troubleshoot-observability in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A disciplined, token-efficient routing skill with explicit intent and availability gates, a concrete need-to-instructions selection table, and genuine progressive disclosure to real reference files. Remaining gaps are second-level nesting under the investigation bundle, a few undefined abstract terms, and an implicit rather than enumerated workflow sequence.

Suggestions

Define or drop in-body abstractions like 'consumed/remaining budgets' and 'scope/window', or link the reference that defines them, so every directive is self-contained.

Flatten or surface the investigation bundle's nested references/ and scripts/ (e.g. mention query_prometheus.py where trace querying is routed) to keep all references one level deep.

DimensionReasoningScore

Conciseness

The body is dense and unpadded with no explanations of concepts Claude already knows, but the availability-gate section restates the missing-reference rule several ways ('Never download, install or attempt a mandatory missing sibling-file read' vs. 'Missing external instructions do not block... or imply permission to install'), so a few sentences could be merged. Anchor 4 ('efficient; minor instances that could be trimmed') fits; the redundancy keeps it below the lean anchor 5.

4 / 5

Actionability

The 'Select one path' table is decision-ready with concrete named targets (e.g. 'Named alert, failure, slow operation or selected finding' → investigation/README.md) and explicit rules like 'never auto-select rank 1 or reassess'. Some directives remain abstract and undefined in-body ('consumed/remaining budgets', 'Retain scope/window, evidence and budgets'), which is the minor gap separating anchor 4 from fully executable anchor 5, while clearly exceeding anchor 3's incomplete guidance.

4 / 5

Workflow Clarity

Gates are explicitly ordered and checkpointed ('On every user turn, before any journey header... confirm a current operational observability request'; availability check before reading any cross-skill reference; dependency-selection checkpoint), with distinct failure handling ('Missing/denied/empty/stale/partial/failed/throttled evidence remains distinct; insufficient evidence is INCONCLUSIVE'). This fits anchor 4's 'clear sequence with most checkpoints'; the sequence is implicit rather than enumerated with an explicit checklist, so not a 5.

4 / 5

Progressive Disclosure

The body is a lean overview whose links (references/intent.md, canonical-dependencies.md, investigation/README.md, scope-permissions.md, selection.md, next-actions.md, monitoring-follow-up.md, journey-indicator.md) all resolve to real one-level-deep files, clearly signaled by a routing table — good structure per anchor 4. Not a 5 because the investigation sub-bundle nests its own references/ and scripts/ two levels deep (references/investigation/references/, scripts/query_prometheus.py), and several siblings (specialists.md, matching.md, trace-capabilities.md) are reachable only indirectly via selection.md — minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

75%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 well-scoped, third-person description with an explicit 'Use for' clause and clear negative boundaries. It covers many specific capability areas but leans on abstract nouns over concrete actions and misses common trigger synonyms such as logs, metrics, or Application Insights.

Suggestions

Add concrete user-utterance triggers to the when-clause, e.g. 'Use when the user reports a slow or failing app, missing telemetry, or a firing alert', to reach explicit trigger-phrase completeness.

Include common natural synonyms among the trigger terms: 'logs', 'metrics', 'traces', and 'Application Insights'.

DimensionReasoningScore

Specificity

Names the domain ('Coordinate Azure observability troubleshooting') and enumerates several specific capability areas — 'runtime failures, operational latency, telemetry, monitoring, alerts, evidence-backed fixes and recovery' — matching the 'lists several specific actions; minor gaps' anchor. It is not a 5 because the capabilities are mostly abstract nouns rather than concrete executable actions.

4 / 5

Completeness

Both parts are present: a clear what ('Coordinate Azure observability troubleshooting... evidence-backed fixes and recovery') and an explicit when ('Use for an end-to-end observability investigation or explicit instrumentation, collection or alerting guidance'). It fits anchor 4 exactly — the when-clause is abstract policy language rather than the concrete trigger phrases required for a 5, and it is clearly above anchor 3's 'when missing or only weakly implied'.

4 / 5

Trigger Term Quality

Natural user terms are well covered: 'health', 'runtime failures', 'operational latency', 'telemetry', 'monitoring', 'alerts', matching 'good keyword coverage; a few natural terms missing'. Not a 5 because common synonyms users would say — 'logs', 'metrics', 'traces', 'Application Insights' — are absent.

4 / 5

Distinctiveness Conflict Risk

The Azure observability niche plus explicit exclusions ('Not general resource/app/agent creation, model deployment, RBAC, cost or coding') sharply limit conflict risk, fitting 'mostly distinct; minor overlap risk'. Not a 5 because plausible overlap remains with closely related Azure diagnostics or general monitoring skills.

4 / 5

Total

16

/

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/azure-skills

Path

.github/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.