Query and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetry, and time series analysis. USE FOR: KQL queries, Kusto database queries, Azure Data Explorer, ADX clusters, log analytics, time series data, IoT telemetry, anomaly detection DO NOT USE FOR: SQL databases, NoSQL queries (use azure-storage), Elasticsearch, AWS analytics tools
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-kusto88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 1.07xAgent success when using this skill
Validation for skill structure
KQL time series and aggregation best practices
Time range filter with ago()
100%
100%
bin() for time bucketing
100%
100%
summarize for aggregation
100%
100%
percentiles() for latency
100%
100%
where before summarize
100%
100%
project to select columns
100%
100%
render timechart
0%
100%
take or limit for exploratory query
100%
87%
extend for calculated fields
100%
100%
No bare count() aggregation
100%
100%
Multiple .kql output files
100%
100%
Without context: $0.3961 · 1m 15s · 22 turns · 29 in / 5,007 out tokens
With context: $0.4855 · 1m 30s · 25 turns · 187 in / 5,629 out tokens
Cross-table correlation and join queries
join keyword used
100%
100%
join kind specified
100%
100%
join on CorrelationId or SessionId
100%
30%
where before join
100%
100%
project to limit columns
100%
100%
Time range filter
100%
100%
between() for bounded time range
0%
100%
String filtering function
100%
100%
parse or extract used
100%
100%
Multiple output .kql files
100%
100%
summarize for aggregation
100%
100%
No .kusto.windows.net in cluster name
100%
100%
Without context: $0.3015 · 1m 23s · 16 turns · 21 in / 5,124 out tokens
With context: $0.5789 · 2m 4s · 28 turns · 317 in / 7,646 out tokens
Azure CLI fallback for ADX operations
az kusto cluster list used
100%
100%
az kusto database list used
100%
100%
az rest --method post used
100%
100%
Correct REST endpoint URL pattern
100%
100%
Correct body structure
100%
100%
Cluster name without suffix
100%
100%
Timeout fallback trigger
50%
100%
Service unavailable fallback trigger
66%
100%
Auth failure fallback trigger
83%
100%
Empty response fallback trigger
0%
100%
subscription parameter present
100%
100%
resource-group parameter present
100%
100%
Without context: $0.3435 · 1m 41s · 16 turns · 21 in / 6,288 out tokens
With context: $0.4567 · 1m 45s · 20 turns · 25 in / 6,441 out tokens
Table of Contents
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.