azure-kusto-irql
Skill1.6k starsChanged 19 days agoMITView on GitHub
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.
3 other projects use a version of this, 1 of them edited.
Trending
More talk lately.about the whole repository
Most recently taken up by
- microsoft/GitHub-Copilot-for-Azureedited, first seen Oct 13, 2026
- microsoft/skillsword for word, first seen Oct 13, 2026
- microsoft/agent-skillsword for word, first seen Oct 8, 2026
Who's talking about microsoft/azure-skills
- microsoft/apm“Fold marketplace authoring config into apm.yml as the single APM surface”GitHub · Apr 29, 2026 · 2 reactions
- salaboy/skills-oci“Support for Skill Collections”GitHub · Jul 3, 2026 · 1 reactions
- Azure/azure-dev“Add `azd tool install/upgrade azure-skills` with per-host selection”GitHub · Jun 18, 2026 · 1 reactions
- microsoft/apm“feat(pack): unify 'apm pack' to produce bundle and marketplace.json (closes #722)”GitHub · Apr 29, 2026 · 1 reactions
- microsoft/GitHub-Copilot-for-Azure“Update CHANGELOG.md when syncing plugin content”GitHub · Apr 16, 2026 · 1 reactions
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Apr 29, 2026Fold marketplace authoring config into apm.yml as the single APM surface — microsoft/apm2 reactions
- Jul 3, 2026Support for Skill Collections — salaboy/skills-oci1 reaction
- Jun 18, 2026Add `azd tool install/upgrade azure-skills` with per-host selection — Azure/azure-dev1 reaction · 1 comment
- Apr 29, 2026feat(pack): unify 'apm pack' to produce bundle and marketplace.json (closes #722) — microsoft/apm1 reaction · 1 comment
- Apr 16, 2026Update CHANGELOG.md when syncing plugin content — microsoft/GitHub-Copilot-for-Azure1 reaction · 2 comments
45 more on GitHub
- Nov 14, 2026agent-skills.github.microsoft.azure-skills: 1.2.123 → 1.2.124 — sudosubin/agents.nix0 reactions
- Nov 13, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.123 → 1.2.124 — sudosubin/agents.nix0 reactions
- Nov 13, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.123 → 1.2.124 — sudosubin/agents.nix0 reactions
- Nov 13, 2026agent-plugins.github.microsoft.azure-skills: 1.2.123 → 1.2.124 — sudosubin/agents.nix0 reactions
- Nov 13, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.123 → 1.2.124 — sudosubin/agents.nix0 reactions
- Nov 13, 2026[Skill Bug]: prereq native-module unknown guidance conflicts with Boolean schema — microsoft/GitHub-Copilot-for-Azure0 reactions · 1 comment
- Nov 13, 2026agent-skills.github.microsoft.azure-skills: 1.2.122 → 1.2.123 — sudosubin/agents.nix0 reactions
- Nov 12, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.122 → 1.2.123 — sudosubin/agents.nix0 reactions
- Nov 12, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.122 → 1.2.123 — sudosubin/agents.nix0 reactions
- Nov 12, 2026agent-plugins.github.microsoft.azure-skills: 1.2.122 → 1.2.123 — sudosubin/agents.nix0 reactions
- Nov 12, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.122 → 1.2.123 — sudosubin/agents.nix0 reactions
- Nov 10, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.120 → 1.2.122 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-skills.github.microsoft.azure-skills: 1.2.120 → 1.2.122 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.120 → 1.2.122 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.120 → 1.2.122 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-plugins.github.microsoft.azure-skills: 1.2.120 → 1.2.122 — sudosubin/agents.nix0 reactions
- Nov 10, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.118 → 1.2.120 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.118 → 1.2.120 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-skills.github.microsoft.azure-skills: 1.2.118 → 1.2.120 — sudosubin/agents.nix0 reactions
- Nov 10, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.118 → 1.2.120 — sudosubin/agents.nix0 reactions
- Nov 10, 2026agent-plugins.github.microsoft.azure-skills: 1.2.118 → 1.2.120 — sudosubin/agents.nix0 reactions
- Nov 9, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.115 → 1.2.118 — sudosubin/agents.nix0 reactions
- Nov 9, 2026chore: sync azure plugin name and version to apm.yml — microsoft/GitHub-Copilot-for-Azure0 reactions
- Nov 9, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.115 → 1.2.118 — sudosubin/agents.nix0 reactions
- Nov 9, 2026agent-skills.github.microsoft.azure-skills: 1.2.115 → 1.2.118 — sudosubin/agents.nix0 reactions
- Nov 9, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.115 → 1.2.118 — sudosubin/agents.nix0 reactions
- Nov 9, 2026agent-plugins.github.microsoft.azure-skills: 1.2.115 → 1.2.118 — sudosubin/agents.nix0 reactions
- Nov 7, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.114 → 1.2.115 — sudosubin/agents.nix0 reactions
- Nov 6, 2026agent-skills.github.microsoft.azure-skills: 1.2.114 → 1.2.115 — sudosubin/agents.nix0 reactions
- Nov 6, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.114 → 1.2.115 — sudosubin/agents.nix0 reactions
- Nov 6, 2026agent-plugins.github.microsoft.azure-skills: 1.2.114 → 1.2.115 — sudosubin/agents.nix0 reactions
- Nov 6, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.114 → 1.2.115 — sudosubin/agents.nix0 reactions
- Nov 6, 2026agent-skills.github.microsoft.azure-skills: 1.2.113 → 1.2.114 — sudosubin/agents.nix0 reactions
- Nov 5, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.113 → 1.2.114 — sudosubin/agents.nix0 reactions
- Nov 5, 2026agent-plugins.github.microsoft.azure-skills: 1.2.113 → 1.2.114 — sudosubin/agents.nix0 reactions
- Nov 5, 2026copilot-plugins.github.microsoft.azure-skills: 1.2.113 → 1.2.114 — sudosubin/agents.nix0 reactions
- Nov 5, 2026claude-code-marketplaces.github.microsoft.azure-skills: 1.2.113 → 1.2.114 — sudosubin/agents.nix0 reactions
- Nov 5, 2026agent-plugins.github.microsoft.azure-skills: init at 1.2.113 — sudosubin/agents.nix0 reactions
- Nov 4, 2026agent-skills.github.microsoft.azure-skills: 1.2.111 → 1.2.113 — sudosubin/agents.nix0 reactions
- Nov 4, 2026claude-code-plugins.github.microsoft.azure-skills: 1.2.111 → 1.2.113 — sudosubin/agents.nix0 reactions
- Nov 4, 2026agent-skills.github.microsoft.azure-skills: 1.2.110 → 1.2.111 — sudosubin/agents.nix0 reactions
- Nov 2, 2026agent-skills.github.microsoft.azure-skills: 1.2.109 → 1.2.110 — sudosubin/agents.nix0 reactions
- Nov 2, 2026chore: bump external skill pins — jthiruveedula/agentkit0 reactions
- Oct 30, 2026agent-skills.github.microsoft.azure-skills: 1.2.108 → 1.2.109 — sudosubin/agents.nix0 reactions
- Oct 29, 2026agent-skills.github.microsoft.azure-skills: 1.2.106 → 1.2.108 — sudosubin/agents.nix0 reactions
Other versions3 projects use a version of this.
Word for word · 2
- microsoft/skills★ 3.2k100% same
- microsoft/agent-skills★ 3.2k100% same
Edited · 1
- microsoft/GitHub-Copilot-for-Azure★ 26499% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository88 other files it gives its agents.
- aks-cost-optimizationSkill
- aks-gpu-inferenceSkill
- aks-known-issuesSkill
- aks-network-captureSkill
- aks-troubleshootingSkill
- azure-search-navSkill
- azure-advisor-actionabilitySkill
- azure-advisor-cost-optimizationSkill
- azure-advisorSkill
- cost-analysisSkill
- cost-estimationSkill
- cost-governanceSkill
- cost-optimizationSkill
- azure-kusto-graphSkill
- azure-kusto-irql-graphSkill
- azure-local-multi-rackSkill
- azure-localSkill
- airunway-aks-setupSkill
- appinsights-instrumentationSkill
- azure-aigatewaySkill
- azure-aiSkill
- azure-app-onboard-prereqSkill
- azure-app-onboardSkill
- azure-cloud-migrateSkill
- azure-complianceSkill
- azure-computeSkill
- azure-deploySkill
- azure-diagnosticsSkill
- azure-enterprise-infra-plannerSkill
- azure-kubernetes-app-deploySkill
- azure-kubernetes-automatic-readinessSkill
- azure-kubernetesSkill
- azure-kustoSkill
- azure-messagingSkill
- azure-prepareSkill
- azure-quotasSkill
- azure-reliabilitySkill
- azure-resource-lookupSkill
- azure-resource-visualizerSkill
- azure-storageSkill
- azure-upgradeSkill
- azure-validateSkill
- discover-azure-skillsSkill
- entra-agent-idSkill
- entra-app-registrationSkill
- finetuningSkill
- capacitySkill
- customizeSkill
- presetSkill
- deploy-modelSkill
- microsoft-foundrySkill
- python-appservice-deploySkill
- foundry-iqSkill
- airunway-aks-setupSkill
- appinsights-instrumentationSkill
- azure-aigatewaySkill
- azure-aiSkill
- azure-app-onboard-prereqSkill
- azure-app-onboardSkill
- azure-cloud-migrateSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 4 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this skill when the user:
- Very specific: line 21
Do not activate for generic security queries (e.g.
- Distinctive: line 27
Before generating a pipeline, verify IRQL is available on the target database:
- Very specific: line 35
If 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 …
- Very specific: line 125
Always pipe (|) between steps.
- Very specific: line 129
Use the minimal selector unless extra columns are needed -> then _All
- Very specific: line 131
Place where filters as early as possible
- Very specific: line 132
Use summarize for aggregations, project for final column selection
- Distinctive: line 220
Always output the complete KQL query in the chat response with Step 1 (connect) and Step 2 (query) clearly labeled:
- Very specific: line 233
If the user asks to save or open in Kusto Explorer, follow the procedure in references/KUSTO_EXPLORER_LAUNCH.md.
- Very specific: line 235
Use ask_user to confirm before writing files or launching executables
- Very specific: line 237
Never use shell interpolation or here-strings — write files via Set-Content/Add-Content
- Distinctive: line 238
Never encode queries into browser URLs
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
IRQL -- Incident Response Query Language
Compose 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.
Activation Triggers
Use this skill when the user:
- Explicitly mentions IRQL,
Get_*,Extract_*, orEnrich_*functions - Says "use IRQL" or "write an IRQL query"
- Requests a composable hunting pipeline using known IRQL selectors
Do not activate for generic security queries (e.g. "find failed logins") unless the user explicitly asks for IRQL. Route those to azure-kusto instead.
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).
IRQL Function Preflight
Before generating a pipeline, verify IRQL is available on the target database:
.show functions
| where Name startswith "Get_" or Name startswith "Extract_" or Name startswith "Enrich_"
| project NameIf 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.
What IRQL Is
IRQL is a function-based dialect on top of KQL. It provides:
- Unified schema -- disparate security tables project into consistent column names regardless of the underlying data source
- Composability -- small functions chain via
| invoketo build complex hunts from simple steps - Portability -- the same IRQL pipeline works across different clusters/databases; only the
Get_*primitives need re-pointing
IRQL is not a separate language. It's KQL functions you invoke. Any valid KQL works alongside IRQL functions.
Deploying IRQL
IRQL functions are stored KQL functions (.create-or-alter function). They must already be deployed to the target database before this skill can generate pipelines.
Public example cluster (functions pre-deployed):
- Cluster:
https://kc7001.eastus.kusto.windows.net - Databases:
ValdyTimes,JoJosHospital
To port IRQL to a new cluster/database, 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.
Function Catalog
1. Selectors -- Get_*
Return projected, schema-unified views of source tables. Use the minimal form by default; use _All when extra columns are needed.
| Function | Columns |
Get_Event_Authentication | EnvTime, Hostname, ClientIp, Username, Result |
Get_Event_Authentication_All | + Description, UserAgent, PasswordHash |
Get_Email | EnvTime, EmailSender, EmailRecipient, Subject, Url |
Get_Email_All | + ReplyTo, Verdict |
Get_Employees | Name, ClientIp, Email, Username, Hostname, Role |
Get_Employees_All | + HireDate, UserAgent, Domain |
Get_Event_FileCreation | EnvTime, Hostname, Filename, Path |
Get_Event_FileCreation_All | + Username, Sha256, ProcessName |
Get_Event_NetworkInbound | EnvTime, ClientIp, Url |
Get_Event_NetworkInbound_All | + Method, UserAgent, StatusCode |
Get_Event_NetworkOutbound | EnvTime, ClientIp, Url |
Get_Event_NetworkOutbound_All | + Method, UserAgent |
Get_Dns_All | EnvTime, Domain, ClientIp |
Get_Event_Process | EnvTime, ProcessCommandLine, ProcessName, Hostname, Username |
Get_Event_Process_All | + ParentProcessName, ParentProcessHash, ProcessHash |
Get_SecurityAlerts_All | EnvTime, AlertType, Severity, Description, Indicators |
Get_Network_Connection_All | EnvTime, SourceIp, SourcePort, DestinationIp, DestinationPort, Protocol, Bytes |
2. Extractors -- Extract_*
Derive a new column from an existing one. Invoke after a selector.
| Function | Input Column | Adds |
Extract_Email_Sender_Domain(T) | EmailSender | Domain |
Extract_Employee_Firstname(T) | Name | Firstname |
Extract_Event_Network_Domain(T) | Url | DomainName |
3. Enrichers -- Enrich_*
Left-join helpers that attach context from a related table.
| Function | Key Column | Enriches With |
Enrich_Event_Authentication_Username(T) | Username | Auth events for user |
Enrich_Ip_Employee(T) | ClientIp | Employee identity from IP |
Enrich_Username_Employee(T) | Username | Employee identity from username |
Enrich_Ip_Domain(T) | ClientIp | DNS domains resolved to IP |
Enrich_Ip_Event_NetworkOutbound(T) | ClientIp | Outbound network from IP |
Enrich_Ip_Network_Connection(T) | ClientIp | Network flows from IP |
4. External Enrichment
| Function | Source | Requirement |
Enrich_Sha256_VirusTotal(T) | VirusTotal file report | API key + callout policy |
Get_CISA_KEV() / Enrich_CISA_KEV(T) | CISA KEV catalog | Callout policy |
Composition Rules
Selector -> Extract -> Filter -> Enrich -> Summarize/Project- Start with a Selector:
Get_Event_Authentication,Get_Email, etc. - Extract derived fields:
| invoke Extract_Email_Sender_Domain() - Filter to the signal:
| where Result == "Failed Login" - Enrich with context:
| invoke Enrich_Username_Employee() - Summarize / project the answer
Always pipe (|) between steps. Extractors and Enrichers use | invoke FunctionName().
Query Generation Guidelines
- Use the minimal selector unless extra columns are needed -> then
_All - Chain extractors before enrichers (extractors add columns enrichers may key on)
- Place
wherefilters as early as possible - Use
summarizefor aggregations,projectfor final column selection - End with
order by+taketo limit output
Examples
For additional prompts and worked examples, see references/EXAMPLES.md.
Brute-force detection
Get_Event_Authentication
| where Result == "Failed Login"
| summarize FailedCount = count() by Username
| where FailedCount > 19
| invoke Enrich_Username_Employee()
| project Username, Name, Role, Email, FailedCount
| order by FailedCount descPhishing triage by recipient seniority
Get_Email
| invoke Extract_Email_Sender_Domain()
| project EnvTime, EmailSender, Domain, Username = EmailRecipient, Subject, Url
| invoke Enrich_Username_Employee()
| extend Seniority = case(
Role has_any ("CEO", "Chief", "Director", "VP", "President"), 3,
Role has_any ("Manager", "Lead", "Senior"), 2,
1)
| summarize
TotalEmails = count(),
SeniorityScore = sum(Seniority),
Recipients = make_set(Name, 50),
DistinctRecipients = dcount(Username)
by Domain
| where DistinctRecipients >= 2
| order by SeniorityScore desc
| take 20Post-exploitation pivot from an indicator
let victims =
Get_Event_FileCreation_All
| where Filename has "<INDICATOR>"
| distinct Hostname;
Get_Event_Process
| where Hostname in (victims)
| where ProcessCommandLine has_any ("rundll32", "regsvr32", "powershell", "systeminfo")
| project EnvTime, Hostname, Username, ProcessName, ProcessCommandLine
| order by EnvTime ascSuspicious outbound traffic enriched with identity
Get_Event_NetworkOutbound
| invoke Extract_Event_Network_Domain()
| where DomainName has_any ("<SUSPICIOUS_DOMAIN_1>", "<SUSPICIOUS_DOMAIN_2>")
| invoke Enrich_Ip_Employee()
| project EnvTime, Name, Role, DomainName, Url, ClientIp
| order by EnvTime descExternal IP authentication anomaly
Get_Event_Authentication_All
| where not(ClientIp startswith "10.") and not(ClientIp startswith "192.168.")
| summarize
Attempts = count(),
Failures = countif(Result == "Failed Login"),
Users = make_set(Username)
by ClientIp
| order by Failures desc
| take 20MCP Tools Used
| Tool | Purpose |
kusto_query | Execute IRQL pipelines against a Kusto database |
kusto_table_schema_get | Discover available tables and columns |
kusto_cluster_list | List available ADX clusters |
kusto_database_list | List databases in a cluster |
Opening Queries in Kusto Explorer (Windows Only)
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.
Always output the complete KQL query in the chat response with Step 1 (connect) and Step 2 (query) clearly labeled:
// Step 1: Connect to your cluster (skip if already connected)
// Example: uncomment to connect to the KC7 training cluster
// #connect cluster('kc7001.eastus.kusto.windows.net').database('ValdyTimes')
// Or replace with your own cluster:
// #connect cluster('<YOUR_CLUSTER>').database('<YOUR_DATABASE>')
// Step 2: Run the query below
<KQL_QUERY>If the user asks to save or open in Kusto Explorer, follow the procedure in references/KUSTO_EXPLORER_LAUNCH.md. Key rules:
- Use
ask_userto confirm before writing files or launching executables - Display file contents in chat so the user can review before opening
- Never use shell interpolation or here-strings — write files via
Set-Content/Add-Content - Never encode queries into browser URLs
- On macOS/Linux, save the
.kqlfile and suggest the VS Code Kusto extension or ADX Web Explorer - For graph visualization from IRQL data, see
azure-kusto-graphandazure-kusto-irql-graph
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

