CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-observability-fix

Verify operational incident recovery for Azure web/API or Foundry agents after an actual approved change, using supplied original/post-change evidence and agreed symptom/guardrail thresholds. Not generic code-fix validation, deployment readiness or resource creation. Conceptual questions need no journey. Never deploy, diagnose, run evaluations or infer causation.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/azure-observability/skills/verify-observability-fix/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.

A well-structured specialist workflow with an executable helper command, precise comparison semantics, explicit verdict labels, and appropriate externalization of the evidence contract and fixtures to real bundle files. Its weaknesses are dense, over-hedged prose with redundant prohibition lists repeated across sections, a Windows-specific path in the command, and a shared reference tree that chains beyond one level.

Suggestions

Consolidate the repeated prohibition/permission caveats ("separate appropriately approved workflow", "no new reads/jobs/traffic") into a single boundaries section stated once, cutting the redundant tokens that hurt conciseness.

Replace the Windows-style path "<skill-directory>\scripts\recovery.py" with a cross-platform form (e.g., <skill-directory>/scripts/recovery.py) so the command is copy-paste ready on any host.

Merge or shorten the "Standalone availability gate" and "Current-request intent gate" preamble into a compact entry checklist so the actual step 1-5 workflow sequence is immediately visible and traceable.

DimensionReasoningScore

Conciseness

There is no concept-teaching padding, but prohibition lists repeat across sections: "no new tests, traffic or reads" in the entry section reappears as "not new reads, jobs, traffic or saving", and "separate appropriately approved workflow" appears in sections 2 and 5. Not 2 because all content is skill-specific rather than generic explanation; not 4 because the cross-section redundancy is more than minor and the prose could be tightened considerably.

3 / 5

Actionability

Concrete command (`python "<skill-directory>\scripts\recovery.py" <sanitized-input.json>`), exact comparison semantics ("compare `total / sample_count` against the explicitly agreed bound in each window"), and a concrete verdict enum (VERIFIED_RECOVERED / NOT_RECOVERED / INCONCLUSIVE). Not 5 because input construction is deferred to contract.md and the path uses a Windows-only backslash; not 3 because the guidance is executable rather than pseudocode.

4 / 5

Workflow Clarity

Numbered stages 1-5 clearly sequence scope agreement, evidence acceptance, comparison, reporting, and optional follow-up, with an explicit error feedback loop ("Invalid helper input instead produces a sanitized error/nonzero exit; correct it explicitly, never call it recovered"). Not 5 because the three preamble gate sections before step 1 obscure the entry sequence and some checkpoints are implicit; not 3 because validation checkpoints are largely present.

4 / 5

Progressive Disclosure

The body appropriately externalizes detail to real, one-level-deep, purpose-signaled links ([the evidence contract](references/contract.md), [the fixture](references/fixture.json), [the fixture-p95 fixture](references/fixture-p95.json), scripts/recovery.py), all of which exist in the bundle. Not 5 because references/shared/next-actions.md chains onward to journey-indicator.md and handoff.md, and references/shared/investigation/ nests references and scripts two-plus levels deep; not 3 because references are clearly signaled, not buried, and the right content is split out.

4 / 5

Total

15

/

20

Passed

Description

78%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, niche-scoped description with a clear "what", an explicit "when" (after an actual approved change), and unusually good negative demarcation that minimizes conflict with neighboring skills. The main gaps are a few missing natural trigger synonyms ("fix", "resolved") and the absence of a classic "Use when..." trigger phrase.

DimensionReasoningScore

Specificity

"Verify operational incident recovery ... using supplied original/post-change evidence and agreed symptom/guardrail thresholds" names the domain, method, and explicit exclusions ("Never deploy, diagnose, run evaluations or infer causation"), but centers on a single core action rather than multiple distinct capabilities. Not 5 because coverage is not comprehensive multi-action; not 3 because it goes beyond 1-2 concrete actions with concrete boundary actions.

4 / 5

Completeness

The "what" is clear ("Verify operational incident recovery ... using supplied ... evidence and agreed ... thresholds") and the "when" is explicitly stated ("after an actual approved change"), but there is no "Use when..." style clause with concrete trigger phrases. Not 5 because the trigger guidance, while present, is not phrased as explicit concrete triggers; not 3 because "when" is explicitly stated rather than weakly implied.

4 / 5

Trigger Term Quality

"incident recovery", "Azure web/API", "Foundry agents", and "after an actual approved change" are natural domain phrases a user would say. Not 5 because common variations like "verify the fix", "resolved", or "post-change validation" are absent; not 3 because keyword coverage is genuinely good, not merely "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

"Not generic code-fix validation, deployment readiness or resource creation" and "Never deploy, diagnose, run evaluations or infer causation" carve out a clear niche with explicit negative boundaries against adjacent skills. This matches the anchor for a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

17

/

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/verify-observability-fix/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.