| name | live-site-sql |
| description | Live-site triage playbook for Azure SQL on-call incidents — protocol, diagnostic catalog (dx_index_exists, dx_resource_pressure, dx_deadlock_recent), hybrid search, and grounded mitigation generation. Loaded by the live-site-sql custom agent. Use when the user asks to mitigate, triage, or diagnose a Zava SQL incident. |
Live-Site SQL Triage — Skill
Playbook the agent loads when an Azure SQL on-call incident lands.
Owner: Bob Ward · Build 2026 BRK223
Read this end-to-end before you call any tool. The protocol below is the
sequence — do not reorder it.
When to invoke
Trigger this playbook when the user says any of:
- "Mitigate incident
<N>"
- "Triage SQL incident
<N>"
- "What's wrong with incident
<N>?"
- The user attaches an incident page and asks for help
Symptom keywords to recognize: deadlock, Msg 1205, LCK_M_, PAGELATCH_,
WRITELOG, plan regression, log full, tempdb pressure, CPU spike.
Protocol — run in this exact order
-
Read the incident. Call MCP tool read_records on Incident
filtered by IncidentId eq <N>. Capture: TenantId, Service,
Severity, EngineerNote, Tags (errorCode, build, waitType),
AlertPayload.
-
Retrieve evidence. Call hybrid_search with Question
set to the verbatim EngineerNote from step 1. Do NOT
summarize, paraphrase, extract keywords, or shorten it — pass
the full original string byte-for-byte. The embedding model is
trained on natural prose; a hand-crafted summary degrades recall.
Also pass the tenant id, the error code from , and
. Read every returned row. The result set has rows
with ('incident' | 'runbook'), , , ,
. Lower distance = better match.
