azure-kusto
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
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It provides specific capabilities, comprehensive trigger terms covering multiple naming conventions (KQL, Kusto, ADX, Azure Data Explorer), explicit 'USE FOR' and 'DO NOT USE FOR' guidance, and clear differentiation from related but distinct skills. The third-person voice is maintained throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Query and analyze data', 'log analytics', 'telemetry', 'time series analysis', 'anomaly detection'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (query and analyze data in ADX using KQL) and 'when' via explicit 'USE FOR' and 'DO NOT USE FOR' clauses that provide clear trigger guidance and boundaries. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'KQL queries', 'Kusto', 'Azure Data Explorer', 'ADX', 'log analytics', 'time series data', 'IoT telemetry'. Includes both acronyms and full names. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit 'DO NOT USE FOR' clause that differentiates from SQL databases, NoSQL/azure-storage, Elasticsearch, and AWS tools. Clear niche in Azure/Kusto ecosystem. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionable guidance with executable KQL examples and clear tool documentation, but suffers from verbosity in explaining concepts Claude already knows (what ADX is, key indicators for activation). The workflow lacks explicit validation checkpoints for query operations, and the content could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the 'Skill Activation Triggers' and 'Key Indicators' sections - Claude can infer when to use this skill from the description
Remove the Overview paragraph explaining what Azure Data Explorer is - Claude already knows this
Add explicit validation steps to the Core Workflow (e.g., 'Verify query syntax before execution', 'Check result count before processing large datasets')
Move the MCP Tools table and CLI Command Reference to separate reference files and link to them from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., 'Azure Data Explorer provides sub-second query performance on billions of records') and verbose sections like 'Skill Activation Triggers' that Claude doesn't need. The overview section explains what ADX is, which Claude already knows. | 2 / 3 |
Actionability | Provides fully executable KQL examples with clear syntax, concrete tool names with required parameters, and copy-paste ready CLI fallback commands. Each query pattern includes working code examples. | 3 / 3 |
Workflow Clarity | The 'Core Workflow' section lists steps but lacks validation checkpoints. For query operations that could timeout or fail, there's no explicit validate-then-proceed pattern. The fallback strategy is good but the main workflow lacks error recovery loops. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic document with no references to external files for detailed content. The MCP tools table and CLI reference could be split into separate reference files to reduce the main skill's length. | 2 / 3 |
Total | 9 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.