CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-kql-queries

[Skill] kql, queries, log analytics, container logs - KQL query templates for Koji container logs, pod errors, restarts, Kubernetes events, build job activity, and node resource usage via Log Analytics.

67

Quality

80%

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 ./.github/skills/skill-kql-queries/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 SKILL.md body is a tight, fully executable KQL query reference: concrete queries, a clear tools table, and consistent namespace-filter guidance, with no verbosity and an explicit fallback note. It is a model concise action-oriented skill body.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a tools table, namespace-filter rules, and ready-to-run KQL blocks with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Every section is a fully executable, copy-paste-ready KQL query with concrete table names, filters, and projections, matching the 'fully executable code, specific examples' anchor.

3 / 3

Workflow Clarity

This is a simple single-purpose query-reference skill with unambiguous, well-organized queries; the KubeEvents note even provides an explicit fallback, satisfying the simple-skill allowance for a 3.

3 / 3

Progressive Disclosure

The content is short and well-organized into clearly labeled sections by query purpose, with no external bundle files or nested references needed, meeting the under-50-line simple-skill allowance for a 3.

3 / 3

Total

12

/

12

Passed

Description

60%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 conveys a strong, specific set of capabilities for a Koji/Kubernetes log query skill, but it lacks an explicit 'Use when...' trigger clause and uses an unnatural '[Skill]' tag prefix instead of third-person prose, which limits completeness and distinctiveness.

Suggestions

Replace the '[Skill] kql, queries, ...' tag-list prefix with a third-person sentence and add a 'Use when the user needs to query Koji/Kubernetes container logs, pod errors, restarts, or node resource usage via Log Analytics' trigger clause to raise completeness to 3.

Drop the '[Skill]' metadata prefix from the description text and keep natural trigger terms a user would actually say (e.g., 'KQL queries', 'container logs', 'pod restarts', 'Log Analytics').

Lead with the concrete action and the tool ('Run KQL queries against Azure Log Analytics to inspect Koji pod logs...') so the description reads as distinct from generic query skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('KQL query templates for Koji container logs, pod errors, restarts, Kubernetes events, build job activity, and node resource usage'), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does, but has no 'Use when...' clause or equivalent explicit trigger guidance, which per guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms like 'kql, queries, log analytics, container logs', but coverage of common variations is partial and the leading '[Skill]' tag-list prefix is unnatural phrasing a user would not say.

2 / 3

Distinctiveness Conflict Risk

The Koji + Log Analytics niche is reasonably specific, but the '[Skill] kql, queries...' tag-list style weakens the distinct-trigger framing, leaving it somewhat generic among query skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/azurelinux
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.