CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

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-irql-graph in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is well-structured, actionable, and properly progressive-disclosed with real reference files and a validation checkpoint for the deploy step. Minor redundancy in the NL-converter disclaimers and a slightly loose integration of the deploy feedback loop keep it just short of top marks on conciseness and workflow clarity.

Suggestions

Consolidate the repeated 'not a natural-language-to-KQL/IRQL converter' disclaimer into a single statement (Input Contract or Activation Triggers) to remove redundant tokens.

Tighten the deploy feedback loop by folding the preflight re-check explicitly into the Function Selection / Translation numbered workflow as a final validation step rather than only describing it in the Environment section.

DimensionReasoningScore

Conciseness

Content is mostly efficient and assumes competence, but the 'not a natural-language-to-KQL/IRQL converter' disclaimer is repeated across Input Contract (line 28) and Activation Triggers (line 45), adding redundant tokens.

4 / 5

Actionability

Provides copy-paste-ready executable KQL: the `.show functions` preflight query, the pipeline pattern template, and four fully worked examples with inline mapping JSON covering common cases.

5 / 5

Workflow Clarity

Sequenced steps (Function Selection 1-6, Translation 1-6) with a validation checkpoint in Function Preflight (check deployed, ask confirmation before deploying, rerun preflight) are present, but the deploy feedback loop is referenced rather than tightly integrated into the main generation workflow.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with one-level-deep, well-signaled references to the real files references/EXAMPLES.md, references/DEPLOY_IRQL_FUNCTIONS.md, and references/KUSTO_EXPLORER_LAUNCH.md, with content appropriately split.

5 / 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.

The description is concrete, comprehensive, and well-routed, clearly stating what the skill does and when to use it while distinguishing it from adjacent graph and query-generation skills. Trigger terms are strong but slightly function-name-centric rather than covering natural-language synonyms.

DimensionReasoningScore

Specificity

Names 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 function family.

5 / 5

Completeness

Explicitly answers both 'what' (apply IRQL graph functions, generate mappings, compose calls) and 'when' via a concrete WHEN: clause with trigger phrases.

5 / 5

Trigger Term Quality

Lists relevant triggers ('Lift_To_Graph', 'Graph_Render_View', 'icon-decorated graph', 'fold graph nodes', 'graph mapping') but coverage leans on function names rather than a fuller set of synonyms or file extensions a user might say.

4 / 5

Distinctiveness Conflict Risk

Explicitly routes away from azure-kusto-graph ('native make-graph analysis, graph-match, shortest paths, components, or persistent graphs') and NL-to-KQL skills, establishing a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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.