SKILLEMALL.ai
GitHub ↗ RU Sign in

AA azure-monitor-query-java

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

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 3 249 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Azure Monitor Query SDK for Java.

As a process A 82/100 · Runs to the end — weak spots: when it triggers

IntegrationAzureGitHubData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
A
82/100
Runs to the end
When it triggers w 12
20
Failures and branches w 10
50
Inputs and preconditions w 11
70
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note edit-residue the text marks something as outdated (lines 4): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 82/100

    • 20When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 13 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3249 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress
    • low 13 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +3Description length 128: enough signal without eating the budget
    • +4Structure: 30 headings
    • +3Step-by-step instructions: 13 items
    • +3Output format is stated explicitly
    • +4Has examples (20 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.