azure-kusto-irql-graph

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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

A highly actionable, well-sequenced skill body with executable examples and proper validation feedback loops for database deployment. The main improvements are token efficiency (repeated caveats and icon URLs) and pushing more worked-example detail into EXAMPLES.md.

Suggestions

State the 'not an NL-to-KQL/IRQL converter' caveat once in the Input Contract and reference it from other sections instead of repeating it three times.

Define the icon URL prefix once and reference icons by filename in example mappings, rather than re-inlining the full GitHub raw URL in every node_type.

Move two of the four fully-worked inline examples into references/EXAMPLES.md, keeping one or two representative pipelines in the body to reduce redundancy with that file.

Dimension	Reasoning	Score
Conciseness	The body is dense domain reference that largely assumes Claude's competence, but the NL-to-KQL caveat is repeated three times and full icon URLs are re-inlined in every example mapping, adding tokens that could be trimmed.	4 / 5
Actionability	Provides complete, copy-paste-ready KQL pipelines with full inline mapping JSON across four worked scenarios plus a preflight query and a concrete pipeline pattern, covering the common cases.	5 / 5
Workflow Clarity	Sequences are clearly numbered (Function Selection, Pipeline Pattern, Translation) with an explicit preflight validate→deploy→rerun-check feedback loop and an ask-user confirmation gate before database alteration, satisfying validation for the database operations.	5 / 5
Progressive Disclosure	References to DEPLOY_IRQL_FUNCTIONS.md, EXAMPLES.md, and KUSTO_EXPLORER_LAUNCH.md are well-signaled and one level deep, but the body still carries the full mapping schema, column reference, and four complete inline examples, with mild redundancy against EXAMPLES.md.	4 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong, specific description that clearly states what the skill does and when to use it, with concrete trigger terms and explicit disambiguation from the related azure-kusto-graph skill. Minor room to add a few more natural synonyms in the trigger clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generates Lift_To_Graph mappings and composes Graph_Render_View, Graph_Fold_By_Property, Extract_Node_, Enrich_Node_, and Enrich_Graph_* calls' — giving comprehensive coverage of the skill's capabilities within its niche.	5 / 5
Completeness	Explicitly answers both 'what' (apply IRQL graph functions to query results, generate mappings, compose calls) and 'when' via a concrete 'WHEN:' trigger clause, matching the top anchor.	5 / 5
Trigger Term Quality	The 'WHEN:' clause covers strong natural terms ('IRQL graph enrichment', 'graph mapping for existing query results', 'icon-decorated graph', 'fold graph nodes') plus function names, but a few common synonyms like 'graph visualization' or 'KQL graph' are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche with active routing away from the sibling skill ('Use azure-kusto-graph for native make-graph analysis, graph-match, shortest paths…') and an explicit disclaimer that it is not an NL-to-KQL/IRQL converter, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/GitHub-Copilot-for-Azure
Path: plugins/azure-kusto-graph-skills/skills/azure-kusto-irql-graph/SKILL.md
Commit: a55fe6d

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.