skill-metrics

[Skill] metrics, azure-monitor, aks - Query Azure Monitor metrics for Koji AKS node CPU, memory, disk usage, and pod readiness.

Quality

64%

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/skills/skill-metrics/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized for a simple single-purpose skill, but its actionability and workflow clarity are held back by a missing timespan parameter in the worked example and an implicit rather than explicit discover-then-query sequence.

Suggestions

Add the missing timespan parameter (e.g. `timespan`: `PT24H` or `start-time`/`end-time`) to the example so the query is fully specified and copy-paste ready.

Explicitly sequence the two-step flow as numbered steps (discover available metrics with `monitor_metrics_definitions`, then query with `monitor_metrics_query`).

Note what to do when a metric returns no data (e.g. confirm the resource/namespace spelling or widen the interval) as a light validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean: compact tool and metric tables plus a single parameter example, with no padding or explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Provides concrete tool names, metric names, namespace, aggregation, and interval, but the example says 'over the last 24 hours' without supplying the corresponding timespan parameter, leaving a key detail missing.	2 / 3
Workflow Clarity	A discover-then-query sequence is implied by the two tools and example, but it is not explicitly sequenced as steps and there are no validation checkpoints or guidance for handling empty results.	2 / 3
Progressive Disclosure	The skill is under 50 lines, self-contained with no external references needed, and well-organized into clear sections (Tools, Key metric namespaces, Common query patterns).	3 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 occupies a clearly distinct niche, but it omits an explicit 'Use when...' trigger and leans on a jargon-flavored tag prefix rather than natural trigger phrasing, leaving completeness and trigger-term quality at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when checking Koji AKS node health, troubleshooting CPU/memory/disk pressure, or verifying pod readiness.'

Replace the '[Skill] metrics, azure-monitor, aks -' tag prefix with a natural third-person lead-in so the opening reads as a sentence a user would say.

Expand beyond the single 'Query' verb to name distinct actions (e.g. discover, query, compare) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('Query Azure Monitor metrics') and specific targets ('Koji AKS node CPU, memory, disk usage, and pod readiness'), but lists only a single query action rather than multiple distinct actions.	2 / 3
Completeness	Clearly states what the skill does ('Query Azure Monitor metrics for ...'), but lacks any 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains relevant natural keywords (metrics, CPU, memory, disk usage, pod readiness), but the leading '[Skill] metrics, azure-monitor, aks -' tag block reads as jargon-flavored tagging rather than natural trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	The 'Koji AKS' / 'Azure Monitor metrics' niche is narrow and specific enough that it is unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 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/azurelinux
Path: .github/skills/skill-metrics/SKILL.md
Commit: 9e308ff

Reviewed: 6 days 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.