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.

59

Quality

68%

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

72%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 Java examples and efficient prose, but it functions as a monolithic reference catalog without progressive disclosure to bundle files and lacks explicit validation feedback loops for batch operations.

Suggestions

Move the migration notes, best practices, and detailed API examples into separate reference files (e.g., references/migration.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit validate/fix/retry loop around batch and metrics queries (check result status, surface errors, retry or adjust) to raise workflow clarity above the batch-operation cap of 3.

Remove the generic 'When to Use' sentence and replace it with concrete trigger guidance or delete it entirely to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is dominated by executable code with little explanation of basic concepts, but the 'Key Concepts' table and the fluff 'When to Use' sentence ('This skill is applicable to execute the workflow or actions described in the overview.') are minor padding that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Java snippets with imports for client creation, logs queries, batch queries, metrics queries, and error handling, covering the common cases.

5 / 5

Workflow Clarity

Operations are organized by type rather than as a sequenced workflow, and while batch queries include failure-status checks, there is no explicit validate/fix/retry feedback loop for batch operations, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Section headers give decent structure, but all detail (installation, migration notes, best practices, full API usage) is inlined in one ~280-line file with no bundle files and only external URL references, so content that could be split out remains inline.

3 / 5

Total

15

/

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 distinctive, clearly conveying what the SDK does, but it omits an explicit 'when to use it' trigger clause, which limits its completeness score.

Suggestions

Append a 'Use when ...' clause naming concrete trigger situations (e.g., querying Log Analytics workspaces, fetching Azure resource metrics) to raise completeness.

Add a few more natural synonyms (e.g., 'Azure Monitor logs', 'KQL', 'resource metrics') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure Monitor Query SDK for Java') and two concrete actions ('Execute Kusto queries against Log Analytics workspaces' and 'query metrics from Azure resources'), but coverage is not comprehensive beyond those two operations.

3 / 5

Completeness

Provides a clear 'what' but no explicit 'when to use it' clause in the description; per the judging guidelines a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural domain terms a user would say ('Azure Monitor Query', 'Kusto queries', 'Log Analytics', 'metrics'), with only a few common variants missing, so it sits above the midpoint but not at full synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Targets a specific niche (Azure Monitor Query SDK for Java, Kusto/Log Analytics/metrics) with distinct triggers and 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.