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

79%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 delivers a rigorously sequenced, highly actionable read-only comparison workflow with explicit validation checkpoints and a clear verdict contract, supported by real, well-signaled one-level references. Its main cost is token efficiency: repetitive guardrail restatements and dense compound sentences make it harder to parse than the underlying rules require.

Suggestions

Consolidate the repeated no-read/no-deploy/no-collect guardrails (currently restated in the availability gate, intent gate, section 2, and section 5) into a single scope-constraints statement referenced from each section.

Break the long compound-negation sentences (e.g. 'A yes/"continue" permits comparison of existing explicitly supplied evidence only, not new reads, jobs, traffic or saving') into short bullet constraints to improve parseability at the same token cost.

Use a platform-neutral path in the invocation (e.g. 'python "<skill-directory>/scripts/recovery.py"') so the command is executable on POSIX systems as well as Windows.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and nearly every sentence carries a rule, but it is noticeably padded with repetition: the no-read/no-deploy/no-collect guardrails are restated across the availability gate, intent gate, section 2, and section 5, and long compound-negation sentences (e.g. 'A yes/"continue" permits comparison of existing explicitly supplied evidence only, not new reads, jobs, traffic or saving') could be tightened. It fits anchor 3 (mostly efficient but could be tightened) better than anchor 2, since the excess is redundancy rather than irrelevant explanation.

3 / 5

Actionability

Concrete, executable guidance throughout: an exact invocation ('python "<skill-directory>\scripts\recovery.py" <sanitized-input.json>'), explicit arithmetic rules ('compare total / sample_count against the explicitly agreed bound', 'compare the explicitly supplied source-computed percentile_value directly'), and a definitive verdict enum (VERIFIED_RECOVERED / NOT_RECOVERED / INCONCLUSIVE). Minor gaps keep it from anchor 5: the path uses a Windows-only backslash separator, and no worked input example is shown inline (deferred to contract.md and fixtures).

4 / 5

Workflow Clarity

A clear sequence (availability gate, intent gate, entry contract, then numbered steps 1-5 from scope agreement through reporting to optional follow-up) with explicit validation checkpoints: thresholds agreed with the task owner 'before execution', original-window/post-window chronology rules, INCONCLUSIVE on missing or ambiguous evidence, and an error-recovery loop ('Invalid helper input instead produces a sanitized error/nonzero exit; correct it explicitly, never call it recovered'). Verdict precedence rules are explicit, matching anchor 5.

5 / 5

Progressive Disclosure

Direct references are real files, one level deep, and each is clearly signaled with its purpose ('Read the evidence contract before constructing input'; fixtures marked as 'synthetic, not recommended SLOs'; the helper script's constraints stated inline). Minor gaps: a large amount of dense policy is inlined in SKILL.md that could live in a reference, and the shared/ tree (next-actions.md chaining to handoff.md, trace-capabilities.md, and a nested investigation/ subtree with its own references/ and scripts/) creates 2+ level chains, consistent with anchor 4 rather than 5.

4 / 5

Total

16

/

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 precise, well-bounded description that clearly delimits a narrow verification niche with strong negative boundaries and minimal conflict risk. Its main weaknesses are the absence of 'Use when...' trigger phrasing and natural user synonym coverage, which leave the completeness and trigger-term dimensions short of the top anchor.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks to verify or confirm recovery after an approved Azure or Foundry change was deployed.'

Include common user phrasings as trigger terms, such as 'did the fix work', 'is the incident resolved', or 'post-deployment verification', and drop internal jargon like 'need no journey'.

DimensionReasoningScore

Specificity

The description names a concrete action ('Verify operational incident recovery') with a specific method ('using supplied original/post-change evidence and agreed symptom/guardrail thresholds') and scope ('Azure web/API or Foundry agents'), plus explicit exclusions. It falls between anchor 3 (1-2 concrete actions, not comprehensive) and anchor 4 (several specific actions) — the action set is narrow but each element is concrete, placing it noticeably above the midpoint.

4 / 5

Completeness

Both what and when are explicitly stated: the what ('Verify operational incident recovery... using supplied original/post-change evidence and agreed symptom/guardrail thresholds') and the when ('after an actual approved change') plus explicit negative triggers ('Not generic code-fix validation, deployment readiness or resource creation'). It lacks a 'Use when...' clause with concrete user trigger phrases, so the 'when' could be more explicit, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present ('incident recovery', 'verify', 'Azure', 'Foundry agents', 'symptom', 'approved change'), giving good keyword coverage. Common variations like 'did the fix work', 'post-deployment check', or 'is it healthy now' are missing, and 'Conceptual questions need no journey' uses internal jargon, so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (post-change recovery verification for Azure web/API or Foundry agents against agreed thresholds) with explicit exclusions ('Not generic code-fix validation, deployment readiness or resource creation'; 'Never deploy, diagnose, run evaluations or infer causation') that sharply separate it from adjacent skills. Minimal conflict risk, matching anchor 5.

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

Path

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