Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoft/azure-kusto-graph
Build and query Kusto graphs from natural language. Covers transient graphs (make-graph), persistent graph models/snapshots, pattern matching (graph-match), shortest paths, connected components, and graph-to-table export. Generates the edges-first thinking: define edges, define node lookups, union, make-graph. WHEN: make-graph, graph-match, graph-shortest-paths, graph-to-table, graph-mark-components, persistent graph, graph model, graph snapshot, build a graph from data, find paths between nodes
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 18 more in the full report
13 fixed8 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a KQL control command to delete an obsolete snapshot named 'Snapshot_2024' from the 'SecurityGraph' model in Azure Data Explorer. What command is used and what safety step should be taken?
| Checked | Without skill | With skill |
|---|---|---|
| Uses .drop graph_snapshot SecurityGraph Snapshot_2024. | Missed | Passed |
| Requests explicit user confirmation before executing the snapshot deletion. | Missed | Passed |
The instructions your model reads when the skill loads.
Build transient and persistent graphs from tabular data using KQL graph operators. This skill translates natural language into the edges-first graph construction pattern and graph query operators.
Use this skill when the user:
make-graph)graph-match, graph-shortest-paths, graph-to-table, graph-mark-componentsNot a natural-language-to-KQL converter. The input should generally be a working KQL query whose results the user wants converted to a graph, plus a natural-language description of the desired graph structure. Basic NL source requests are supported only when they map directly to a known table with obvious columns. For general NL-to-KQL conversion, use a dedicated query-generation skill (available separately).
Complementary skills:
azure-kusto-irql -- composable security query primitives that produce the tabular inputs for graphsazure-kusto-irql-graph -- IRQL's Lift_To_Graph JSON mapping system for richly-typed, icon-decorated graphs in Kusto ExplorerThe fundamental pattern for building graphs in Kusto:
1. Define your EDGES -> src --> dest, with relationship type/properties
2. Define your NODE LOOKUPS -> display names, types, properties for each node ID
3. Union edge types -> if you have multiple relationship types
4. Union node lookups -> if you have multiple node types
5. Call make-graph -> edges | make-graph Source --> Target with nodes on nodeId
This is how to think in make-graph. Edges are the relationships you care about. Nodes are lookup tables that give those IDs a face -- display names, types, properties.
make-graph -- Build a graph from tablesEdges | make-graph SourceId --> TargetId with Nodes on NodeId
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.