Creator · microsoft
Last updated · Sep 1, 2026
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, incide
Creator · microsoft
Last updated · Sep 1, 2026
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, incide
Creator · microsoft
Last updated · Sep 1, 2026
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, incide
Creator · microsoft
Last updated · Sep 1, 2026
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, incide
Do not auto-install
Install targets
Codex install prompt
Install the "azure-kusto-irql" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-kusto-graph-skills/skills/azure-kusto-irql. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"microsoft-azure-kusto-irql","task":"Install azure-kusto-irql","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Agent fit
Claude Code + Browser agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Maintenance
fresh
5d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
248
71/100 Quality · 65/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
248 GitHub stars
Repo activity
248 stars, 196 forks
Maintenance
5d since push
License
MIT
Install
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlDo not use when
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
Agent should check
Copy prompt
Task: Use azure-kusto-irql in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install
Install command: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
LLM text format
/api/skills/microsoft-azure-kusto-irql/install?format=text
Find alternatives
/api/skills/search?q=azure-kusto-irql&limit=3
Agent prompt
Use azure-kusto-irql for this task. Review https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install, then install with: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/microsoft-azure-kusto-irql
LLM text
/api/registry/manifest/microsoft-azure-kusto-irql?format=text
Install alias
/api/registry/install/microsoft-azure-kusto-irql
Recommend
/api/registry/recommend?task=Use%20azure-kusto-irql%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code, Browser agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
GitHub automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO248 GitHub stars
Stars/forks activity
INFO248 stars, 196 forks; issue activity unavailable in current metadata
Recent maintenance
PASS5d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: azure-kusto-irql description: "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." license: MIT metadata: author: Microsoft version: "0.0.0-placeholder" ---
# 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_*`, or `Enrich_*` 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:
```kql .show functions | where Name startswith "Get_" or Name startswith "Extract_" or Name startswith "Enrich_" | project Name ```
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 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:
1. **Unified schema** -- disparate security tables project into consistent column names regardless of the underlying data source 2. **Composability** -- small functions chain via `| invoke` to build complex hunts from simple steps 3. **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 ```
1. **Start with a Selector**: `Get_Event_Authentication`, `Get_Email`, etc. 2. **Extract** derived fields: `| invoke Extract_Email_Sender_Domain()` 3. **Filter** to the signal: `| where Result == "Failed Login"` 4. **Enrich** with context: `| invoke Enrich_Username_Employee()` 5. **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 `where` filters as early as possible - Use `summarize` for aggregations, `project` for final column selection - End with `order by` + `take` to limit output
## Examples
For additional prompts and worked examples, see [references/EXAMPLES.md](references/EXAMPLES.md).
### Brute-force detection ```kql 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 desc ```
### Phishing triage by recipient seniority ```kql 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 20 ```
### Post-exploitation pivot from an indicator ```kql 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 asc ```
### Suspicious outbound traffic enriched with identity ```kql 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 desc ```
### External IP authentication anomaly ```kql 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 20 ```
## MCP 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](references/KUSTO_EXPLORER_LAUNCH.md). Key rules:
- Use `ask_user` to 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 `.kql` file and suggest the VS Code Kusto extension or ADX Web Explorer - For graph visualization from IRQL data, see `azure-kusto-graph` and `azure-kusto-irql-graph`
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for azure-kusto-irql, ready for a manual X post.
azure-kusto-irql: Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigation... 248 stars https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x
Listing + install path for azure-kusto-irql: https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x Install: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to microsoft but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql/audit)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)microsoft
@microsoft
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsDo not auto-install
Install targets
Codex install prompt
Install the "azure-kusto-irql" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-kusto-graph-skills/skills/azure-kusto-irql. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"microsoft-azure-kusto-irql","task":"Install azure-kusto-irql","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Agent fit
Claude Code + Browser agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Maintenance
fresh
5d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
248
71/100 Quality · 65/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
248 GitHub stars
Repo activity
248 stars, 196 forks
Maintenance
5d since push
License
MIT
Install
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlDo not use when
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
Agent should check
Copy prompt
Task: Use azure-kusto-irql in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install
Install command: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
LLM text format
/api/skills/microsoft-azure-kusto-irql/install?format=text
Find alternatives
/api/skills/search?q=azure-kusto-irql&limit=3
Agent prompt
Use azure-kusto-irql for this task. Review https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install, then install with: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/microsoft-azure-kusto-irql
LLM text
/api/registry/manifest/microsoft-azure-kusto-irql?format=text
Install alias
/api/registry/install/microsoft-azure-kusto-irql
Recommend
/api/registry/recommend?task=Use%20azure-kusto-irql%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code, Browser agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
GitHub automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO248 GitHub stars
Stars/forks activity
INFO248 stars, 196 forks; issue activity unavailable in current metadata
Recent maintenance
PASS5d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: azure-kusto-irql description: "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." license: MIT metadata: author: Microsoft version: "0.0.0-placeholder" ---
# 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_*`, or `Enrich_*` 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:
```kql .show functions | where Name startswith "Get_" or Name startswith "Extract_" or Name startswith "Enrich_" | project Name ```
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 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:
1. **Unified schema** -- disparate security tables project into consistent column names regardless of the underlying data source 2. **Composability** -- small functions chain via `| invoke` to build complex hunts from simple steps 3. **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 ```
1. **Start with a Selector**: `Get_Event_Authentication`, `Get_Email`, etc. 2. **Extract** derived fields: `| invoke Extract_Email_Sender_Domain()` 3. **Filter** to the signal: `| where Result == "Failed Login"` 4. **Enrich** with context: `| invoke Enrich_Username_Employee()` 5. **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 `where` filters as early as possible - Use `summarize` for aggregations, `project` for final column selection - End with `order by` + `take` to limit output
## Examples
For additional prompts and worked examples, see [references/EXAMPLES.md](references/EXAMPLES.md).
### Brute-force detection ```kql 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 desc ```
### Phishing triage by recipient seniority ```kql 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 20 ```
### Post-exploitation pivot from an indicator ```kql 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 asc ```
### Suspicious outbound traffic enriched with identity ```kql 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 desc ```
### External IP authentication anomaly ```kql 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 20 ```
## MCP 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](references/KUSTO_EXPLORER_LAUNCH.md). Key rules:
- Use `ask_user` to 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 `.kql` file and suggest the VS Code Kusto extension or ADX Web Explorer - For graph visualization from IRQL data, see `azure-kusto-graph` and `azure-kusto-irql-graph`
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for azure-kusto-irql, ready for a manual X post.
azure-kusto-irql: Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigation... 248 stars https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x
Listing + install path for azure-kusto-irql: https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x Install: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to microsoft but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql/audit)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)microsoft
@microsoft
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsDo not auto-install
Install targets
Codex install prompt
Install the "azure-kusto-irql" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-kusto-graph-skills/skills/azure-kusto-irql. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"microsoft-azure-kusto-irql","task":"Install azure-kusto-irql","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Agent fit
Claude Code + Browser agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Maintenance
fresh
5d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
248
71/100 Quality · 65/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
248 GitHub stars
Repo activity
248 stars, 196 forks
Maintenance
5d since push
License
MIT
Install
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlDo not use when
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
Agent should check
Copy prompt
Task: Use azure-kusto-irql in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install
Install command: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
LLM text format
/api/skills/microsoft-azure-kusto-irql/install?format=text
Find alternatives
/api/skills/search?q=azure-kusto-irql&limit=3
Agent prompt
Use azure-kusto-irql for this task. Review https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install, then install with: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/microsoft-azure-kusto-irql
LLM text
/api/registry/manifest/microsoft-azure-kusto-irql?format=text
Install alias
/api/registry/install/microsoft-azure-kusto-irql
Recommend
/api/registry/recommend?task=Use%20azure-kusto-irql%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code, Browser agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
GitHub automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO248 GitHub stars
Stars/forks activity
INFO248 stars, 196 forks; issue activity unavailable in current metadata
Recent maintenance
PASS5d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: azure-kusto-irql description: "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." license: MIT metadata: author: Microsoft version: "0.0.0-placeholder" ---
# 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_*`, or `Enrich_*` 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:
```kql .show functions | where Name startswith "Get_" or Name startswith "Extract_" or Name startswith "Enrich_" | project Name ```
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 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:
1. **Unified schema** -- disparate security tables project into consistent column names regardless of the underlying data source 2. **Composability** -- small functions chain via `| invoke` to build complex hunts from simple steps 3. **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 ```
1. **Start with a Selector**: `Get_Event_Authentication`, `Get_Email`, etc. 2. **Extract** derived fields: `| invoke Extract_Email_Sender_Domain()` 3. **Filter** to the signal: `| where Result == "Failed Login"` 4. **Enrich** with context: `| invoke Enrich_Username_Employee()` 5. **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 `where` filters as early as possible - Use `summarize` for aggregations, `project` for final column selection - End with `order by` + `take` to limit output
## Examples
For additional prompts and worked examples, see [references/EXAMPLES.md](references/EXAMPLES.md).
### Brute-force detection ```kql 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 desc ```
### Phishing triage by recipient seniority ```kql 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 20 ```
### Post-exploitation pivot from an indicator ```kql 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 asc ```
### Suspicious outbound traffic enriched with identity ```kql 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 desc ```
### External IP authentication anomaly ```kql 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 20 ```
## MCP 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](references/KUSTO_EXPLORER_LAUNCH.md). Key rules:
- Use `ask_user` to 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 `.kql` file and suggest the VS Code Kusto extension or ADX Web Explorer - For graph visualization from IRQL data, see `azure-kusto-graph` and `azure-kusto-irql-graph`
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for azure-kusto-irql, ready for a manual X post.
azure-kusto-irql: Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigation... 248 stars https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x
Listing + install path for azure-kusto-irql: https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x Install: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to microsoft but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql/audit)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)microsoft
@microsoft
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsDo not auto-install
Install targets
Codex install prompt
Install the "azure-kusto-irql" agent skill from https://github.com/microsoft/GitHub-Copilot-for-Azure/tree/main/plugins/azure-kusto-graph-skills/skills/azure-kusto-irql. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"microsoft-azure-kusto-irql","task":"Install azure-kusto-irql","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Agent fit
Claude Code + Browser agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Maintenance
fresh
5d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
248
71/100 Quality · 65/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
248 GitHub stars
Repo activity
248 stars, 196 forks
Maintenance
5d since push
License
MIT
Install
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlDo not use when
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
Agent should check
Copy prompt
Task: Use azure-kusto-irql in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20azure-kusto-irql%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install
Install command: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/microsoft-azure-kusto-irql/install
LLM text format
/api/skills/microsoft-azure-kusto-irql/install?format=text
Find alternatives
/api/skills/search?q=azure-kusto-irql&limit=3
Agent prompt
Use azure-kusto-irql for this task. Review https://www.openagentskill.com/api/skills/microsoft-azure-kusto-irql/install, then install with: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irqlRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/microsoft-azure-kusto-irql
LLM text
/api/registry/manifest/microsoft-azure-kusto-irql?format=text
Install alias
/api/registry/install/microsoft-azure-kusto-irql
Recommend
/api/registry/recommend?task=Use%20azure-kusto-irql%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code, Browser agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
GitHub automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
INFO248 GitHub stars
Stars/forks activity
INFO248 stars, 196 forks; issue activity unavailable in current metadata
Recent maintenance
PASS5d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: azure-kusto-irql description: "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." license: MIT metadata: author: Microsoft version: "0.0.0-placeholder" ---
# 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_*`, or `Enrich_*` 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:
```kql .show functions | where Name startswith "Get_" or Name startswith "Extract_" or Name startswith "Enrich_" | project Name ```
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 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:
1. **Unified schema** -- disparate security tables project into consistent column names regardless of the underlying data source 2. **Composability** -- small functions chain via `| invoke` to build complex hunts from simple steps 3. **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 ```
1. **Start with a Selector**: `Get_Event_Authentication`, `Get_Email`, etc. 2. **Extract** derived fields: `| invoke Extract_Email_Sender_Domain()` 3. **Filter** to the signal: `| where Result == "Failed Login"` 4. **Enrich** with context: `| invoke Enrich_Username_Employee()` 5. **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 `where` filters as early as possible - Use `summarize` for aggregations, `project` for final column selection - End with `order by` + `take` to limit output
## Examples
For additional prompts and worked examples, see [references/EXAMPLES.md](references/EXAMPLES.md).
### Brute-force detection ```kql 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 desc ```
### Phishing triage by recipient seniority ```kql 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 20 ```
### Post-exploitation pivot from an indicator ```kql 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 asc ```
### Suspicious outbound traffic enriched with identity ```kql 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 desc ```
### External IP authentication anomaly ```kql 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 20 ```
## MCP 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](references/KUSTO_EXPLORER_LAUNCH.md). Key rules:
- Use `ask_user` to 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 `.kql` file and suggest the VS Code Kusto extension or ADX Web Explorer - For graph visualization from IRQL data, see `azure-kusto-graph` and `azure-kusto-irql-graph`
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for azure-kusto-irql, ready for a manual X post.
azure-kusto-irql: Compose IRQL (Incident Response Query Language) queries for Kusto cybersecurity investigation... 248 stars https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x
Listing + install path for azure-kusto-irql: https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=x Install: npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to microsoft but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql/audit)
[](https://www.openagentskill.com/skills/microsoft-azure-kusto-irql?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)microsoft
@microsoft
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Do not auto-install
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
🕵️♂️ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsPermission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness