skill
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.
About
# Validate recovery
Experimental, narrow recovery-verification specialist. Instructions guide host behavior; they are **not host enforcement**. Host approvals, restricted tools, and least privilege remain necessary. Skill discovery is not guaranteed routing or deterministic sibling-skill invocation.
## Standalone availability gate
For an admitted task, check availability before reading any cross-skill reference or loading a sibling. Individual installation may omit them. Use available shared instructions unchanged in the bundle; their use below is conditional. Unknown availability follows the missing-reference fallback. Never download, install or attempt a mandatory missing sibling-file read. If shared next-action guidance is absent, run only this local supplied-evidence comparison and return its status, agreed thresholds, guardrails and gaps. Ask for the smallest missing comparable evidence or offer one unexecuted plan-review question when supported; no diagnosis, new reads or edits follow. Missing follow-up specialists are explicit handoff blockers, not recovery proof.
## Current-request intent gate
Before any journey header, diagram, discovery, onboarding question or read, confirm the current request is operational incident recovery, not generic "fix" validation. Other telemetry, monitoring, alerting, health, actual failure or application latency questions can use the appropriate available specialist directly without forcing this comparator or coordinator. Answer conceptual observability questions directly without onboarding/tools. Explicit instrumentation/collection/alert design or setup is relevant even before deployment, but requires an applicable design/setup workflow and normal approvals, never a recovery pass or implicit permission to provision/install/edit. Generic "fix"/"slow" outside application/operational context is insufficient. Resource/app/agent creation, model deployment, RBAC, subscription, cost and general coding/docs are unrelated absent explicit observability intent or actual failure diagnosis. If incidentally loaded, continue the normal task or appropriate available workflow with normal approvals: no observability labels, stepper, tools/questions or coordinator invocation. A topic switch ends presentation; prior investigation is not sticky. Resume only on a relevant current request. Clarify only genuinely ambiguous operational intent with one minimal question before presentation/reads.
Only for an admitted recovery task, at the top of substantive answers, show **Using:** `verify-observability-fix` only when host-loaded and being followed, plus **Stage:** Validate. For local instruction review use **Instructions read:** and **host activation unverified**. Show **Discovered:** only for a relevant skill/tool/MCP actually found, including external skills; state its kind, fit and unverified prerequisites. Discovery and loading are not tool execution or permission. Propose a concrete next action and ask **Allow once** or **Continue with current capabilities** when permission is missing; reuse unexpired covered approval within scope, destination and remaining budget, and preserve declines. Any collection/setup/write belongs to a separately approved workflow, never this evidence-only comparison. Use **Planned tools:** before execution and **Tools used:** only afterward, with actual outcomes; no discovery label authorizes Azure reads here.
## Entry from an investigation or change
Follow [the result-to-next-action contract](references/shared/next-actions.md). A proposed or approved plan without an actual confirmed change stays at **Guide an approved fix**; do not start verification or label it recovered. Confirm the change is effective in the scope being verified. A local edit or local unit validation does not establish deployed behavior. Local-only changes can be compared using supplied local evidence without requiring cloud deployment; no new tests, traffic or reads follow automatically. After an actual approved change, accept an offered comparison or reuse an already accepted verification request without another prompt. A yes/"continue" permits comparison of existing explicitly supplied evidence only, not new reads, jobs, traffic or saving. Missing/stale evidence or unagreed criteria requires the minimal missing supplied input/decision or separately approved collection; report INCONCLUSIVE, never manufacture success. Preserve accepted/ declined next steps, read-only ceilings and explicit stops across handoffs.
Read [the evidence contract](references/contract.md) before constructing input. Use [the fixture](references/fixture.json) only for offline demonstration; its thresholds, scope and results are synthetic, not recommended SLOs. The separate [slow-agent p95 fixture](references/fixture-p95.json) demonstrates source-computed tail latency, not live agent recovery.
## 1. Retain scope and agree the gate
State the selected skill, confirmed environment/targets, incident, actual chang
Install
Run this command
git clone https://github.com/microsoft/azure-skills && cp -r azure-skills/.github/plugins/azure-observability/skills/verify-observability-fix ~/.claude/skills/Works with
Manual steps
Clone the repository and copy the `.github/plugins/azure-observability/skills/verify-observability-fix` folder into your Claude skills directory. Compatible with Claude Code, Cursor, Codex, and any Agent Skills-compatible agent.
Frequently asked questions
What is the Verify Observability Fix skill?
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.
How do I install Verify Observability Fix?
Run this in your terminal:
git clone https://github.com/microsoft/azure-skills && cp -r azure-skills/.github/plugins/azure-observability/skills/verify-observability-fix ~/.claude/skills/Which AI tools does Verify Observability Fix work with?
It works with claude_app, claude_code, claude_api, cursor, codex, windsurf, cline, zed.
Who made Verify Observability Fix?
Microsoft, released under the MIT license.
Is Verify Observability Fix free?
Yes, it is free to use under the MIT license.
git clone https://github.com/anthropics/skills && cp -r skills/skills/claude-api ~/.claude/skills/
npx skills add mattpocock/skills
npx skills add mattpocock/skills
npx skills add mattpocock/skills
npx skills add mattpocock/skills
npx skills add microsoft/azure-skills
Audit before you install
Run any source through our checks - AI visibility, security, performance, and stack detection.
AI Agent / MCP Server Tester
ai testing
Automated Web Security Scan
security
AI Content Quality Test
arabic content
Site Stack Detector
migration
PageSpeed Analyzer
performance
AI SEO / AEO / GEO Audit
ai visibility
llms.txt Generator
ai visibility
Schema / JSON-LD Builder
ai visibility
Readability Score
arabic content
AI Cost Calculator
ai testing
Headline Analyzer
arabic content