[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-incidentpostmortemgenerator":3,"mdc-7r2rws-key":39,"related-repo-azure-incidentpostmortemgenerator":492,"related-org-azure-incidentpostmortemgenerator":630},{"slug":4,"name":5,"fn":6,"description":7,"org":8,"tags":13,"stars":28,"repoUrl":29,"updatedAt":30,"license":31,"forks":32,"topics":33,"repo":34,"sourceUrl":37,"mdContent":38},"incidentpostmortemgenerator","incident_postmortem_generator","generate incident postmortem reports","Generate a blameless incident postmortem from the current or recent SRE Agent investigation. Use after an incident is resolved, when asked for a postmortem, RCA report, or lessons learned document.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},"azure","Azure (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fazure.png","Azure",[14,18,21,22,25],{"name":15,"slug":16,"type":17},"SRE","sre","tag",{"name":19,"slug":20,"type":17},"Operations","operations",{"name":12,"slug":9,"type":17},{"name":23,"slug":24,"type":17},"Documentation","documentation",{"name":26,"slug":27,"type":17},"Incident Response","incident-response",2,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fsre-agent-plugins","2026-08-23T04:00:12.143462",null,8,[],{"repoUrl":29,"stars":28,"forks":32,"topics":35,"description":36},[],"Azure SRE Agent Plugins","https:\u002F\u002Fgithub.com\u002FAzure\u002Fsre-agent-plugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fazure-proactive-operations\u002Fskills\u002Fincident_postmortem_generator","---\nname: incident_postmortem_generator\ndescription: Generate a blameless incident postmortem from the current or recent SRE Agent investigation. Use after an incident is resolved, when asked for a postmortem, RCA report, or lessons learned document.\n---\n\n# Incident Postmortem Generator\n\n## Purpose\n\nAutomatically generate a structured, blameless postmortem document from the context of a resolved incident investigation.\n\n## Principles\n\n- **Blameless**: Focus on systems and processes, never individuals\n- **Evidence-based**: Every claim backed by data (logs, metrics, timeline)\n- **Action-oriented**: Every finding leads to a concrete action item\n\n## Procedure\n\n### Step 1: Gather incident context\n\nFrom the current conversation and agent memory, extract:\n- Incident ID, severity, duration, affected services, impacted users\n- Timeline: issue start, detection, acknowledgment, mitigation, resolution\n- Root cause and contributing factors\n\n### Step 2: Assess detection and response\n\n| Metric | Description |\n|--------|-------------|\n| Time to detect (TTD) | Issue start to alert firing |\n| Time to acknowledge (TTA) | Alert to human engagement |\n| Time to mitigate (TTM) | Engagement to mitigation |\n| Time to resolve (TTR) | Total duration |\n\n### Step 3: Five Whys analysis\n\nApply the 5 Whys technique to the root cause to identify systemic issues.\n\n### Step 4: Generate action items\n\nFor each finding, create a SMART action item with owner, priority, and due date. Categories: prevent recurrence, improve detection, improve response, improve resilience.\n\n### Step 5: Compile postmortem\n\nGenerate the full document with: executive summary, impact, timeline, root cause, Five Whys, detection assessment, what went well, what could be improved, action items, and lessons learned.\n\n## Sample output\n\n| Field | Value |\n|-------|-------|\n| Incident Date | 2026-07-10 |\n| Severity | Sev-2 |\n| Duration | 1h 23m |\n\n**Summary**: payment-service returned HTTP 500 errors for 1h 23m due to OOM-killed pod. Root cause: memory leak in connection pool from release v2.14.0. Impact: ~340 failed transactions, 120 customers.\n\n| Metric | Value | Target | Status |\n|--------|-------|--------|--------|\n| TTD | 6m | \u003C5m | ⚠️ |\n| TTA | 4m | \u003C15m | ✅ |\n| TTM | 28m | \u003C30m | ✅ |\n| TTR | 1h 23m | \u003C2h | ✅ |\n\n## References\n\n- Postmortem Culture: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fwell-architected\u002Foperational-excellence\u002Fmitigation-strategy\n- Azure Resource Health: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fservice-health\u002Fresource-health-overview\n",{"data":40,"body":41},{"name":5,"description":7},{"type":42,"children":43},"root",[44,53,60,66,72,108,114,121,126,144,150,230,236,241,247,252,258,263,269,330,340,459,465],{"type":45,"tag":46,"props":47,"children":49},"element","h1",{"id":48},"incident-postmortem-generator",[50],{"type":51,"value":52},"text","Incident Postmortem Generator",{"type":45,"tag":54,"props":55,"children":57},"h2",{"id":56},"purpose",[58],{"type":51,"value":59},"Purpose",{"type":45,"tag":61,"props":62,"children":63},"p",{},[64],{"type":51,"value":65},"Automatically generate a structured, blameless postmortem document from the context of a resolved incident investigation.",{"type":45,"tag":54,"props":67,"children":69},{"id":68},"principles",[70],{"type":51,"value":71},"Principles",{"type":45,"tag":73,"props":74,"children":75},"ul",{},[76,88,98],{"type":45,"tag":77,"props":78,"children":79},"li",{},[80,86],{"type":45,"tag":81,"props":82,"children":83},"strong",{},[84],{"type":51,"value":85},"Blameless",{"type":51,"value":87},": Focus on systems and processes, never individuals",{"type":45,"tag":77,"props":89,"children":90},{},[91,96],{"type":45,"tag":81,"props":92,"children":93},{},[94],{"type":51,"value":95},"Evidence-based",{"type":51,"value":97},": Every claim backed by data (logs, metrics, timeline)",{"type":45,"tag":77,"props":99,"children":100},{},[101,106],{"type":45,"tag":81,"props":102,"children":103},{},[104],{"type":51,"value":105},"Action-oriented",{"type":51,"value":107},": Every finding leads to a concrete action item",{"type":45,"tag":54,"props":109,"children":111},{"id":110},"procedure",[112],{"type":51,"value":113},"Procedure",{"type":45,"tag":115,"props":116,"children":118},"h3",{"id":117},"step-1-gather-incident-context",[119],{"type":51,"value":120},"Step 1: Gather incident context",{"type":45,"tag":61,"props":122,"children":123},{},[124],{"type":51,"value":125},"From the current conversation and agent memory, extract:",{"type":45,"tag":73,"props":127,"children":128},{},[129,134,139],{"type":45,"tag":77,"props":130,"children":131},{},[132],{"type":51,"value":133},"Incident ID, severity, duration, affected services, impacted users",{"type":45,"tag":77,"props":135,"children":136},{},[137],{"type":51,"value":138},"Timeline: issue start, detection, acknowledgment, mitigation, resolution",{"type":45,"tag":77,"props":140,"children":141},{},[142],{"type":51,"value":143},"Root cause and contributing factors",{"type":45,"tag":115,"props":145,"children":147},{"id":146},"step-2-assess-detection-and-response",[148],{"type":51,"value":149},"Step 2: Assess detection and response",{"type":45,"tag":151,"props":152,"children":153},"table",{},[154,173],{"type":45,"tag":155,"props":156,"children":157},"thead",{},[158],{"type":45,"tag":159,"props":160,"children":161},"tr",{},[162,168],{"type":45,"tag":163,"props":164,"children":165},"th",{},[166],{"type":51,"value":167},"Metric",{"type":45,"tag":163,"props":169,"children":170},{},[171],{"type":51,"value":172},"Description",{"type":45,"tag":174,"props":175,"children":176},"tbody",{},[177,191,204,217],{"type":45,"tag":159,"props":178,"children":179},{},[180,186],{"type":45,"tag":181,"props":182,"children":183},"td",{},[184],{"type":51,"value":185},"Time to detect (TTD)",{"type":45,"tag":181,"props":187,"children":188},{},[189],{"type":51,"value":190},"Issue start to alert firing",{"type":45,"tag":159,"props":192,"children":193},{},[194,199],{"type":45,"tag":181,"props":195,"children":196},{},[197],{"type":51,"value":198},"Time to acknowledge (TTA)",{"type":45,"tag":181,"props":200,"children":201},{},[202],{"type":51,"value":203},"Alert to human engagement",{"type":45,"tag":159,"props":205,"children":206},{},[207,212],{"type":45,"tag":181,"props":208,"children":209},{},[210],{"type":51,"value":211},"Time to mitigate (TTM)",{"type":45,"tag":181,"props":213,"children":214},{},[215],{"type":51,"value":216},"Engagement to mitigation",{"type":45,"tag":159,"props":218,"children":219},{},[220,225],{"type":45,"tag":181,"props":221,"children":222},{},[223],{"type":51,"value":224},"Time to resolve (TTR)",{"type":45,"tag":181,"props":226,"children":227},{},[228],{"type":51,"value":229},"Total duration",{"type":45,"tag":115,"props":231,"children":233},{"id":232},"step-3-five-whys-analysis",[234],{"type":51,"value":235},"Step 3: Five Whys analysis",{"type":45,"tag":61,"props":237,"children":238},{},[239],{"type":51,"value":240},"Apply the 5 Whys technique to the root cause to identify systemic issues.",{"type":45,"tag":115,"props":242,"children":244},{"id":243},"step-4-generate-action-items",[245],{"type":51,"value":246},"Step 4: Generate action items",{"type":45,"tag":61,"props":248,"children":249},{},[250],{"type":51,"value":251},"For each finding, create a SMART action item with owner, priority, and due date. Categories: prevent recurrence, improve detection, improve response, improve resilience.",{"type":45,"tag":115,"props":253,"children":255},{"id":254},"step-5-compile-postmortem",[256],{"type":51,"value":257},"Step 5: Compile postmortem",{"type":45,"tag":61,"props":259,"children":260},{},[261],{"type":51,"value":262},"Generate the full document with: executive summary, impact, timeline, root cause, Five Whys, detection assessment, what went well, what could be improved, action items, and lessons learned.",{"type":45,"tag":54,"props":264,"children":266},{"id":265},"sample-output",[267],{"type":51,"value":268},"Sample output",{"type":45,"tag":151,"props":270,"children":271},{},[272,288],{"type":45,"tag":155,"props":273,"children":274},{},[275],{"type":45,"tag":159,"props":276,"children":277},{},[278,283],{"type":45,"tag":163,"props":279,"children":280},{},[281],{"type":51,"value":282},"Field",{"type":45,"tag":163,"props":284,"children":285},{},[286],{"type":51,"value":287},"Value",{"type":45,"tag":174,"props":289,"children":290},{},[291,304,317],{"type":45,"tag":159,"props":292,"children":293},{},[294,299],{"type":45,"tag":181,"props":295,"children":296},{},[297],{"type":51,"value":298},"Incident Date",{"type":45,"tag":181,"props":300,"children":301},{},[302],{"type":51,"value":303},"2026-07-10",{"type":45,"tag":159,"props":305,"children":306},{},[307,312],{"type":45,"tag":181,"props":308,"children":309},{},[310],{"type":51,"value":311},"Severity",{"type":45,"tag":181,"props":313,"children":314},{},[315],{"type":51,"value":316},"Sev-2",{"type":45,"tag":159,"props":318,"children":319},{},[320,325],{"type":45,"tag":181,"props":321,"children":322},{},[323],{"type":51,"value":324},"Duration",{"type":45,"tag":181,"props":326,"children":327},{},[328],{"type":51,"value":329},"1h 23m",{"type":45,"tag":61,"props":331,"children":332},{},[333,338],{"type":45,"tag":81,"props":334,"children":335},{},[336],{"type":51,"value":337},"Summary",{"type":51,"value":339},": payment-service returned HTTP 500 errors for 1h 23m due to OOM-killed pod. Root cause: memory leak in connection pool from release v2.14.0. Impact: ~340 failed transactions, 120 customers.",{"type":45,"tag":151,"props":341,"children":342},{},[343,367],{"type":45,"tag":155,"props":344,"children":345},{},[346],{"type":45,"tag":159,"props":347,"children":348},{},[349,353,357,362],{"type":45,"tag":163,"props":350,"children":351},{},[352],{"type":51,"value":167},{"type":45,"tag":163,"props":354,"children":355},{},[356],{"type":51,"value":287},{"type":45,"tag":163,"props":358,"children":359},{},[360],{"type":51,"value":361},"Target",{"type":45,"tag":163,"props":363,"children":364},{},[365],{"type":51,"value":366},"Status",{"type":45,"tag":174,"props":368,"children":369},{},[370,393,416,438],{"type":45,"tag":159,"props":371,"children":372},{},[373,378,383,388],{"type":45,"tag":181,"props":374,"children":375},{},[376],{"type":51,"value":377},"TTD",{"type":45,"tag":181,"props":379,"children":380},{},[381],{"type":51,"value":382},"6m",{"type":45,"tag":181,"props":384,"children":385},{},[386],{"type":51,"value":387},"\u003C5m",{"type":45,"tag":181,"props":389,"children":390},{},[391],{"type":51,"value":392},"⚠️",{"type":45,"tag":159,"props":394,"children":395},{},[396,401,406,411],{"type":45,"tag":181,"props":397,"children":398},{},[399],{"type":51,"value":400},"TTA",{"type":45,"tag":181,"props":402,"children":403},{},[404],{"type":51,"value":405},"4m",{"type":45,"tag":181,"props":407,"children":408},{},[409],{"type":51,"value":410},"\u003C15m",{"type":45,"tag":181,"props":412,"children":413},{},[414],{"type":51,"value":415},"✅",{"type":45,"tag":159,"props":417,"children":418},{},[419,424,429,434],{"type":45,"tag":181,"props":420,"children":421},{},[422],{"type":51,"value":423},"TTM",{"type":45,"tag":181,"props":425,"children":426},{},[427],{"type":51,"value":428},"28m",{"type":45,"tag":181,"props":430,"children":431},{},[432],{"type":51,"value":433},"\u003C30m",{"type":45,"tag":181,"props":435,"children":436},{},[437],{"type":51,"value":415},{"type":45,"tag":159,"props":439,"children":440},{},[441,446,450,455],{"type":45,"tag":181,"props":442,"children":443},{},[444],{"type":51,"value":445},"TTR",{"type":45,"tag":181,"props":447,"children":448},{},[449],{"type":51,"value":329},{"type":45,"tag":181,"props":451,"children":452},{},[453],{"type":51,"value":454},"\u003C2h",{"type":45,"tag":181,"props":456,"children":457},{},[458],{"type":51,"value":415},{"type":45,"tag":54,"props":460,"children":462},{"id":461},"references",[463],{"type":51,"value":464},"References",{"type":45,"tag":73,"props":466,"children":467},{},[468,481],{"type":45,"tag":77,"props":469,"children":470},{},[471,473],{"type":51,"value":472},"Postmortem Culture: ",{"type":45,"tag":474,"props":475,"children":479},"a",{"href":476,"rel":477},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fwell-architected\u002Foperational-excellence\u002Fmitigation-strategy",[478],"nofollow",[480],{"type":51,"value":476},{"type":45,"tag":77,"props":482,"children":483},{},[484,486],{"type":51,"value":485},"Azure Resource Health: ",{"type":45,"tag":474,"props":487,"children":490},{"href":488,"rel":489},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fservice-health\u002Fresource-health-overview",[478],[491],{"type":51,"value":488},{"items":493,"total":629},[494,515,535,556,575,591,610],{"slug":495,"name":496,"fn":497,"description":498,"org":499,"tags":500,"stars":28,"repoUrl":29,"updatedAt":514},"aifoundryposturecheck","ai_foundry_posture_check","assess Azure AI Foundry deployment posture","Assess security, reliability, and cost posture of Azure OpenAI and AI Foundry deployments. Detects anti-patterns like API keys instead of Managed Identity, public endpoints, disabled content filtering, deprecated models, over-provisioned PTU, missing AI Gateway, and single-region deployment.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[501,504,505,508,511],{"name":502,"slug":503,"type":17},"AI","ai",{"name":12,"slug":9,"type":17},{"name":506,"slug":507,"type":17},"Cost Optimization","cost-optimization",{"name":509,"slug":510,"type":17},"Reliability","reliability",{"name":512,"slug":513,"type":17},"Security","security","2026-08-23T04:00:38.426809",{"slug":516,"name":517,"fn":518,"description":519,"org":520,"tags":521,"stars":28,"repoUrl":29,"updatedAt":534},"atlassianrovo","atlassian_rovo","manage Atlassian Jira and Confluence tasks","Expertise in Atlassian Cloud products including Jira, Confluence, Compass, and Jira Service Management. Use for searching issues with JQL, creating and updating pages, managing service components, investigating ops alerts, and navigating Atlassian workspaces via the Rovo MCP server.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[522,525,528,531],{"name":523,"slug":524,"type":17},"Atlassian","atlassian",{"name":526,"slug":527,"type":17},"Confluence","confluence",{"name":529,"slug":530,"type":17},"Jira","jira",{"name":532,"slug":533,"type":17},"Project Management","project-management","2026-07-12T08:20:33.735452",{"slug":536,"name":537,"fn":538,"description":539,"org":540,"tags":541,"stars":28,"repoUrl":29,"updatedAt":555},"awscloudoperations","aws_cloud_operations","manage and troubleshoot AWS cloud operations","Expertise in AWS cloud operations including infrastructure management, troubleshooting, documentation search, API execution, and operational procedures. Use for querying AWS resources, investigating incidents, following SOPs, searching documentation, checking service availability, and executing AWS API calls via the AWS MCP Server.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[542,545,548,551,554],{"name":543,"slug":544,"type":17},"AWS","aws",{"name":546,"slug":547,"type":17},"Debugging","debugging",{"name":549,"slug":550,"type":17},"Infrastructure","infrastructure",{"name":552,"slug":553,"type":17},"Monitoring","monitoring",{"name":19,"slug":20,"type":17},"2026-07-12T08:20:14.702793",{"slug":557,"name":558,"fn":559,"description":560,"org":561,"tags":562,"stars":28,"repoUrl":29,"updatedAt":574},"azuremanagedgrafana","azure_managed_grafana","monitor Azure infrastructure with Grafana","Expertise in Azure Managed Grafana including dashboards, Azure Monitor metrics, Application Insights failures and traces, Azure Data Explorer (Kusto) queries, SQL Server queries, and Azure Resource Graph. Use for querying observability data, searching dashboards, investigating failures, analyzing GenAI agent telemetry, and running KQL or SQL queries via the AMG-MCP endpoint.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[563,566,567,570,571],{"name":564,"slug":565,"type":17},"Application Insights","application-insights",{"name":12,"slug":9,"type":17},{"name":568,"slug":569,"type":17},"Dashboards","dashboards",{"name":552,"slug":553,"type":17},{"name":572,"slug":573,"type":17},"Observability","observability","2026-07-12T08:19:37.659849",{"slug":576,"name":577,"fn":578,"description":579,"org":580,"tags":581,"stars":28,"repoUrl":29,"updatedAt":590},"capacityplanning","capacity_planning","assess Azure resource capacity and scaling","Assess Azure resource capacity, quota utilization, and growth trends to prevent outages from resource exhaustion. Use when asked about capacity, quotas, scaling readiness, load testing prep, or growth projections.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[582,583,586,587],{"name":12,"slug":9,"type":17},{"name":584,"slug":585,"type":17},"Capacity Planning","capacity-planning",{"name":19,"slug":20,"type":17},{"name":588,"slug":589,"type":17},"Performance","performance","2026-08-23T04:00:12.510248",{"slug":592,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":28,"repoUrl":29,"updatedAt":609},"compliancegovernanceaudit","compliance_governance_audit","audit Azure compliance and governance","Audit Azure environment for compliance and governance posture. Checks Azure Policy, RBAC, tagging, resource locks, naming conventions, and regulatory alignment. Use when asked about compliance, governance, audit readiness, or policy violations.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[598,601,602,605,608],{"name":599,"slug":600,"type":17},"Audit","audit",{"name":12,"slug":9,"type":17},{"name":603,"slug":604,"type":17},"Compliance","compliance",{"name":606,"slug":607,"type":17},"Governance","governance",{"name":512,"slug":513,"type":17},"2026-08-23T04:00:39.064619",{"slug":611,"name":612,"fn":613,"description":614,"org":615,"tags":616,"stars":28,"repoUrl":29,"updatedAt":628},"datadogobservability","datadog_observability","query Datadog telemetry and investigate behavior","Expertise in Datadog's observability platform including logs, metrics, APM, monitors, incidents, dashboards, hosts, and services. Use for searching logs, querying metrics, investigating incidents, analyzing traces, inspecting monitors, and navigating Datadog data via the Datadog MCP server.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[617,620,623,626,627],{"name":618,"slug":619,"type":17},"Datadog","datadog",{"name":621,"slug":622,"type":17},"Logs","logs",{"name":624,"slug":625,"type":17},"Metrics","metrics",{"name":552,"slug":553,"type":17},{"name":572,"slug":573,"type":17},"2026-07-12T08:20:41.400308",15,{"items":631,"total":799},[632,647,666,683,698,711,724,739,750,762,773,785],{"slug":633,"name":633,"fn":634,"description":635,"org":636,"tags":637,"stars":644,"repoUrl":645,"updatedAt":646},"azure-arg-external-evaluation-policy-author","author and test Azure Resource Graph policies","Use when the user wants to author, design, or test an Azure Policy that queries Azure Resource Graph (ARG) at request-time — i.e. a policy whose deny\u002Faudit decision depends on data from elsewhere in the subscription (sibling\u002Fparent resource state, RG-wide invariants, multi-hop relationships, etc.). Formally called Azure Policy External Evaluation; sometimes referred to colloquially as \"Invoke\". Drives an iterative KQL co-design loop against the user's real subscription via `az graph query`, then emits a policy definition, assignment, `.http` test flow, and an `EXPLANATION.md` companion. Read-only; never provisions anything.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[638,639,640,641],{"name":12,"slug":9,"type":17},{"name":603,"slug":604,"type":17},{"name":606,"slug":607,"type":17},{"name":642,"slug":643,"type":17},"Policy","policy",1689,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":648,"name":648,"fn":649,"description":650,"org":651,"tags":652,"stars":663,"repoUrl":664,"updatedAt":665},"azure-blueprints-migration","migrate Azure Blueprints to Template Specs","Use when a user needs to migrate off Azure Blueprints (definitions and\u002For assignments) to Template Specs and Deployment Stacks before the January 31, 2027 retirement. Covers inventory, export, conversion to Bicep, policy decoupling, Template Spec publishing, Deployment Stack deployment with deny-settings, validation, and cutover.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[653,654,657,660],{"name":12,"slug":9,"type":17},{"name":655,"slug":656,"type":17},"Deployment","deployment",{"name":658,"slug":659,"type":17},"Infrastructure as Code","infrastructure-as-code",{"name":661,"slug":662,"type":17},"Migration","migration",261,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-08-20T03:28:18.136156",{"slug":667,"name":667,"fn":668,"description":669,"org":670,"tags":671,"stars":680,"repoUrl":681,"updatedAt":682},"apiview-feedback-resolution","resolve APIView feedback on Azure SDKs","Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_typespec_customized_code_update.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[672,675,676,679],{"name":673,"slug":674,"type":17},"API Development","api-development",{"name":12,"slug":9,"type":17},{"name":677,"slug":678,"type":17},"Code Review","code-review",{"name":23,"slug":24,"type":17},136,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-tools","2026-07-12T08:17:43.350876",{"slug":684,"name":684,"fn":685,"description":686,"org":687,"tags":688,"stars":680,"repoUrl":681,"updatedAt":697},"azsdk-common-live-and-recorded-tests","deploy resources and run Azure SDK tests","Deploy test resources and run Azure SDK tests in live, record, or playback mode. WHEN: \"run live tests\", \"run recorded tests\", \"deploy test resources\", \"record tests\", \"run tests in record mode\", \"clean up test resources\", \"run tests against live resources\". DO NOT USE FOR: writing new tests, authoring Bicep templates, playback-only test runs without resource deployment. INVOKES: azure-sdk-mcp:azsdk_package_run_tests.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[689,690,691,694],{"name":12,"slug":9,"type":17},{"name":655,"slug":656,"type":17},{"name":692,"slug":693,"type":17},"SDK","sdk",{"name":695,"slug":696,"type":17},"Testing","testing","2026-07-12T08:17:44.718943",{"slug":699,"name":699,"fn":700,"description":701,"org":702,"tags":703,"stars":680,"repoUrl":681,"updatedAt":710},"azsdk-common-prepare-release-plan","manage Azure SDK release plan work items","Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. **UTILITY SKILL**. USE FOR: \"create release plan\", \"get release plan\", \"update release plan\", \"update API spec in release plan\", \"update SDK details in release plan\", \"abandon release plan\", \"link SDK PR to plan\", \"namespace approval\", \"check release plan status\". DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_get_release_plan_for_spec_pr, azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[704,705,708,709],{"name":12,"slug":9,"type":17},{"name":706,"slug":707,"type":17},"GitHub","github",{"name":532,"slug":533,"type":17},{"name":692,"slug":693,"type":17},"2026-07-12T08:17:38.345387",{"slug":712,"name":712,"fn":713,"description":714,"org":715,"tags":716,"stars":680,"repoUrl":681,"updatedAt":723},"azsdk-common-sdk-release","release Azure SDK packages","Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: \"release SDK\", \"trigger release\", \"check release readiness\", \"release pipeline\", \"publish package\", \"ship SDK\". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[717,718,721,722],{"name":12,"slug":9,"type":17},{"name":719,"slug":720,"type":17},"CI\u002FCD","ci-cd",{"name":655,"slug":656,"type":17},{"name":692,"slug":693,"type":17},"2026-07-12T08:17:34.27607",{"slug":725,"name":725,"fn":726,"description":727,"org":728,"tags":729,"stars":680,"repoUrl":681,"updatedAt":738},"azure-typespec-author","author and modify Azure TypeSpec API specifications","Authors and modifies Azure TypeSpec (.tsp) API specifications. USE FOR: any TypeSpec\u002Ftsp change — api versions (add, bump, preview, stable, promote), resources, operations, models, properties, decorators, visibility, constraints, breaking changes, LRO, suppressions, operationId, spread model. Covers ARM resource-manager and data-plane services. DO NOT USE FOR: SDK generation, releasing SDK packages, or single MCP tool calls. INVOKES: azure-sdk-mcp:azsdk_typespec_generate_authoring_plan, azure-sdk-mcp:azsdk_run_typespec_validation.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[730,731,732,735],{"name":673,"slug":674,"type":17},{"name":12,"slug":9,"type":17},{"name":733,"slug":734,"type":17},"OpenAPI","openapi",{"name":736,"slug":737,"type":17},"Technical Writing","technical-writing","2026-07-12T08:17:39.603232",{"slug":740,"name":740,"fn":741,"description":742,"org":743,"tags":744,"stars":680,"repoUrl":681,"updatedAt":749},"generate-sdk-locally","generate and test Azure SDKs locally","Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. WHEN: \"generate SDK locally\", \"build SDK\", \"run SDK tests\", \"run CI checks\", \"validate package\", \"run checks\", \"update changelog\", \"fix SDK build errors\", \"fix breaking changes\", \"resolve SDK generation errors\", \"customize TypeSpec\", \"rename SDK client\", \"rename SDK model\", \"hide operation from SDK\", \"fix analyzer errors\", \"resolve customization drift\", \"create subclient\", \"update metadata\", \"update version\". DO NOT USE FOR: publishing to package registries, CI pipeline configuration, API design review. INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[745,746,747,748],{"name":12,"slug":9,"type":17},{"name":719,"slug":720,"type":17},{"name":692,"slug":693,"type":17},{"name":695,"slug":696,"type":17},"2026-07-12T08:17:37.08523",{"slug":751,"name":751,"fn":752,"description":753,"org":754,"tags":755,"stars":680,"repoUrl":681,"updatedAt":761},"markdown-token-optimizer","optimize markdown files for token efficiency","Analyze markdown files for token efficiency and reduce context-window bloat. **UTILITY SKILL**. DO NOT USE FOR: code optimization, general file editing, non-markdown files. TRIGGERS: optimize markdown, reduce tokens, token count, token bloat, too many tokens, make concise, shrink file, file too large, optimize for AI, token efficiency, verbose markdown, reduce file size. INVOKES: waza CLI.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[756,759,760],{"name":757,"slug":758,"type":17},"LLM","llm",{"name":588,"slug":589,"type":17},{"name":736,"slug":737,"type":17},"2026-07-12T08:17:42.080413",{"slug":763,"name":763,"fn":764,"description":765,"org":766,"tags":767,"stars":680,"repoUrl":681,"updatedAt":772},"pipeline-troubleshooting","troubleshoot Azure SDK CI pipelines","Diagnose and resolve failures in Azure SDK CI and generation pipelines. **UTILITY SKILL**. USE FOR: \"pipeline failed\", \"build failure\", \"CI check failing\", \"SDK generation error\", \"reproduce pipeline locally\", \"debug SDK pipeline\". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing. INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_package_build_code, azure-sdk-mcp:azsdk_package_run_check.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[768,769,770,771],{"name":12,"slug":9,"type":17},{"name":719,"slug":720,"type":17},{"name":546,"slug":547,"type":17},{"name":692,"slug":693,"type":17},"2026-07-12T08:17:40.821512",{"slug":774,"name":774,"fn":775,"description":776,"org":777,"tags":778,"stars":680,"repoUrl":681,"updatedAt":784},"skill-authoring","author agent skills for agentskills.io","Write Agent Skills that comply with the agentskills.io specification. WHEN: \"create a skill\", \"new skill\", \"write a skill\", \"skill template\", \"skill structure\", \"review skill\", \"skill PR\", \"skill compliance\", \"SKILL.md format\", \"skill frontmatter\", \"skill best practices\". DO NOT USE FOR: general documentation. INVOKES: waza CLI.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[779,780,783],{"name":23,"slug":24,"type":17},{"name":781,"slug":782,"type":17},"Plugin Development","plugin-development",{"name":736,"slug":737,"type":17},"2026-08-07T04:39:22.66861",{"slug":786,"name":786,"fn":787,"description":788,"org":789,"tags":790,"stars":796,"repoUrl":797,"updatedAt":798},"kickstart-acr-integration","integrate Azure Container Registry with AKS","ACR integration for AKS Automatic. Teaches attaching an ACR, image reference conventions (digest pinning, no :latest), and pull-secret-free authentication via the managed identity.",{"slug":9,"name":10,"logoUrl":11,"githubOrg":12},[791,792,795],{"name":12,"slug":9,"type":17},{"name":793,"slug":794,"type":17},"Containers","containers",{"name":655,"slug":656,"type":17},65,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fvscode-aks-tools","2026-07-12T08:18:05.091337",124]