[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-azure-functions-diagnostics":3,"mdc--bh6esd-key":35,"related-repo-azure-azure-functions-diagnostics":346,"related-org-azure-azure-functions-diagnostics":441},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"azure-functions-diagnostics","diagnose and resolve Azure Functions issues","Use when diagnosing or resolving Azure Functions issues: deployment failures, runtime errors, trigger\u002Fbinding failures, language worker issues, telemetry\u002Flog analysis, known issue research, source investigation, and remediation. Acts as a facade that routes to focused Azure Functions skills and small language\u002Fextension references.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"azure","Azure (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fazure.png","Azure",[13,15,18,21],{"name":11,"slug":8,"type":14},"tag",{"name":16,"slug":17,"type":14},"Logs","logs",{"name":19,"slug":20,"type":14},"Monitoring","monitoring",{"name":22,"slug":23,"type":14},"Debugging","debugging",12,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-functions-skills","2026-07-12T08:19:30.738425",null,1,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"A repository for Azure Functions skills, prompts, and reusable definitions to support agentic development and operational workflows.","https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-functions-skills\u002Ftree\u002FHEAD\u002Ftemplates\u002Fskills\u002Fazure-functions-diagnostics","---\nname: azure-functions-diagnostics\ntitle: Azure Functions Diagnostics\ndescription: \"Use when diagnosing or resolving Azure Functions issues: deployment failures, runtime errors, trigger\u002Fbinding failures, language worker issues, telemetry\u002Flog analysis, known issue research, source investigation, and remediation. Acts as a facade that routes to focused Azure Functions skills and small language\u002Fextension references.\"\ncategory: task\n---\n\n# Azure Functions Diagnostics\n\nUse this skill to diagnose and resolve Azure Functions issues by orchestrating focused skills and loading only the references needed for the current app.\n\nWrite final answers in the user's language.\n\n## Core principle\n\nDo not load all diagnostic references up front. First collect the app inventory, infer runtime\u002Flanguage and trigger\u002Fbinding\u002Fextension shape, then load only the matching language and extension reference files.\n\nFor multi-step reviews, source investigations, or remediation work, create a short checklist plan file or todo list and update it after each completed step. Do not require a checklist for quick read-only diagnosis because it adds token overhead.\n\n## Required inputs\n\nAsk only for missing inputs needed to start:\n\n- Function App name, unless already provided.\n- Subscription ID\u002Fname and resource group, if needed to disambiguate.\n- Symptom, error message, command output, or portal\u002Fdeployment failure context.\n- Time window, default `24h` for current or recent production issues.\n\nIf the user has a local workspace issue without a deployed app, skip Azure resource collection and start from local project\u002Fruntime\u002Ftrigger discovery.\n\n## Diagnostic workflow\n\nFollow [workflow.md](references\u002Fworkflow.md). Use shared reference routing from [..\u002Fazure-functions-common\u002Freferences\u002Frouting.md](..\u002Fazure-functions-common\u002Freferences\u002Frouting.md) only after inventory\u002Fhealth data identifies the relevant runtime, trigger, binding, or symptom.\n\nFast path:\n\n1. Use `azure-functions-inventory` to collect static app specifications.\n2. Use `azure-functions-health-status` to collect current health, metrics, telemetry, and Activity Log.\n3. Use [..\u002Fazure-functions-common\u002Freferences\u002Frouting.md](..\u002Fazure-functions-common\u002Freferences\u002Frouting.md) to select only the required language and extension references.\n4. Use [evidence-checklist.md](references\u002Fevidence-checklist.md) before stating root cause or recommended fixes.\n5. Prefer official documentation, official repositories, official samples, and package\u002Fcontainer registries before broader web sources.\n\n## Reference loading rules\n\nUse `azure-functions-common` for shared runtime, language, and trigger\u002Fbinding references.\n\n- Load exactly one language reference when the runtime is known, plus Durable only when Durable is involved.\n- Load only extension references matching the app's triggers\u002Fbindings or the symptom.\n- Load Extension Bundles only for non-.NET apps or extension-version\u002Fbinding-resolution symptoms.\n- Do not load migration provenance during normal diagnostics.\n\n## Guardrails\n\n- Redact secrets, connection strings, keys, tokens, SAS URLs, and storage credentials.\n- Report setting names and whether values exist; do not reveal values.\n- Ask before cloning large repositories, using sparse checkout, deploying to Azure, restarting apps, changing configuration, or running disruptive commands.\n- Distinguish confirmed evidence from hypotheses.\n- For transient issues, state whether the current app is healthy and identify the historical evidence used.\n\n## Next steps\n\n- On success, suggest `azure-functions-inventory` if the app shape or configuration changed during remediation.\n- On failure, suggest `azure-functions-health-status` to re-check current health and telemetry before continuing diagnosis.\n\n## Output shape\n\nUse this concise structure unless the user asks for a different format:\n\n```text\nTarget: \u003Capp\u002Fresource\u002Flocal project>\nSymptom: \u003Csummary>\nInventory: \u003Cruntime\u002Fplan\u002Fnetwork\u002Ftriggers summary>\nHealth: \u003Ccurrent state\u002Fmetrics\u002Flog findings summary>\nRelevant references loaded: \u003Clanguage refs>, \u003Cextension refs>\nFindings: \u003Cevidence-backed bullets>\nLikely cause: \u003Cconfirmed or suspected>\nRecommended actions: \u003Cordered steps>\nValidation plan: \u003Clocal\u002FE2E\u002FAzure validation steps>\nGaps: \u003Cmissing permissions\u002Ftelemetry\u002Fcontext>\n```\n",{"data":36,"body":39},{"name":4,"title":37,"description":6,"category":38},"Azure Functions Diagnostics","task",{"type":40,"children":41},"root",[42,49,55,60,67,72,77,83,88,122,127,133,154,159,215,221,233,256,262,290,296,323,329,334],{"type":43,"tag":44,"props":45,"children":46},"element","h1",{"id":4},[47],{"type":48,"value":37},"text",{"type":43,"tag":50,"props":51,"children":52},"p",{},[53],{"type":48,"value":54},"Use this skill to diagnose and resolve Azure Functions issues by orchestrating focused skills and loading only the references needed for the current app.",{"type":43,"tag":50,"props":56,"children":57},{},[58],{"type":48,"value":59},"Write final answers in the user's language.",{"type":43,"tag":61,"props":62,"children":64},"h2",{"id":63},"core-principle",[65],{"type":48,"value":66},"Core principle",{"type":43,"tag":50,"props":68,"children":69},{},[70],{"type":48,"value":71},"Do not load all diagnostic references up front. First collect the app inventory, infer runtime\u002Flanguage and trigger\u002Fbinding\u002Fextension shape, then load only the matching language and extension reference files.",{"type":43,"tag":50,"props":73,"children":74},{},[75],{"type":48,"value":76},"For multi-step reviews, source investigations, or remediation work, create a short checklist plan file or todo list and update it after each completed step. Do not require a checklist for quick read-only diagnosis because it adds token overhead.",{"type":43,"tag":61,"props":78,"children":80},{"id":79},"required-inputs",[81],{"type":48,"value":82},"Required inputs",{"type":43,"tag":50,"props":84,"children":85},{},[86],{"type":48,"value":87},"Ask only for missing inputs needed to start:",{"type":43,"tag":89,"props":90,"children":91},"ul",{},[92,98,103,108],{"type":43,"tag":93,"props":94,"children":95},"li",{},[96],{"type":48,"value":97},"Function App name, unless already provided.",{"type":43,"tag":93,"props":99,"children":100},{},[101],{"type":48,"value":102},"Subscription ID\u002Fname and resource group, if needed to disambiguate.",{"type":43,"tag":93,"props":104,"children":105},{},[106],{"type":48,"value":107},"Symptom, error message, command output, or portal\u002Fdeployment failure context.",{"type":43,"tag":93,"props":109,"children":110},{},[111,113,120],{"type":48,"value":112},"Time window, default ",{"type":43,"tag":114,"props":115,"children":117},"code",{"className":116},[],[118],{"type":48,"value":119},"24h",{"type":48,"value":121}," for current or recent production issues.",{"type":43,"tag":50,"props":123,"children":124},{},[125],{"type":48,"value":126},"If the user has a local workspace issue without a deployed app, skip Azure resource collection and start from local project\u002Fruntime\u002Ftrigger discovery.",{"type":43,"tag":61,"props":128,"children":130},{"id":129},"diagnostic-workflow",[131],{"type":48,"value":132},"Diagnostic workflow",{"type":43,"tag":50,"props":134,"children":135},{},[136,138,145,147,152],{"type":48,"value":137},"Follow ",{"type":43,"tag":139,"props":140,"children":142},"a",{"href":141},"references\u002Fworkflow.md",[143],{"type":48,"value":144},"workflow.md",{"type":48,"value":146},". Use shared reference routing from ",{"type":43,"tag":139,"props":148,"children":150},{"href":149},"..\u002Fazure-functions-common\u002Freferences\u002Frouting.md",[151],{"type":48,"value":149},{"type":48,"value":153}," only after inventory\u002Fhealth data identifies the relevant runtime, trigger, binding, or symptom.",{"type":43,"tag":50,"props":155,"children":156},{},[157],{"type":48,"value":158},"Fast path:",{"type":43,"tag":160,"props":161,"children":162},"ol",{},[163,176,188,198,210],{"type":43,"tag":93,"props":164,"children":165},{},[166,168,174],{"type":48,"value":167},"Use ",{"type":43,"tag":114,"props":169,"children":171},{"className":170},[],[172],{"type":48,"value":173},"azure-functions-inventory",{"type":48,"value":175}," to collect static app specifications.",{"type":43,"tag":93,"props":177,"children":178},{},[179,180,186],{"type":48,"value":167},{"type":43,"tag":114,"props":181,"children":183},{"className":182},[],[184],{"type":48,"value":185},"azure-functions-health-status",{"type":48,"value":187}," to collect current health, metrics, telemetry, and Activity Log.",{"type":43,"tag":93,"props":189,"children":190},{},[191,192,196],{"type":48,"value":167},{"type":43,"tag":139,"props":193,"children":194},{"href":149},[195],{"type":48,"value":149},{"type":48,"value":197}," to select only the required language and extension references.",{"type":43,"tag":93,"props":199,"children":200},{},[201,202,208],{"type":48,"value":167},{"type":43,"tag":139,"props":203,"children":205},{"href":204},"references\u002Fevidence-checklist.md",[206],{"type":48,"value":207},"evidence-checklist.md",{"type":48,"value":209}," before stating root cause or recommended fixes.",{"type":43,"tag":93,"props":211,"children":212},{},[213],{"type":48,"value":214},"Prefer official documentation, official repositories, official samples, and package\u002Fcontainer registries before broader web sources.",{"type":43,"tag":61,"props":216,"children":218},{"id":217},"reference-loading-rules",[219],{"type":48,"value":220},"Reference loading rules",{"type":43,"tag":50,"props":222,"children":223},{},[224,225,231],{"type":48,"value":167},{"type":43,"tag":114,"props":226,"children":228},{"className":227},[],[229],{"type":48,"value":230},"azure-functions-common",{"type":48,"value":232}," for shared runtime, language, and trigger\u002Fbinding references.",{"type":43,"tag":89,"props":234,"children":235},{},[236,241,246,251],{"type":43,"tag":93,"props":237,"children":238},{},[239],{"type":48,"value":240},"Load exactly one language reference when the runtime is known, plus Durable only when Durable is involved.",{"type":43,"tag":93,"props":242,"children":243},{},[244],{"type":48,"value":245},"Load only extension references matching the app's triggers\u002Fbindings or the symptom.",{"type":43,"tag":93,"props":247,"children":248},{},[249],{"type":48,"value":250},"Load Extension Bundles only for non-.NET apps or extension-version\u002Fbinding-resolution symptoms.",{"type":43,"tag":93,"props":252,"children":253},{},[254],{"type":48,"value":255},"Do not load migration provenance during normal diagnostics.",{"type":43,"tag":61,"props":257,"children":259},{"id":258},"guardrails",[260],{"type":48,"value":261},"Guardrails",{"type":43,"tag":89,"props":263,"children":264},{},[265,270,275,280,285],{"type":43,"tag":93,"props":266,"children":267},{},[268],{"type":48,"value":269},"Redact secrets, connection strings, keys, tokens, SAS URLs, and storage credentials.",{"type":43,"tag":93,"props":271,"children":272},{},[273],{"type":48,"value":274},"Report setting names and whether values exist; do not reveal values.",{"type":43,"tag":93,"props":276,"children":277},{},[278],{"type":48,"value":279},"Ask before cloning large repositories, using sparse checkout, deploying to Azure, restarting apps, changing configuration, or running disruptive commands.",{"type":43,"tag":93,"props":281,"children":282},{},[283],{"type":48,"value":284},"Distinguish confirmed evidence from hypotheses.",{"type":43,"tag":93,"props":286,"children":287},{},[288],{"type":48,"value":289},"For transient issues, state whether the current app is healthy and identify the historical evidence used.",{"type":43,"tag":61,"props":291,"children":293},{"id":292},"next-steps",[294],{"type":48,"value":295},"Next steps",{"type":43,"tag":89,"props":297,"children":298},{},[299,311],{"type":43,"tag":93,"props":300,"children":301},{},[302,304,309],{"type":48,"value":303},"On success, suggest ",{"type":43,"tag":114,"props":305,"children":307},{"className":306},[],[308],{"type":48,"value":173},{"type":48,"value":310}," if the app shape or configuration changed during remediation.",{"type":43,"tag":93,"props":312,"children":313},{},[314,316,321],{"type":48,"value":315},"On failure, suggest ",{"type":43,"tag":114,"props":317,"children":319},{"className":318},[],[320],{"type":48,"value":185},{"type":48,"value":322}," to re-check current health and telemetry before continuing diagnosis.",{"type":43,"tag":61,"props":324,"children":326},{"id":325},"output-shape",[327],{"type":48,"value":328},"Output shape",{"type":43,"tag":50,"props":330,"children":331},{},[332],{"type":48,"value":333},"Use this concise structure unless the user asks for a different format:",{"type":43,"tag":335,"props":336,"children":341},"pre",{"className":337,"code":339,"language":48,"meta":340},[338],"language-text","Target: \u003Capp\u002Fresource\u002Flocal project>\nSymptom: \u003Csummary>\nInventory: \u003Cruntime\u002Fplan\u002Fnetwork\u002Ftriggers summary>\nHealth: \u003Ccurrent state\u002Fmetrics\u002Flog findings summary>\nRelevant references loaded: \u003Clanguage refs>, \u003Cextension refs>\nFindings: \u003Cevidence-backed bullets>\nLikely cause: \u003Cconfirmed or suspected>\nRecommended actions: \u003Cordered steps>\nValidation plan: \u003Clocal\u002FE2E\u002FAzure validation steps>\nGaps: \u003Cmissing permissions\u002Ftelemetry\u002Fcontext>\n","",[342],{"type":43,"tag":114,"props":343,"children":344},{"__ignoreMap":340},[345],{"type":48,"value":339},{"items":347,"total":440},[348,365,382,395,409,421,428],{"slug":349,"name":349,"fn":350,"description":351,"org":352,"tags":353,"stars":24,"repoUrl":25,"updatedAt":364},"azure-functions-agents","build and deploy Azure Functions agents","Build, scaffold, extend, deploy, and troubleshoot Azure Functions serverless agents and event-driven AI agents using the Azure Functions serverless agents runtime. Use when the user says serverless agent, serverless agents, Azure Functions agent, scheduled agent, morning briefing, daily digest, timer agent, inbox summary, email or Teams briefing, background AI workflow, connector-triggered agent, event-driven AI automation, HTTP\u002Fchat agent, webhook-style agent, or Azure Functions hosted agent.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[354,357,358,361],{"name":355,"slug":356,"type":14},"Agents","agents",{"name":11,"slug":8,"type":14},{"name":359,"slug":360,"type":14},"Deployment","deployment",{"name":362,"slug":363,"type":14},"Serverless","serverless","2026-07-12T08:19:28.200894",{"slug":366,"name":366,"fn":367,"description":368,"org":369,"tags":370,"stars":24,"repoUrl":25,"updatedAt":381},"azure-functions-best-practices","apply Azure Functions best practices","Use when reviewing an existing Azure Function App against Azure Functions best practices and proposing safe, approval-gated remediations for runtime, configuration, identity, security, observability, performance, scale, cost, triggers, and bindings.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[371,372,375,378],{"name":11,"slug":8,"type":14},{"name":373,"slug":374,"type":14},"Best Practices","best-practices",{"name":376,"slug":377,"type":14},"Observability","observability",{"name":379,"slug":380,"type":14},"Security","security","2026-07-15T06:02:48.801578",{"slug":230,"name":230,"fn":383,"description":384,"org":385,"tags":386,"stars":24,"repoUrl":25,"updatedAt":394},"reference Azure Functions documentation and configuration","Shared Azure Functions reference material for the Azure Functions skill suite: runtime\u002Flanguage routing, trigger\u002Fbinding extension references, official docs and repository pointers. Use only when another Azure Functions skill needs reusable language or binding context. Not intended as a standalone user-facing workflow.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[387,388,391],{"name":11,"slug":8,"type":14},{"name":389,"slug":390,"type":14},"Configuration","configuration",{"name":392,"slug":393,"type":14},"Documentation","documentation","2026-07-15T06:02:47.557542",{"slug":396,"name":396,"fn":397,"description":398,"org":399,"tags":400,"stars":24,"repoUrl":25,"updatedAt":408},"azure-functions-create","scaffold Azure Functions projects and triggers","Scaffold a new Azure Functions project, or add a new function\u002Ftrigger to an existing project without re-initializing it",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[401,404,405],{"name":402,"slug":403,"type":14},"API Development","api-development",{"name":11,"slug":8,"type":14},{"name":406,"slug":407,"type":14},"Edge Functions","edge-functions","2026-07-12T08:19:36.401016",{"slug":410,"name":410,"fn":411,"description":412,"org":413,"tags":414,"stars":24,"repoUrl":25,"updatedAt":420},"azure-functions-deploy","deploy Azure Functions applications","Proxy Azure Functions deployment requests to the Azure Skills prepare, validate, and deploy workflow while preserving Azure Functions-specific guidance",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[415,416,419],{"name":11,"slug":8,"type":14},{"name":417,"slug":418,"type":14},"CI\u002FCD","ci-cd",{"name":359,"slug":360,"type":14},"2026-07-12T08:19:34.579423",{"slug":4,"name":4,"fn":5,"description":6,"org":422,"tags":423,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[424,425,426,427],{"name":11,"slug":8,"type":14},{"name":22,"slug":23,"type":14},{"name":16,"slug":17,"type":14},{"name":19,"slug":20,"type":14},{"slug":429,"name":429,"fn":430,"description":431,"org":432,"tags":433,"stars":24,"repoUrl":25,"updatedAt":439},"azure-functions-doctor","diagnose Azure Functions workspace configuration","Analyze local Azure Functions workspace code and configuration for common issues. Produces structured JSON findings for integration with the doctor CLI command. This skill targets local workspaces only — use azure-functions-diagnostics for deployed Azure resources.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[434,435,438],{"name":11,"slug":8,"type":14},{"name":436,"slug":437,"type":14},"Code Analysis","code-analysis",{"name":22,"slug":23,"type":14},"2026-07-15T06:02:46.335328",11,{"items":442,"total":611},[443,462,479,494,509,524,535,550,561,575,586,599],{"slug":444,"name":444,"fn":445,"description":446,"org":447,"tags":448,"stars":459,"repoUrl":460,"updatedAt":461},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[449,450,453,456],{"name":11,"slug":8,"type":14},{"name":451,"slug":452,"type":14},"Compliance","compliance",{"name":454,"slug":455,"type":14},"Governance","governance",{"name":457,"slug":458,"type":14},"Policy","policy",1686,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":463,"name":463,"fn":464,"description":465,"org":466,"tags":467,"stars":476,"repoUrl":477,"updatedAt":478},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[468,469,470,473],{"name":11,"slug":8,"type":14},{"name":359,"slug":360,"type":14},{"name":471,"slug":472,"type":14},"Infrastructure as Code","infrastructure-as-code",{"name":474,"slug":475,"type":14},"Migration","migration",260,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-07-12T08:17:49.646405",{"slug":480,"name":480,"fn":481,"description":482,"org":483,"tags":484,"stars":491,"repoUrl":492,"updatedAt":493},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[485,486,487,490],{"name":402,"slug":403,"type":14},{"name":11,"slug":8,"type":14},{"name":488,"slug":489,"type":14},"Code Review","code-review",{"name":392,"slug":393,"type":14},133,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-sdk-tools","2026-07-12T08:17:43.350876",{"slug":495,"name":495,"fn":496,"description":497,"org":498,"tags":499,"stars":491,"repoUrl":492,"updatedAt":508},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[500,501,502,505],{"name":11,"slug":8,"type":14},{"name":359,"slug":360,"type":14},{"name":503,"slug":504,"type":14},"SDK","sdk",{"name":506,"slug":507,"type":14},"Testing","testing","2026-07-12T08:17:44.718943",{"slug":510,"name":510,"fn":511,"description":512,"org":513,"tags":514,"stars":491,"repoUrl":492,"updatedAt":523},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[515,516,519,522],{"name":11,"slug":8,"type":14},{"name":517,"slug":518,"type":14},"GitHub","github",{"name":520,"slug":521,"type":14},"Project Management","project-management",{"name":503,"slug":504,"type":14},"2026-07-12T08:17:38.345387",{"slug":525,"name":525,"fn":526,"description":527,"org":528,"tags":529,"stars":491,"repoUrl":492,"updatedAt":534},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[530,531,532,533],{"name":11,"slug":8,"type":14},{"name":417,"slug":418,"type":14},{"name":359,"slug":360,"type":14},{"name":503,"slug":504,"type":14},"2026-07-12T08:17:34.27607",{"slug":536,"name":536,"fn":537,"description":538,"org":539,"tags":540,"stars":491,"repoUrl":492,"updatedAt":549},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[541,542,543,546],{"name":402,"slug":403,"type":14},{"name":11,"slug":8,"type":14},{"name":544,"slug":545,"type":14},"OpenAPI","openapi",{"name":547,"slug":548,"type":14},"Technical Writing","technical-writing","2026-07-12T08:17:39.603232",{"slug":551,"name":551,"fn":552,"description":553,"org":554,"tags":555,"stars":491,"repoUrl":492,"updatedAt":560},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[556,557,558,559],{"name":11,"slug":8,"type":14},{"name":417,"slug":418,"type":14},{"name":503,"slug":504,"type":14},{"name":506,"slug":507,"type":14},"2026-07-12T08:17:37.08523",{"slug":562,"name":562,"fn":563,"description":564,"org":565,"tags":566,"stars":491,"repoUrl":492,"updatedAt":574},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[567,570,573],{"name":568,"slug":569,"type":14},"LLM","llm",{"name":571,"slug":572,"type":14},"Performance","performance",{"name":547,"slug":548,"type":14},"2026-07-12T08:17:42.080413",{"slug":576,"name":576,"fn":577,"description":578,"org":579,"tags":580,"stars":491,"repoUrl":492,"updatedAt":585},"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":8,"name":9,"logoUrl":10,"githubOrg":11},[581,582,583,584],{"name":11,"slug":8,"type":14},{"name":417,"slug":418,"type":14},{"name":22,"slug":23,"type":14},{"name":503,"slug":504,"type":14},"2026-07-12T08:17:40.821512",{"slug":587,"name":587,"fn":588,"description":589,"org":590,"tags":591,"stars":491,"repoUrl":492,"updatedAt":598},"sensei","improve skill frontmatter compliance","**WORKFLOW SKILL** — Iteratively improve skill frontmatter compliance using the Ralph loop pattern. WHEN: \"run sensei\", \"sensei help\", \"improve skill\", \"fix frontmatter\", \"skill compliance\", \"frontmatter audit\", \"score skill\", \"check skill tokens\". INVOKES: token counting tools, test runners, git commands. FOR SINGLE OPERATIONS: use token CLI directly for counts\u002Fchecks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[592,593,594,597],{"name":11,"slug":8,"type":14},{"name":451,"slug":452,"type":14},{"name":595,"slug":596,"type":14},"Process Optimization","process-optimization",{"name":547,"slug":548,"type":14},"2026-07-12T08:17:32.970921",{"slug":600,"name":600,"fn":601,"description":602,"org":603,"tags":604,"stars":491,"repoUrl":492,"updatedAt":610},"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: improving existing skills (use sensei), general documentation. INVOKES: waza CLI.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[605,606,609],{"name":392,"slug":393,"type":14},{"name":607,"slug":608,"type":14},"Plugin Development","plugin-development",{"name":547,"slug":548,"type":14},"2026-07-12T08:17:35.873862",109]