CtrlK
BlogDocsLog inGet started
Tessl Logo

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, pattern matching in graph, connected components, transient graph, Kusto graph, KQL graph.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is azure-kusto-graph in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable KQL and clearly sequenced, safety-conscious workflows, but it over-inlines repeated worked examples that duplicate the referenced example files, hurting token efficiency and the overview-to-reference split.

Suggestions

Move the full security threat-hunting examples (auth graph, lateral movement, shortest attack path, connected components) into references/EXAMPLES.md or SCENARIOS.md, keeping only one representative pattern plus a pointer in SKILL.md.

Consolidate the repeated 'edges → nodes → make-graph' scaffolding into a single named template and reference it from later examples instead of restating it each time.

Add an explicit validation/feedback-loop step to the persistent-graph workflow (e.g., '.show graph_model SecurityGraph to verify schema after .create-or-alter') to lift workflow clarity toward the top anchor.

DimensionReasoningScore

Conciseness

The body is ~460 lines and mostly domain-specific KQL graph syntax that earns its place, but the edge→node→make-graph pattern is repeated verbatim across several inlined security and IRQL worked examples, which is padding that could be tightened or moved out.

3 / 5

Actionability

Executable copy-paste KQL is provided throughout — operator reference snippets, parameterized templates, and complete worked examples (auth graph, lateral movement, shortest attack path, components) covering the common cases.

5 / 5

Workflow Clarity

A clear edges-first 5-step sequence and a Step 1/2/3 persistent-graph flow are present, with explicit Safety callouts requiring confirmation before destructive commands (.create-or-alter graph_model, .make graph_snapshot, .drop), though explicit error-recovery feedback loops are only implied.

4 / 5

Progressive Disclosure

Real one-level-deep references (EXAMPLES.md, SCENARIOS.md, KUSTO_EXPLORER_LAUNCH.md) are clearly signaled, but a substantial amount of worked security/IRQL example content is inlined in SKILL.md rather than split into those reference files.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong, third-person statement of capabilities with an explicit WHEN trigger clause and comprehensive natural-language keywords. It cleanly answers both what the skill does and when to invoke it, with low conflict risk against sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — build/query graphs, transient (make-graph) and persistent models/snapshots, pattern matching, shortest paths, connected components, graph-to-table export, plus the edges-first construction pattern — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

It explicitly answers 'what' (build and query Kusto graphs from natural language, with the listed capabilities) and 'when' via a concrete WHEN: trigger clause, matching the anchor for clearly answering both.

5 / 5

Trigger Term Quality

The WHEN clause covers natural operator names (make-graph, graph-match, graph-shortest-paths, graph-mark-components) alongside synonyms and plain phrases (build a graph from data, find paths between nodes, Kusto graph, KQL graph) that a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear Kusto/KQL graph niche with operator-specific triggers, and complementary skills are named separately, leaving minimal overlap or wrong-skill conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/azure-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.