azure-kusto

Query and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clusters, log analytics, time series data, IoT telemetry, anomaly detection.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/plugins/azure-skills/skills/azure-kusto/SKILL.md

Quality

Content

65%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 highly actionable with concrete KQL and CLI examples and good structural organization, but suffers from redundant best-practice sections and lacks validation checkpoints in its workflow and external reference files for its length.

Suggestions

Consolidate the overlapping 'KQL Best Practices' and 'Best Practices' sections into a single deduplicated list to improve conciseness.

Add explicit validation checkpoints to the Core Workflow (e.g., verify schema exists before querying, confirm non-empty results before analyzing) to support a feedback loop for query operations.

Move the detailed CLI fallback reference and/or KQL function catalog into a separate reference file (e.g., references/cli-fallback.md) referenced from SKILL.md to improve progressive disclosure for a 230-line skill.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with section headers, tables, and code blocks, but contains redundancy (the 'KQL Best Practices' and 'Best Practices' sections overlap heavily) and minor over-explanation of what ADX is; it could be tightened, fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides five complete, executable KQL examples plus real Azure CLI fallback commands and explicit tool/parameter tables, covering common cases copy-paste ready, matching the top anchor.	5 / 5
Workflow Clarity	A four-step Core Workflow is present but the steps are abstract ('Discover Resources', 'Explore Schema') with no explicit validation checkpoints; database/query operations warrant feedback loops per the rubric, so this fits the 'steps listed but checkpoints missing' anchor and is capped at 3.	3 / 5
Progressive Disclosure	The file is well-sectioned but all content lives in a single ~230-line SKILL.md with no bundle files or external references, and material like the full CLI reference and best-practice lists is inlined rather than split out, fitting the 'some structure, content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

95%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 strong: it concisely states both capability and explicit activation triggers with comprehensive, natural-language synonyms for the Kusto/ADX domain. The only minor gap is a slightly limited count of distinct concrete actions versus the most comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several specific capability areas ('log analytics, telemetry, and time series analysis', anomaly detection), but the actions themselves ('Query and analyze') are limited in number rather than fully comprehensive, fitting the 'several specific actions; minor gaps' anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('Query and analyze data in Azure Data Explorer using KQL') and 'when' via a 'WHEN:' clause with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms users would say, including synonyms and acronyms ('KQL', 'Kusto', 'Azure Data Explorer', 'ADX', 'log analytics', 'time series data', 'IoT telemetry'), matching the 'comprehensive coverage including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Kusto/ADX/KQL) with distinct, domain-specific triggers that are unlikely to fire for unrelated skills, giving minimal 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/azure-skills
Path: .github/plugins/azure-skills/skills/azure-kusto/SKILL.md
Commit: 16dc8c5

Reviewed: about 12 hours 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.