CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-monitor-query-java

Azure Monitor Query SDK for Java. Execute Kusto queries against Log Analytics workspaces and query metrics from Azure resources.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-monitor-query-java/SKILL.md

The canonical home for this skill is azure-monitor-query-java in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is highly actionable with complete executable examples and decent workflow validation, but it is a monolithic single-file reference rather than a lean overview pointing to detail files, which limits progressive disclosure.

Suggestions

Split the detailed API examples (batch queries, metrics aggregations, migration notes) into reference files under references/ and link to them from a leaner SKILL.md overview.

Replace the vague 'When to Use' filler with concrete trigger conditions or remove it entirely.

Add an explicit validate->fix->retry feedback loop for batch operations to push workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

The body is code-forward and assumes competence, with minimal over-explanation; only minor padding remains, such as the vague 'When to Use' line ('applicable to execute the workflow or actions described in the overview') and the basic Key Concepts table.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Java with real imports and method calls (queryWorkspace, queryResource, queryBatchWithResponse, queryResourceWithResponse) covering the common logs and metrics cases.

5 / 5

Workflow Clarity

Content is clearly organized by operation with status-check validation for batch queries (FAILURE) and error handling (PARTIAL_FAILURE), satisfying the batch-operation validation expectation; it falls short of a 5 only because there is no explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

All ~280 lines of detailed API reference, migration notes, and examples are inlined in a single SKILL.md with no bundle files and no split into reference files; structure is decent but content that the rubric expects to live in separate detail files is inline.

3 / 5

Total

16

/

20

Passed

Description

65%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 specific and well-targeted to a clear niche, but it omits any 'Use when' trigger guidance, which caps its completeness. Adding an explicit usage clause would lift the weakest dimension.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when querying Azure Log Analytics workspaces with Kusto (KQL) or retrieving metrics from Azure resources in Java.'

Mention one or two more concrete capabilities (e.g. batch queries, metric aggregations) to broaden specificity beyond the two core actions.

Add common synonyms users might say such as 'KQL' and 'Azure logs' to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions — 'Execute Kusto queries against Log Analytics workspaces' and 'query metrics from Azure resources' — but stops at two actions without covering other capabilities (batch queries, aggregations), matching the 1-2-action anchor rather than the broader several-action anchor.

3 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at the 'clear what, missing when' anchor.

3 / 5

Trigger Term Quality

Strong natural keyword coverage — 'Azure Monitor', 'Kusto queries', 'Log Analytics workspaces', 'metrics', 'Azure resources' — which are exactly the terms a user would say when needing this skill; a few minor synonyms/variants are absent.

4 / 5

Distinctiveness Conflict Risk

The Azure Monitor Query / Kusto / Log Analytics niche is highly specific with distinct triggers, giving minimal overlap risk with unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.