[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699VDFTD61T60KSB4MMA1D8":3,"skill-same:01M699VDFTD61T60KSB4MMA1D8":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M699VDFTD61T60KSB4MMA1D8","azure-kusto-irql",null,"Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigations. Translates natural language hunting questions into composable IRQL pipelines using Get_*, Extract_*, and Enrich_* functions. WHEN: IRQL query, security hunt, threat hunting KQL, incident response query, compose hunting pipeline, failed logins, phishing investigation, lateral movement, process execution, file creation events.","microsoft\u002FGitHub-Copilot-for-Azure","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699SRDDGQCK3TYBF146AE4D",264,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-kusto-graph-skills\u002Fskills\u002Fazure-kusto-irql\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,9,41,42,43],"azure kusto irql","azure kusto","azure","threat","investigations","when","process execution","lateral movement","hunting","enrich","creation","get","incident","query","security","pipeline","placeholder","threat hunting","incident response","cybersecurity","2026-11-10 10:12:30",false,"---\nname: azure-kusto-irql\ndescription: \"Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigations. Translates natural language hunting questions into composable IRQL pipelines using Get_*, Extract_*, and Enrich_* functions. WHEN: IRQL query, security hunt, threat hunting KQL, incident response query, compose hunting pipeline, failed logins, phishing investigation, lateral movement, process execution, file creation events.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"0.0.0-placeholder\"\n---\n\n# IRQL -- Incident Response Query Language\n\nCompose IRQL function pipelines from selector, extractor, and enricher building blocks. IRQL wraps raw KQL security tables behind intent-revealing, composable functions so analysts (and LLMs) can express hunts without memorizing schemas, cluster locations, or join keys.\n\n## Activation Triggers\n\nUse this skill when the user:\n- Explicitly mentions IRQL, `Get_*`, `Extract_*`, or `Enrich_*` functions\n- Says \"use IRQL\" or \"write an IRQL query\"\n- Requests a composable hunting pipeline using known IRQL selectors\n\nDo **not** activate for generic security queries (e.g. \"find failed logins\") unless the user explicitly asks for IRQL. Route those to `azure-kusto` instead.\n\n**Not a natural-language-to-IRQL converter.** This skill composes IRQL function pipelines and may handle basic natural-language requests that map directly to known selectors and simple filters. For general NL-to-KQL or NL-to-IRQL conversion, use a dedicated query-generation skill (available separately).\n\n## IRQL Function Preflight\n\nBefore generating a pipeline, verify IRQL is available on the target database:\n\n```kql\n.show functions\n| where Name startswith \"Get_\" or Name startswith \"Extract_\" or Name startswith \"Enrich_\"\n| project Name\n```\n\nIf no IRQL functions are found, inform the user that IRQL is not deployed on the target database and suggest using `azure-kusto` for raw KQL queries instead. IRQL functions are a prerequisite -- this skill does not deploy base IRQL selectors.\n\n## What IRQL Is\n\nIRQL is a **function-based dialect on top of KQL**. It provides:\n\n1. **Unified schema** -- disparate security tables project into consistent column names regardless of the underlying data source\n2. **Composability** -- small functions chain via `| invoke` to build complex hunts from simple steps\n3. **Portability** -- the same IRQL pipeline works across different clusters\u002Fdatabases; only the `Get_*` primitives need re-pointing\n\nIRQL is not a separate language. It's KQL functions you invoke. Any valid KQL works alongside IRQL functions.\n\n## Deploying IRQL\n\nIRQL functions are stored KQL functions (`.create-or-alter function`). They must already be deployed to the target database before this skill can generate pipelines.\n\n**Public example cluster** (functions pre-deployed):\n- Cluster: `https:\u002F\u002Fkc7001.eastus.kusto.windows.net`\n- Databases: `ValdyTimes`, `JoJosHospital`\n\nTo port IRQL to a new cluster\u002Fdatabase, create `Get_*` selectors that project your source tables into the unified schema (column names below), then deploy extractors and enrichers. The extractors and enrichers work unchanged as long as the input schema matches.\n\n## Function Catalog\n\n### 1. Selectors -- `Get_*`\n\nReturn projected, schema-unified views of source tables. Use the minimal form by default; use `_All` when extra columns are needed.\n\n| Function | Columns |\n|---|---|\n| `Get_Event_Authentication` | `EnvTime`, `Hostname`, `ClientIp`, `Username`, `Result` |\n| `Get_Event_Authentication_All` | + `Description`, `UserAgent`, `PasswordHash` |\n| `Get_Email` | `EnvTime`, `EmailSender`, `EmailRecipient`, `Subject`, `Url` |\n| `Get_Email_All` | + `ReplyTo`, `Verdict` |\n| `Get_Employees` | `Name`, `ClientIp`, `Email`, `Username`, `Hostname`, `Role` |\n| `Get_Employees_All` | + `HireDate`, `UserAgent`, `Domain` |\n| `Get_Event_FileCreation` | `EnvTime`, `Hostname`, `Filename`, `Path` |\n| `Get_Event_FileCreation_All` | + `Username`, `Sha256`, `ProcessName` |\n| `Get_Event_NetworkInbound` | `EnvTime`, `ClientIp`, `Url` |\n| `Get_Event_NetworkInbound_All` | + `Method`, `UserAgent`, `StatusCode` |\n| `Get_Event_NetworkOutbound` | `EnvTime`, `ClientIp`, `Url` |\n| `Get_Event_NetworkOutbound_All` | + `Method`, `UserAgent` |\n| `Get_Dns_All` | `EnvTime`, `Domain`, `ClientIp` |\n| `Get_Event_Process` | `EnvTime`, `ProcessCommandLine`, `ProcessName`, `Hostname`, `Username` |\n| `Get_Event_Process_All` | + `ParentProcessName`, `ParentProcessHash`, `ProcessHash` |\n| `Get_SecurityAlerts_All` | `EnvTime`, `AlertType`, `Severity`, `Description`, `Indicators` |\n| `Get_Network_Connection_All` | `EnvTime`, `SourceIp`, `SourcePort`, `DestinationIp`, `DestinationPort`, `Protocol`, `Bytes` |\n\n### 2. Extractors -- `Extract_*`\n\nDerive a new column from an existing one. Invoke after a selector.\n\n| Function | Input Column | Adds |\n|---|---|---|\n| `Extract_Email_Sender_Domain(T)` | `EmailSender` | `Domain` |\n| `Extract_Employee_Firstname(T)` | `Name` | `Firstname` |\n| `Extract_Event_Network_Domain(T)` | `Url` | `DomainName` |\n\n### 3. Enrichers -- `Enrich_*`\n\nLeft-join helpers that attach context from a related table.\n\n| Function | Key Column | Enriches With |\n|---|---|---|\n| `Enrich_Event_Authentication_Username(T)` | `Username` | Auth events for user |\n| `Enrich_Ip_Employee(T)` | `ClientIp` | Employee identity from IP |\n| `Enrich_Username_Employee(T)` | `Username` | Employee identity from username |\n| `Enrich_Ip_Domain(T)` | `ClientIp` | DNS domains resolved to IP |\n| `Enrich_Ip_Event_NetworkOutbound(T)` | `ClientIp` | Outbound network from IP |\n| `Enrich_Ip_Network_Connection(T)` | `ClientIp` | Network flows from IP |\n\n### 4. External Enrichment\n\n| Function | Source | Requirement |\n|---|---|---|\n| `Enrich_Sha256_VirusTotal(T)` | VirusTotal file report | API key + callout policy |\n| `Get_CISA_KEV()` \u002F `Enrich_CISA_KEV(T)` | CISA KEV catalog | Callout policy |\n\n## Composition Rules\n\n```\nSelector -> Extract -> Filter -> Enrich -> Summarize\u002FProject\n```\n\n1. **Start with a Selector**: `Get_Event_Authentication`, `Get_Email`, etc.\n2. **Extract** derived fields: `| invoke Extract_Email_Sender_Domain()`\n3. **Filter** to the signal: `| where Result == \"Failed Login\"`\n4. **Enrich** with context: `| invoke Enrich_Username_Employee()`\n5. **Summarize \u002F project** the answer\n\nAlways pipe (`|`) between steps. Extractors and Enrichers use `| invoke FunctionName()`.\n\n## Query Generation Guidelines\n\n- Use the **minimal selector** unless extra columns are needed -> then `_All`\n- Chain extractors before enrichers (extractors add columns enrichers may key on)\n- Place `where` filters as early as possible\n- Use `summarize` for aggregations, `project` for final column selection\n- End with `order by` + `take` to limit output\n\n## Examples\n\nFor additional prompts and worked examples, see [references\u002FEXAMPLES.md](references\u002FEXAMPLES.md).\n\n### Brute-force detection\n```kql\nGet_Event_Authentication\n| where Result == \"Failed Login\"\n| summarize FailedCount = count() by Username\n| where FailedCount > 19\n| invoke Enrich_Username_Employee()\n| project Username, Name, Role, Email, FailedCount\n| order by FailedCount desc\n```\n\n### Phishing triage by recipient seniority\n```kql\nGet_Email\n| invoke Extract_Email_Sender_Domain()\n| project EnvTime, EmailSender, Domain, Username = EmailRecipient, Subject, Url\n| invoke Enrich_Username_Employee()\n| extend Seniority = case(\n    Role has_any (\"CEO\", \"Chief\", \"Director\", \"VP\", \"President\"), 3,\n    Role has_any (\"Manager\", \"Lead\", \"Senior\"), 2,\n    1)\n| summarize\n    TotalEmails = count(),\n    SeniorityScore = sum(Seniority),\n    Recipients = make_set(Name, 50),\n    DistinctRecipients = dcount(Username)\n  by Domain\n| where DistinctRecipients >= 2\n| order by SeniorityScore desc\n| take 20\n```\n\n### Post-exploitation pivot from an indicator\n```kql\nlet victims =\n    Get_Event_FileCreation_All\n    | where Filename has \"\u003CINDICATOR>\"\n    | distinct Hostname;\nGet_Event_Process\n| where Hostname in (victims)\n| where ProcessCommandLine has_any (\"rundll32\", \"regsvr32\", \"powershell\", \"systeminfo\")\n| project EnvTime, Hostname, Username, ProcessName, ProcessCommandLine\n| order by EnvTime asc\n```\n\n### Suspicious outbound traffic enriched with identity\n```kql\nGet_Event_NetworkOutbound\n| invoke Extract_Event_Network_Domain()\n| where DomainName has_any (\"\u003CSUSPICIOUS_DOMAIN_1>\", \"\u003CSUSPICIOUS_DOMAIN_2>\")\n| invoke Enrich_Ip_Employee()\n| project EnvTime, Name, Role, DomainName, Url, ClientIp\n| order by EnvTime desc\n```\n\n### External IP authentication anomaly\n```kql\nGet_Event_Authentication_All\n| where not(ClientIp startswith \"10.\") and not(ClientIp startswith \"192.168.\")\n| summarize\n    Attempts = count(),\n    Failures = countif(Result == \"Failed Login\"),\n    Users = make_set(Username)\n  by ClientIp\n| order by Failures desc\n| take 20\n```\n\n## MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `kusto_query` | Execute IRQL pipelines against a Kusto database |\n| `kusto_table_schema_get` | Discover available tables and columns |\n| `kusto_cluster_list` | List available ADX clusters |\n| `kusto_database_list` | List databases in a cluster |\n\n## Opening Queries in Kusto Explorer (Windows Only)\n\n> **Optional convenience feature.** The default workflow is to output the KQL in chat and let the user copy it into Kusto Explorer or the VS Code Kusto extension manually. Auto-launch is opt-in only.\n\nAlways output the complete KQL query in the chat response with Step 1 (connect) and Step 2 (query) clearly labeled:\n\n```\n\u002F\u002F Step 1: Connect to your cluster (skip if already connected)\n\u002F\u002F Example: uncomment to connect to the KC7 training cluster\n\u002F\u002F #connect cluster('kc7001.eastus.kusto.windows.net').database('ValdyTimes')\n\u002F\u002F Or replace with your own cluster:\n\u002F\u002F #connect cluster('\u003CYOUR_CLUSTER>').database('\u003CYOUR_DATABASE>')\n\n\u002F\u002F Step 2: Run the query below\n\u003CKQL_QUERY>\n```\n\nIf the user asks to save or open in Kusto Explorer, follow the procedure in [references\u002FKUSTO_EXPLORER_LAUNCH.md](references\u002FKUSTO_EXPLORER_LAUNCH.md). Key rules:\n\n- Use `ask_user` to confirm before writing files or launching executables\n- Display file contents in chat so the user can review before opening\n- Never use shell interpolation or here-strings — write files via `Set-Content`\u002F`Add-Content`\n- Never encode queries into browser URLs\n- On macOS\u002FLinux, save the `.kql` file and suggest the VS Code Kusto extension or ADX Web Explorer\n- For graph visualization from IRQL data, see `azure-kusto-graph` and `azure-kusto-irql-graph`\n","# IRQL -- Incident Response Query Language\n\nCompose IRQL function pipelines from selector, extractor, and enricher building blocks. IRQL wraps raw KQL security tables behind intent-revealing, composable functions so analysts (and LLMs) can express hunts without memorizing schemas, cluster locations, or join keys.\n\n## Activation Triggers\n\nUse this skill when the user:\n- Explicitly mentions IRQL, `Get_*`, `Extract_*`, or `Enrich_*` functions\n- Says \"use IRQL\" or \"write an IRQL query\"\n- Requests a composable hunting pipeline using known IRQL selectors\n\nDo **not** activate for generic security queries (e.g. \"find failed logins\") unless the user explicitly asks for IRQL. Route those to `azure-kusto` instead.\n\n**Not a natural-language-to-IRQL converter.** This skill composes IRQL function pipelines and may handle basic natural-language requests that map directly to known selectors and simple filters. For general NL-to-KQL or NL-to-IRQL conversion, use a dedicated query-generation skill (available separately).\n\n## IRQL Function Preflight\n\nBefore generating a pipeline, verify IRQL is available on the target database:\n\n```kql\n.show functions\n| where Name startswith \"Get_\" or Name startswith \"Extract_\" or Name startswith \"Enrich_\"\n| project Name\n```\n\nIf no IRQL functions are found, inform the user that IRQL is not deployed on the target database and suggest using `azure-kusto` for raw KQL queries instead. IRQL functions are a prerequisite -- this skill does not deploy base IRQL selectors.\n\n## What IRQL Is\n\nIRQL is a **function-based dialect on top of KQL**. It provides:\n\n1. **Unified schema** -- disparate security tables project into consistent column names regardless of the underlying data source\n2. **Composability** -- small functions chain via `| invoke` to build complex hunts from simple steps\n3. **Portability** -- the same IRQL pipeline works across different clusters\u002Fdatabases; only the `Get_*` primitives need re-pointing\n\nIRQL is not a separate language. It's KQL functions you invoke. Any valid KQL works alongside IRQL functions.\n\n## Deploying IRQL\n\nIRQL functions are stored KQL functions (`.create-or-alter function`). They must already be deployed to the target database before this skill can generate pipelines.\n\n**Public example cluster** (functions pre-deployed):\n- Cluster: `https:\u002F\u002Fkc7001.eastus.kusto.windows.net`\n- Databases: `ValdyTimes`, `JoJosHospital`\n\nTo port IRQL to a new cluster\u002Fdatabase, create `Get_*` selectors that project your source tables into the unified schema (column names below), then deploy extractors and enrichers. The extractors and enrichers work unchanged as long as the input schema matches.\n\n## Function Catalog\n\n### 1. Selectors -- `Get_*`\n\nReturn projected, schema-unified views of source tables. Use the minimal form by default; use `_All` when extra columns are needed.\n\n| Function | Columns |\n|---|---|\n| `Get_Event_Authentication` | `EnvTime`, `Hostname`, `ClientIp`, `Username`, `Result` |\n| `Get_Event_Authentication_All` | + `Description`, `UserAgent`, `PasswordHash` |\n| `Get_Email` | `EnvTime`, `EmailSender`, `EmailRecipient`, `Subject`, `Url` |\n| `Get_Email_All` | + `ReplyTo`, `Verdict` |\n| `Get_Employees` | `Name`, `ClientIp`, `Email`, `Username`, `Hostname`, `Role` |\n| `Get_Employees_All` | + `HireDate`, `UserAgent`, `Domain` |\n| `Get_Event_FileCreation` | `EnvTime`, `Hostname`, `Filename`, `Path` |\n| `Get_Event_FileCreation_All` | + `Username`, `Sha256`, `ProcessName` |\n| `Get_Event_NetworkInbound` | `EnvTime`, `ClientIp`, `Url` |\n| `Get_Event_NetworkInbound_All` | + `Method`, `UserAgent`, `StatusCode` |\n| `Get_Event_NetworkOutbound` | `EnvTime`, `ClientIp`, `Url` |\n| `Get_Event_NetworkOutbound_All` | + `Method`, `UserAgent` |\n| `Get_Dns_All` | `EnvTime`, `Domain`, `ClientIp` |\n| `Get_Event_Process` | `EnvTime`, `ProcessCommandLine`, `ProcessName`, `Hostname`, `Username` |\n| `Get_Event_Process_All` | + `ParentProcessName`, `ParentProcessHash`, `ProcessHash` |\n| `Get_SecurityAlerts_All` | `EnvTime`, `AlertType`, `Severity`, `Description`, `Indicators` |\n| `Get_Network_Connection_All` | `EnvTime`, `SourceIp`, `SourcePort`, `DestinationIp`, `DestinationPort`, `Protocol`, `Bytes` |\n\n### 2. Extractors -- `Extract_*`\n\nDerive a new column from an existing one. Invoke after a selector.\n\n| Function | Input Column | Adds |\n|---|---|---|\n| `Extract_Email_Sender_Domain(T)` | `EmailSender` | `Domain` |\n| `Extract_Employee_Firstname(T)` | `Name` | `Firstname` |\n| `Extract_Event_Network_Domain(T)` | `Url` | `DomainName` |\n\n### 3. Enrichers -- `Enrich_*`\n\nLeft-join helpers that attach context from a related table.\n\n| Function | Key Column | Enriches With |\n|---|---|---|\n| `Enrich_Event_Authentication_Username(T)` | `Username` | Auth events for user |\n| `Enrich_Ip_Employee(T)` | `ClientIp` | Employee identity from IP |\n| `Enrich_Username_Employee(T)` | `Username` | Employee identity from username |\n| `Enrich_Ip_Domain(T)` | `ClientIp` | DNS domains resolved to IP |\n| `Enrich_Ip_Event_NetworkOutbound(T)` | `ClientIp` | Outbound network from IP |\n| `Enrich_Ip_Network_Connection(T)` | `ClientIp` | Network flows from IP |\n\n### 4. External Enrichment\n\n| Function | Source | Requirement |\n|---|---|---|\n| `Enrich_Sha256_VirusTotal(T)` | VirusTotal file report | API key + callout policy |\n| `Get_CISA_KEV()` \u002F `Enrich_CISA_KEV(T)` | CISA KEV catalog | Callout policy |\n\n## Composition Rules\n\n```\nSelector -> Extract -> Filter -> Enrich -> Summarize\u002FProject\n```\n\n1. **Start with a Selector**: `Get_Event_Authentication`, `Get_Email`, etc.\n2. **Extract** derived fields: `| invoke Extract_Email_Sender_Domain()`\n3. **Filter** to the signal: `| where Result == \"Failed Login\"`\n4. **Enrich** with context: `| invoke Enrich_Username_Employee()`\n5. **Summarize \u002F project** the answer\n\nAlways pipe (`|`) between steps. Extractors and Enrichers use `| invoke FunctionName()`.\n\n## Query Generation Guidelines\n\n- Use the **minimal selector** unless extra columns are needed -> then `_All`\n- Chain extractors before enrichers (extractors add columns enrichers may key on)\n- Place `where` filters as early as possible\n- Use `summarize` for aggregations, `project` for final column selection\n- End with `order by` + `take` to limit output\n\n## Examples\n\nFor additional prompts and worked examples, see [references\u002FEXAMPLES.md](references\u002FEXAMPLES.md).\n\n### Brute-force detection\n```kql\nGet_Event_Authentication\n| where Result == \"Failed Login\"\n| summarize FailedCount = count() by Username\n| where FailedCount > 19\n| invoke Enrich_Username_Employee()\n| project Username, Name, Role, Email, FailedCount\n| order by FailedCount desc\n```\n\n### Phishing triage by recipient seniority\n```kql\nGet_Email\n| invoke Extract_Email_Sender_Domain()\n| project EnvTime, EmailSender, Domain, Username = EmailRecipient, Subject, Url\n| invoke Enrich_Username_Employee()\n| extend Seniority = case(\n    Role has_any (\"CEO\", \"Chief\", \"Director\", \"VP\", \"President\"), 3,\n    Role has_any (\"Manager\", \"Lead\", \"Senior\"), 2,\n    1)\n| summarize\n    TotalEmails = count(),\n    SeniorityScore = sum(Seniority),\n    Recipients = make_set(Name, 50),\n    DistinctRecipients = dcount(Username)\n  by Domain\n| where DistinctRecipients >= 2\n| order by SeniorityScore desc\n| take 20\n```\n\n### Post-exploitation pivot from an indicator\n```kql\nlet victims =\n    Get_Event_FileCreation_All\n    | where Filename has \"\u003CINDICATOR>\"\n    | distinct Hostname;\nGet_Event_Process\n| where Hostname in (victims)\n| where ProcessCommandLine has_any (\"rundll32\", \"regsvr32\", \"powershell\", \"systeminfo\")\n| project EnvTime, Hostname, Username, ProcessName, ProcessCommandLine\n| order by EnvTime asc\n```\n\n### Suspicious outbound traffic enriched with identity\n```kql\nGet_Event_NetworkOutbound\n| invoke Extract_Event_Network_Domain()\n| where DomainName has_any (\"\u003CSUSPICIOUS_DOMAIN_1>\", \"\u003CSUSPICIOUS_DOMAIN_2>\")\n| invoke Enrich_Ip_Employee()\n| project EnvTime, Name, Role, DomainName, Url, ClientIp\n| order by EnvTime desc\n```\n\n### External IP authentication anomaly\n```kql\nGet_Event_Authentication_All\n| where not(ClientIp startswith \"10.\") and not(ClientIp startswith \"192.168.\")\n| summarize\n    Attempts = count(),\n    Failures = countif(Result == \"Failed Login\"),\n    Users = make_set(Username)\n  by ClientIp\n| order by Failures desc\n| take 20\n```\n\n## MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `kusto_query` | Execute IRQL pipelines against a Kusto database |\n| `kusto_table_schema_get` | Discover available tables and columns |\n| `kusto_cluster_list` | List available ADX clusters |\n| `kusto_database_list` | List databases in a cluster |\n\n## Opening Queries in Kusto Explorer (Windows Only)\n\n> **Optional convenience feature.** The default workflow is to output the KQL in chat and let the user copy it into Kusto Explorer or the VS Code Kusto extension manually. Auto-launch is opt-in only.\n\nAlways output the complete KQL query in the chat response with Step 1 (connect) and Step 2 (query) clearly labeled:\n\n```\n\u002F\u002F Step 1: Connect to your cluster (skip if already connected)\n\u002F\u002F Example: uncomment to connect to the KC7 training cluster\n\u002F\u002F #connect cluster('kc7001.eastus.kusto.windows.net').database('ValdyTimes')\n\u002F\u002F Or replace with your own cluster:\n\u002F\u002F #connect cluster('\u003CYOUR_CLUSTER>').database('\u003CYOUR_DATABASE>')\n\n\u002F\u002F Step 2: Run the query below\n\u003CKQL_QUERY>\n```\n\nIf the user asks to save or open in Kusto Explorer, follow the procedure in [references\u002FKUSTO_EXPLORER_LAUNCH.md](references\u002FKUSTO_EXPLORER_LAUNCH.md). Key rules:\n\n- Use `ask_user` to confirm before writing files or launching executables\n- Display file contents in chat so the user can review before opening\n- Never use shell interpolation or here-strings — write files via `Set-Content`\u002F`Add-Content`\n- Never encode queries into browser URLs\n- On macOS\u002FLinux, save the `.kql` file and suggest the VS Code Kusto extension or ADX Web Explorer\n- For graph visualization from IRQL data, see `azure-kusto-graph` and `azure-kusto-irql-graph`\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":12,"version":50},"0.0.0-placeholder","main","90929a087ad50fa0dd02fc396c9b8f721ddced08","plugins\u002Fazure-kusto-graph-skills\u002Fskills\u002Fazure-kusto-irql",225,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 03:43:10",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add microsoft\u002FGitHub-Copilot-for-Azure --skill azure-kusto-irql",{"tool":66,"command":67},"bunx","bunx skills add microsoft\u002FGitHub-Copilot-for-Azure --skill azure-kusto-irql",{"tool":69,"command":70},"pnpm","pnpm dlx skills add microsoft\u002FGitHub-Copilot-for-Azure --skill azure-kusto-irql","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-kusto-graph-skills\u002Fskills\u002Fazure-kusto-irql\u002FSKILL.md",true,[74,80,84],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002FEXAMPLES.md","REFERENCE","参考文档",2284,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-kusto-graph-skills\u002Fskills\u002Fazure-kusto-irql\u002Freferences\u002FEXAMPLES.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002FKUSTO_EXPLORER_LAUNCH.md",2659,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-kusto-graph-skills\u002Fskills\u002Fazure-kusto-irql\u002Freferences\u002FKUSTO_EXPLORER_LAUNCH.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"version.json",38,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-kusto-graph-skills\u002Fskills\u002Fazure-kusto-irql\u002Fversion.json",[89,112,138,163,188,210],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":44},"01M7153X40NMFY8DV2ATNDW060","azure-advisor-cost-optimization","Analyze Azure Advisor Cost\u002FIdleResources findings and prevalidate deletion safety, including Service Groups. WHEN: \"find unused Azure resources\", \"what resources am I paying for but no longer using\", \"idle-resource savings\", \"historical idle-resource savings\", \"are these idle resources safe to delete\". Generic Cost, other subcategories, and cross-category requests use azure-advisor.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-advisor\u002Fskills\u002Fazure-advisor-cost-optimization\u002FSKILL.md",[],[96,97,98,26,99,100,101,102,103,104,105,106,107,29,108,40,109,110,111,9],"azure advisor","Optimization","cost optimization","cost","advisor","azure advisor cost optimization","resources","generic","for","deletion","unused","use","analyze","delete","requests","find",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":44},"01M699ZWKYS4MRFW0KQM1FFCJK","foundry-iq","Foundry IQ knowledge bases. WHEN: make local or Blob documents searchable; create\u002Fdiagnose KBs; triage unsupported connectors or multi-source KB creation\u002Freconfiguration (even with classic-search terms); connect existing KB to agents (including multi-source KBs); create\u002Freuse a Search service; retrieve from an existing knowledge base with citations; no brand words needed. Read its procedure before query\u002Ftarget questions. NOT: other KB providers, repository-file search, classic Azure AI Search index\u002Fquery\u002Fapp work with no Foundry IQ KB or connector request, generic agent creation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Ffoundry-iq-skills\u002Fskills\u002Ffoundry-iq\u002FSKILL.md",[118],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,40,122,123,9,124,125,126,127,128,103,34,129,130,131,26,132,133,134,135,136,137,29,37],"foundry","foundry iq","triage","azure ai","connectors","app","Citations","brand","kb","diagnose","search","local","reuse","knowledge","foundry iq knowledge bases","connect","Existing","documents",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":44},"01M699ZT26E2D0VTWFZBBGJHMG","python-appservice-deploy","Deploy Python (Flask\u002FDjango\u002FFastAPI) code to Azure App Service Linux. WHEN: \"Flask App Service\", \"Django App Service\", \"FastAPI App Service\", \"deploy Python to App Service\". DO NOT USE FOR: Container Apps, Functions, non-Python, Terraform\u002FBicep\u002FIaC, full infra — use azure-prepare.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fpython-appservice-deploy\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[148,149,150,40,151,152,125,153,154,104,155,26,156,157,158,107,159,160,161,162,29],"python appservice deploy","deploy","python","linux","infra","do","django","azure app service","container","iac","fastapi","apps","code","functions","fastapi app",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":171,"publishedAt":44},"01M699ZR83J83TATQZKXHPXPF7","preset","Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002Fpreset\u002FSKILL.md",[169,170],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,149,172,9,173,174,153,175,176,104,177,178,179,26,180,181,182,107,183,184,185,186,187],"setup","capacity","customize","quick","availability","deployment","alternatives","selection","custom","deployments","high availability","version","across","check","multi","first",{"skillNo":189,"name":174,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":44},"01M699ZPM2ZHC9VXG582DY4268","Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard\u002FStandard\u002FProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002Fcustomize\u002FSKILL.md",[193],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,165,9,173,195,196,175,197,198,199,200,201,179,202,203,204,205,206,207,208,209,153,104,177],"policy","SET","processing","advanced","model","select","choose","configure","filter","azure openai","options","flow","openai","throughput","full",{"skillNo":211,"name":173,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":44},"01M699ZMCK9T4EM6NASDB940R7","Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FGitHub-Copilot-for-Azure\u002Fblob\u002Fmain\u002Fplugins\u002Fazure-skills\u002Fskills\u002Fmicrosoft-foundry\u002Fmodels\u002Fdeploy-model\u002Fcapacity\u002FSKILL.md",[],[173,165,149,9,174,216,199,217,130,218,219,220,184,204,221,222,207,223,224,153,176,104,225,177],"projects","project","analysis","listing","hand","limits","azure portal","direct","TPM","discovery"]