live-site-sql Skill
Live-site triage playbook for Azure SQL on-call incidents — protocol, diagnostic catalog (dxindexexists, dxresourcepressure, dxdeadlockrecent), 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. Published by microsoft in Build26-BRK223-from-rows-to-reasoning-designing-databases-for-ai-apps-and-agents.
What is live-site-sql Skill?
Live-site triage playbook for Azure SQL on-call incidents — protocol, diagnostic catalog (dxindexexists, dxresourcepressure, dxdeadlockrecent), 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. Published by microsoft in Build26-BRK223-from-rows-to-reasoning-designing-databases-for-ai-apps-and-agents. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Database workflows
- Research
- Database workflows use cases
- Research use cases
Technical details
- Install or run with Copy skill directory
When to use live-site-sql Skill
- Use it for database workflows.
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Build26-BRK223-from-rows-to-reasoning-designing-databases-for-ai-apps-and-agents
- Skill file: .github/skills/live-site-sql/SKILL.md
What it does
Live-site triage playbook for Azure SQL on-call incidents — protocol, diagnostic catalog (dxindexexists, dxresourcepressure, dxdeadlockrecent), 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.
Skill instructions
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, LCKM, PAGELATCH, WRITELOG, plan regression, log full, tempdb pressure, CPU spike. Protocol — run in this exact order 1. Read the incident. Call MCP tool readrecords on Incident filtered by IncidentId eq <N. Capture: TenantId, Service, Severity, EngineerNote, Tags (errorCode, build, waitType), AlertPayload. 2. Retrieve evidence. Call hybridsearch with Question set to the verbatim EngineerNote from step 1. Do NOT summarize, paraphrase, extract keywords, or shorten it — pass the full original string by
Explore related resources
Frequently asked questions
What is live-site-sql?
live-site-sql is a open-source AI agent skill with Copy skill directory. Live-site triage playbook for Azure SQL on-call incidents — protocol, diagnostic catalog (dxindexexists, dxresourcepressure, dxdeadlockrecent), hybrid search, and grounded mitigation generation.
Who is live-site-sql best for?
live-site-sql is best for reusing agent instructions, scripts, and references, database workflows, research workflows.
How do I install live-site-sql?
Install or run live-site-sql using Copy skill directory. Check live-site-sql for the latest setup command.
Is live-site-sql actively maintained?
live-site-sql may need a closer maintenance check before production use.
Auto-fetched from GitHub.
