Official agent skill

Azure Kusto Irql Graph

by microsoft in microsoft/GitHub-Copilot-for-Azure

Apply IRQL graph functions to KQL or IRQL query results for Kusto Explorer visualization.

OfficialMITAuto-check passed

Install Azure Kusto Irql Graph

skills CLI
$ npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql-graph -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/GitHub-Copilot-for-Azure azure-kusto-irql-graph --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/GitHub-Copilot-for-Azure.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/azure-kusto-graph-skills/skills/azure-kusto-irql-graph .claude/skills/azure-kusto-irql-graph && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
azure-kusto-irql-graph
GitHub stars
255
Token cost
~4.8k tokens
SKILL.md length
1,488 words
Files
5 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Apply IRQL graph functions to KQL or IRQL query results for Kusto Explorer visualization.

  • Works in 6 steps: Identify entities -> each distinct noun… → Identify relationships -> each… → Map to columns -> use actual columns… → …
  • SKILL.md covers Scope and Routing, Input Contract, Activation Triggers and Environment, plus 8 more sections
  • Reaches raw.githubusercontent.com and kc7001.eastus.kusto.windows.net

What it does

Azure Kusto Irql Graph is an agent skill from microsoft/GitHub-Copilot-for-Azure, published by the product's own GitHub organization. Apply IRQL graph functions to KQL or IRQL query results for Kusto Explorer visualization. Generates LiftToGraph mappings and composes GraphRenderView, GraphFoldByProperty, ExtractNode, EnrichNode, and EnrichGraph calls. Accepts a supplied query or limited basic natural-language source request; it is not a general natural-language-to-KQL/IRQL skill. WHEN: LiftToGraph, GraphRenderView, GraphFoldByProperty, IRQL graph enrichment, graph mapping for existing query results, icon-decorated graph, fold graph nodes. Use…

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/DEPLOY_IRQL_FUNCTIONS.md`, `references/EXAMPLES.md` and `references/KUSTO_EXPLORER_LAUNCH.md`).

It works with Microsoft Azure and Microsoft Sentinel. The repository describes itself as: GitHub Copilot for Azure. The licence is MIT.

Example prompts

  • “/azure-kusto-irql-graph”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify entities -> each distinct noun becomes a node_type
  2. Identify relationships -> each verb/preposition becomes an edge
  3. Map to columns -> use actual columns produced by the supplied query; never assume unavailable columns
  4. Set direction -> source is the actor, target is the acted-upon
  5. Add properties -> include columns relevant to investigation (timestamps, results, hashes)
  6. Assign icons -> pick from the icon set above based on entity type

What it can do on your machine

Read from SKILL.md and the folder at commit ce94fce. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are kql).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • raw.githubusercontent.com
    • kc7001.eastus.kusto.windows.net

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Azure Kusto Irql Graph loads about 4.8k tokens when it runs, and up to ~9.2k if it reads all its reference files. Until then it costs about 169 tokens; SKILL.md has 1,488 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~169
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/GitHub-Copilot-for-Azure at commit ce94fce, republished under its MIT licence (© microsoft). 1,488 words, ~4,781 tokens.

Download SKILL.mdSave it as .claude/skills/azure-kusto-irql-graph/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
azure-kusto-irql-graph
description
Apply IRQL graph functions to KQL or IRQL query results for Kusto Explorer visualization. Generates Lift_To_Graph mappings and composes Graph_Render_View, Graph_Fold_By_Property, Extract_Node_*, Enrich_Node_*, and Enrich_Graph_* calls. Accepts a supplied query or limited basic natural-language source request; it is not a general natural-language-to-KQL/IRQL skill. WHEN: Lift_To_Graph, Graph_Render_View, Graph_Fold_By_Property, IRQL graph enrichment, graph mapping for existing query results, icon-decorated graph, fold graph nodes. Use azure-kusto-graph for native make-graph analysis, graph-match, shortest paths, components, or persistent graphs.
license
MIT
metadata.author
Microsoft
metadata.version
0.0.0-placeholder

IRQL Graph Functions -- Query Results to Visualization

Apply the IRQL graph function family to tabular results. Given a KQL or IRQL query and the user's graph description, generate a Lift_To_Graph mapping and compose only the stored graph functions needed to visualize, fold, extract, or enrich the graph in Kusto Explorer. The source query does not need to use IRQL.

Scope and Routing

RequestUse
Turn supplied KQL/IRQL rows into an icon-decorated visual graphThis skill: Lift_To_Graph + Graph_Render_View
Fold nodes or apply Extract_Node_*, Enrich_Node_*, or Enrich_Graph_*This skill
Use make-graph, graph-match, shortest paths, connected components, graph models, or snapshotsazure-kusto-graph
Author a non-trivial KQL/IRQL investigation from natural languageA Kusto or IRQL query-generation skill, then this skill

If a request mixes visualization and native graph analysis, use this skill for the lift/render portion and azure-kusto-graph for operator semantics. Do not replace graph-lift functions with a hand-built edges-first graph unless the user asks for native graph operators.

Input Contract

  • Preferred input: a working KQL/IRQL query that produces tabular results, plus a natural-language description of the desired nodes, edges, labels, icons, extracts, enrichments, or folds.
  • This skill is not a natural-language-to-KQL or NL-to-IRQL converter. It transforms existing query results into graph visualizations. For general NL-to-KQL or NL-to-IRQL conversion, use a dedicated query-generation skill (available separately).
  • Preserve the supplied query's retrieval, joins, filters, and aggregations. Add only projections or synthetic IDs required by the graph mapping.
  • A basic natural-language source request is supported only when it maps directly to one known table or IRQL Get_* selector with obvious columns and simple filters. State the assumed source, and do not invent joins, schema, or investigation logic.
  • For non-trivial query construction, use a separate Kusto/IRQL query-generation skill first, then apply this skill to its output.
  • If no query or output schema is available and the source is not trivial, request the KQL query or its result columns before generating a mapping.

Activation Triggers

Use this skill when the user:

  • Supplies KQL/IRQL results and asks for an IRQL graph visualization or mapping
  • Mentions Lift_To_Graph, Graph_Render_View, or Graph_Fold_By_Property
  • Asks for icon-decorated node/edge mappings in Kusto Explorer
  • Wants to fold/collapse nodes by a shared property
  • Requests graph extraction or enrichment through Extract_Node_*, Enrich_Node_*, or Enrich_Graph_*

Do not activate this skill solely for graph-match, graph paths/components, persistent graphs, or generic make-graph construction; those belong to azure-kusto-graph.

Not a natural-language-to-KQL/IRQL converter. The input should generally be a working KQL or IRQL query whose results need graph visualization. Basic NL source requests work only for trivial single-table/selector cases. For general NL-to-KQL or NL-to-IRQL, use a dedicated query-generation skill (available separately).

Environment

  • Cluster: https://kc7001.eastus.kusto.windows.net
  • Databases: ValdyTimes, JoJosHospital (graph functions pre-deployed)
  • Rendering: Kusto Explorer desktop app (make-graph visualization window)
  • Tool: kusto_query (via Azure MCP Server)
Function Preflight

Lift_To_Graph and Graph_Render_View are stored functions, not built-in Kusto operators. Before generating or running a lift pipeline against a target database, check what is deployed:

kql
.show functions
| where Name in~ ("Lift_To_Graph", "Graph_Render_View", "Graph_Fold_By_Property")
| project Name
  • Lift_To_Graph and Graph_Render_View are required.
  • Graph_Fold_By_Property is required only when folding is requested.
  • Check any Extract_Node_*, Enrich_Node_*, or Enrich_Graph_* function before using it; omit optional enrichment when unavailable unless the user wants it deployed.
  • If a required function is missing and you have permission to alter the database, ask the user for confirmation before deploying. Then use the .create-or-alter function definitions in references/DEPLOY_IRQL_FUNCTIONS.md. Run the relevant .create-or-alter block, then rerun the preflight check to confirm.
  • If you do not have alter permissions, tell the user which functions are missing and point them to references/DEPLOY_IRQL_FUNCTIONS.md for manual deployment.

IRQL Graph Function Family

Lift_To_Graph(T, mappingJson)

Transforms any tabular KQL result into a unified node + edge table.

Input: Any table T + a JSON mapping string. Output: Rows with EntityType = "node" or "edge", ready for make-graph.

Graph_Render_View(T)

Takes Lift_To_Graph output, splits nodes/edges, and calls make-graph to open Kusto Explorer's graph window.

Graph_Fold_By_Property(T, NodeType, PropertyName)

Collapses nodes of a given type sharing a property value into a single node. Rewires edges automatically.

Graph Extraction and Enrichment Functions

These are additional stored functions that must already be deployed on the target database. They are not bundled in references/DEPLOY_IRQL_FUNCTIONS.md. Use .show functions to verify availability before including in a pipeline.

FunctionOperationKey Property
Extract_Node_Email_Sender_Domain(T, displayName)Adds Domain to node propsEmailSender
Extract_Node_Employee_Firstname(T, displayName)Adds Firstname to node propsName
Extract_Node_Event_Network_Domain(T, displayName)Adds DomainName to node propsUrl
Enrich_Node_Ip_Employee(T, displayName)Adds employee info to IP nodesClientIp
Enrich_Node_Username_Employee(T, displayName)Adds employee info to user nodesUsername
Enrich_Node_Event_Authentication_Username(T, displayName)Adds auth contextUsername
Enrich_Node_Ip_Domain(T, displayName)Adds DNS domainsClientIp
Enrich_Node_Ip_Event_NetworkOutbound(T, displayName)Adds outbound eventsClientIp
Enrich_Graph_Ip_Employee(T, mappingJson)Expands graph with employee nodesClientIp
Enrich_Graph_Username_Employee(T, mappingJson)Expands graph with employee nodesUsername
Enrich_Graph_Event_Authentication_Username(T, mappingJson)Expands with auth nodesUsername

Mapping JSON Schema

The JSON mapping has two arrays: node_types and edges.

node_types[]
FieldRequiredDescription
typeYesNode type label (e.g. "User", "Host", "IP")
idYesPrefix for node ID; usually same as type
keyYesColumn name whose value becomes the node's identity
propsYesArray of columns to carry as node properties
defaultsNoObject of fallback values for null/empty properties
defIconNoDefault icon URL for this node type
displayNameNoColumn to use for display label (defaults to id)
colorNoColumn to source color from
sizeNoColumn to source size from
edges[]
FieldRequiredDescription
typeYesEdge type label (e.g. "AuthenticatesTo", "SentEmail")
sourceYes{"id": "<prefix>", "type": "<NodeType>"}
targetYes{"id": "<prefix>", "type": "<NodeType>"}
propsNoArray of columns to carry as edge properties
displayNameNoColumn for edge label
colorNoColumn for edge color
Show full SKILL.md (576 more words)Show less
Icon Repository

Use icons from https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/:

  • IP: Public-IP-Addresses-(Classic).svg
  • Host/VM: Virtual-Machine.svg
  • User: Users.svg
  • Email: Mailbox.svg (or azure-cds/command-1070-Mail.svg)
  • Process: App-Services.svg
  • File: Storage-Accounts.svg
  • Alert: Activity-Log.svg
  • Domain: DNS-Zones.svg

Mapping Generation Rules

Given the supplied query columns and the user's graph description, generate the mapping JSON by:

  1. Identify entities -> each distinct noun becomes a node_type
  2. Identify relationships -> each verb/preposition becomes an edge
  3. Map to columns -> use actual columns produced by the supplied query; never assume unavailable columns
  4. Set direction -> source is the actor, target is the acted-upon
  5. Add properties -> include columns relevant to investigation (timestamps, results, hashes)
  6. Assign icons -> pick from the icon set above based on entity type
Column Reference (IRQL unified schema)
EntityKey ColumnAvailable Props
UserUsernameUsername, Name, Role, Email
HostHostnameHostname
IPClientIpClientIp
Email MessageSubjectEnvTime, Subject, Verdict, Url
SenderEmailSenderEmailSender, Domain
RecipientEmailRecipientEmailRecipient
ProcessProcessNameEnvTime, ProcessName, ProcessCommandLine, ProcessHash
FileFilenameEnvTime, Filename, Path, Sha256
DomainDomainNameDomainName
Auth Event(synthetic ID)EnvTime, UserAgent, Result, Description

Function Selection

  1. Start with the supplied KQL/IRQL tabular pipeline.
  2. Use Lift_To_Graph(mapping) to create graph entities.
  3. Add Extract_Node_*, Enrich_Node_*, or Enrich_Graph_* only when requested and compatible with the mapped keys.
  4. Add Graph_Fold_By_Property() only when grouping/collapse is requested.
  5. End visual output with Graph_Render_View().
  6. Preflight the exact stored functions selected for the pipeline.

Pipeline Pattern

kql
// 1. Preserve the supplied KQL or IRQL query
<input query>
// 2. Lift to graph
| invoke Lift_To_Graph(<mapping_json>)
// 3. Optionally extract or enrich graph entities
| invoke <Extract_Node_* | Enrich_Node_* | Enrich_Graph_*>()
// 4. Optionally fold nodes when requested
| invoke Graph_Fold_By_Property("<NodeType>", "<PropertyName>")
// 5. Render
| invoke Graph_Render_View()

Examples

For additional prompts and worked examples, see references/EXAMPLES.md.

Authentication graph: IP -> AuthEvent -> User -> Host

Input query: Get_Event_Authentication_All | where Result == "Failed Login" | take 200

Graph request: "Show IPs, authentication events, users, and hosts; fold events by result."

kql
let auth_mapping = '{"node_types":[{"type":"SrcIp","id":"SrcIp","key":"ClientIp","props":["ClientIp"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Public-IP-Addresses-(Classic).svg"},{"type":"Host","id":"Host","key":"Hostname","props":["Hostname"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Virtual-Machine.svg"},{"type":"User","id":"User","key":"Username","props":["Username"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Users.svg"},{"type":"AuthEvent","id":"AuthEvent","key":"AuthEventId","props":["AuthEventId","EnvTime","UserAgent","Result","Description"],"defaults":{"Result":"unknown"},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Activity-Log.svg"}],"edges":[{"type":"RequestsAuth","source":{"id":"SrcIp","type":"SrcIp"},"target":{"id":"AuthEvent","type":"AuthEvent"},"props":["EnvTime"]},{"type":"TargetsUser","source":{"id":"AuthEvent","type":"AuthEvent"},"target":{"id":"User","type":"User"},"props":["EnvTime"]},{"type":"AgainstHost","source":{"id":"AuthEvent","type":"AuthEvent"},"target":{"id":"Host","type":"Host"},"props":["EnvTime"]}]}';
Get_Event_Authentication_All
| extend AuthEventId = strcat(Username, "_", Hostname, "_", EnvTime)
| where Result == "Failed Login"
| take 200
| invoke Lift_To_Graph(auth_mapping)
| invoke Graph_Fold_By_Property("AuthEvent", "Result")
| invoke Graph_Render_View()
Email graph: Sender -> Message -> Recipient

Input query: Get_Email_All | take 400

Graph request: "Visualize sender-to-message-to-recipient flow and fold messages by verdict."

kql
let mail_mapping = '{"node_types":[{"type":"EmailMessage","id":"Message","key":"Subject","props":["EnvTime","Subject","Verdict"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Media-File.svg"},{"type":"Sender","id":"Email","key":"EmailSender","props":["EmailSender"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-cds/command-1070-Mail.svg"},{"type":"Recipient","id":"Email","key":"EmailRecipient","props":["EmailRecipient"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-cds/command-1070-Mail.svg"}],"edges":[{"type":"SentBy","source":{"id":"Message","type":"EmailMessage"},"target":{"id":"Email","type":"Sender"},"props":["EnvTime","Verdict"]},{"type":"DeliveredTo","source":{"id":"Message","type":"EmailMessage"},"target":{"id":"Email","type":"Recipient"},"props":["EnvTime","Verdict"]}]}';
Get_Email_All
| take 400
| invoke Lift_To_Graph(mail_mapping)
| invoke Graph_Fold_By_Property("EmailMessage", "Verdict")
| invoke Graph_Render_View()
Suspicious domain investigation (end-to-end)

Basic source request: "Use outbound network events for these suspicious domains and graph IP-to-domain connections enriched with employee names."

This is the limited fallback: one known selector, one extractor, and one direct filter.

kql
let suspicious_domain_mapping = '{"node_types":[{"type":"IP","id":"IP","key":"ClientIp","props":["ClientIp"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Public-IP-Addresses-(Classic).svg"},{"type":"Domain","id":"Domain","key":"DomainName","props":["DomainName"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/DNS-Zones.svg"}],"edges":[{"type":"ConnectsTo","source":{"id":"IP","type":"IP"},"target":{"id":"Domain","type":"Domain"},"props":["EnvTime"]}]}';
Get_Event_NetworkOutbound
| invoke Extract_Event_Network_Domain()
| where DomainName has_any ("raisinkanes.com", "nothing-to-see-here.net", "totally-legit-domain.com")
| invoke Lift_To_Graph(suspicious_domain_mapping)
| invoke Enrich_Node_Ip_Employee("Name")
| invoke Graph_Fold_By_Property("Domain", "DomainName")
| invoke Graph_Render_View()
Process execution graph: User -> Process -> ParentProcess

Input query: Get_Event_Process_All | where ProcessCommandLine has "powershell" | take 300

Graph request: "Visualize process, parent process, host, and user relationships."

kql
let proc_mapping = '{"node_types":[{"type":"Process","id":"Proc","key":"ProcessName","props":["ProcessName","ProcessCommandLine","ProcessHash"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/App-Services.svg"},{"type":"ParentProcess","id":"Proc","key":"ParentProcessName","props":["ParentProcessName","ParentProcessHash"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/App-Services.svg"},{"type":"Host","id":"Host","key":"Hostname","props":["Hostname"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Virtual-Machine.svg"},{"type":"User","id":"User","key":"Username","props":["Username"],"defaults":{},"defIcon":"https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/Users.svg"}],"edges":[{"type":"SpawnedBy","source":{"id":"Proc","type":"Process"},"target":{"id":"Proc","type":"ParentProcess"},"props":["EnvTime"]},{"type":"RanOn","source":{"id":"Proc","type":"Process"},"target":{"id":"Host","type":"Host"},"props":["EnvTime"]},{"type":"ExecutedBy","source":{"id":"Proc","type":"Process"},"target":{"id":"User","type":"User"},"props":["EnvTime"]}]}';
Get_Event_Process_All
| where ProcessCommandLine has "powershell"
| take 300
| invoke Lift_To_Graph(proc_mapping)
| invoke Graph_Render_View()

Query Results -> Mapping Translation

When the user supplies a query and describes the graph:

  1. Inspect the query's final output columns
  2. Parse the entity nouns and relationship verbs
  3. Generate the mapping JSON using only those columns
  4. Preserve the supplied pipeline and append Lift_To_Graph()
  5. Include Graph_Render_View() at the end
  6. If the user mentions grouping/collapsing and the function exists, add Graph_Fold_By_Property()

Output the complete KQL -- the supplied query plus mapping JSON inline as a string let binding -- after the required-function preflight passes. Clearly mark unverified function dependencies when the target database cannot be checked.

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_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

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in plugins/azure-kusto-graph-skills/skills/azure-kusto-irql-graph of microsoft/GitHub-Copilot-for-Azure.

  • SKILL.md
  • references/DEPLOY_IRQL_FUNCTIONS.md
  • references/EXAMPLES.md
  • references/KUSTO_EXPLORER_LAUNCH.md
  • version.json

Open the folder on GitHubat commit ce94fce

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in microsoft/GitHub-Copilot-for-Azure, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Azure Kusto Irql Graph next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Azure Kusto Irql Graph compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azure Kusto Irql Graph this skillmicrosoft/GitHub-Copilot-for-Azure255—~4.8kAutomated safety check: PassMIT
Kql ValidatorAzure/azqr795—~703Automated safety check: PassMIT
Kqlmicrosoft/fabric-rti-mcp131—~6.2kAutomated safety check: PassMIT
Apex Azure Diagnosticsjonathan-vella/apex217—~2.1kAutomated safety check: PassMIT
Fleet Intelligencemicrosoft/physical-ai-toolchain123—~598Automated safety check: PassMIT
Deploying Cloud Deception With Decoy Resourcesmukul975/Anthropic-Cybersecurity-Skills34k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Kql Validator

    Azure/azqr

    Official

    Validate KQL (Kusto Query Language) files used in Azure Quick Review (azqr) against their recommendation definitions.

    795 GitHub stars~703 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Kql

    microsoft/fabric-rti-mcp

    Official

    KQL language expertise for writing correct, efficient Kusto queries using the Fabric RTI MCP tools.

    131 GitHub stars~6.2k tokensUpdated 8 days ago
    Data & AnalyticsAuto-check passed
  • Apex Azure Diagnostics

    jonathan-vella/apex

    WORKFLOW SKILL — Debug Azure production issues: Container Apps, Functions, App Service, AKS, VMs and messaging, with KQL log analysis.

    217 GitHub stars~2.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Fleet Intelligence

    microsoft/physical-ai-toolchain

    Official

    Monitor robot fleet telemetry via Azure IoT Operations, drift detection, Grafana dashboards, and Fabric analytics

    123 GitHub stars~598 tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Deploying Cloud Deception With Decoy Resources

    mukul975/Anthropic-Cybersecurity-Skills

    Deploy cloud-native deception across AWS, Azure, and GCP using decoy (honey) resources whose only purpose is to generate a high-fidelity alert the instant an attacker touches them: canary IAM access…

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Detecting Azure Service Principal Abuse

    mukul975/Anthropic-Cybersecurity-Skills

    Detect Azure service principal abuse in Microsoft Entra ID using KQL detection queries (Sentinel/Splunk) against Azure AD Audit and Sign-in Logs, covering added credentials, privileged role…

    34k GitHub stars~2.1k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from microsoft/GitHub-Copilot-for-Azure

All 61 skills in this repo
  • Capacity

    microsoft/GitHub-Copilot-for-Azure

    Official

    Discovers available Azure OpenAI model capacity across regions and projects.

    255 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Deploy Model

    microsoft/GitHub-Copilot-for-Azure

    Official

    Unified Azure OpenAI model deployment skill with intelligent intent-based routing.

    255 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Azure Storage

    microsoft/GitHub-Copilot-for-Azure

    Official

    Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake.

    255 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Microsoft Foundry

    microsoft/GitHub-Copilot-for-Azure

    Official

    Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end.

    255 GitHub starsUsed in 1 repo~6.7k tokens
    Auto-check passed
  • Entra Agent Id

    microsoft/GitHub-Copilot-for-Azure

    Official

    Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant)…

    255 GitHub starsUsed in 2 repos~4k tokens
    Auto-check passed
  • Azure Kubernetes Automatic Readiness

    microsoft/GitHub-Copilot-for-Azure

    Official

    Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility.

    255 GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed

Questions about Azure Kusto Irql Graph

What does Azure Kusto Irql Graph do?

Apply IRQL graph functions to KQL or IRQL query results for Kusto Explorer visualization. Azure Kusto Irql Graph is an agent skill from microsoft/GitHub-Copilot-for-Azure, published by the product's own GitHub organization. Apply IRQL graph functions to KQL or IRQL query results for Kusto Explorer visualization.

How do I install Azure Kusto Irql Graph in Claude Code?

Run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql-graph -a claude-code`. Or copy the skill folder (plugins/azure-kusto-graph-skills/skills/azure-kusto-irql-graph in microsoft/GitHub-Copilot-for-Azure) into .claude/skills/azure-kusto-irql-graph in your project. Claude Code loads it when a task matches its description.

How do I install Azure Kusto Irql Graph in Codex?

Run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql-graph -a codex`. Or copy the skill folder (plugins/azure-kusto-graph-skills/skills/azure-kusto-irql-graph in microsoft/GitHub-Copilot-for-Azure) into .agents/skills/azure-kusto-irql-graph in your project. Codex loads it when a task matches its description.

Can I use Azure Kusto Irql Graph in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/GitHub-Copilot-for-Azure --skill azure-kusto-irql-graph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-kusto-irql-graph, .gemini/skills/azure-kusto-irql-graph, .github/skills/azure-kusto-irql-graph and .opencode/skills/azure-kusto-irql-graph in your project.

What does Azure Kusto Irql Graph need to run?

SKILL.md names no scripts, command-line tools or credentials: Azure Kusto Irql Graph is instructions for the agent only.

Does Azure Kusto Irql Graph access the network?

SKILL.md names 2 domains. In commands or code: raw.githubusercontent.com and kc7001.eastus.kusto.windows.net; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Azure Kusto Irql Graph safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Azure Kusto Irql Graph use?

Azure Kusto Irql Graph is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Azure Kusto Irql Graph use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.

What are the alternatives to Azure Kusto Irql Graph?

Skills that share tags, products or a category with Azure Kusto Irql Graph: Kql Validator (Azure/azqr, 795 stars), Kql (microsoft/fabric-rti-mcp, 131 stars), Apex Azure Diagnostics (jonathan-vella/apex, 217 stars) and Fleet Intelligence (microsoft/physical-ai-toolchain, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azure Kusto Irql Graph?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/GitHub-Copilot-for-Azure, which has 255 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 9, 2026.

Source: microsoft/GitHub-Copilot-for-Azure on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.