skill-deployment-context

[Skill] deployment context, aks, azure, koji - Resolve Koji AKS deployment context -- resource group, cluster name, subscription, Log Analytics workspace, and monitoring resource names from deployment_summary.yaml when available, or discover them dynamically from Azure.

Quality

77%

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-deployment-context/SKILL.md

Quality

Content

87%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 content is concise and actionable with executable Azure commands and a clear branching workflow, but it lacks validation checkpoints for the discovery steps and interleaves a manual-confirmation step awkwardly.

Suggestions

Add an explicit validation step after dynamic discovery (e.g., verify the discovered cluster/subscription against expectations or confirm with the user before proceeding) to add a feedback loop.

Reorder prerequisites (Node.js/npx, az login) to the top so they precede the commands that depend on them.

Clarify Step 3 by stating when to ask versus when to fall through to the dynamic discovery commands in Step 4.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no concept padding; it assumes Claude's knowledge and every line (commands, naming convention, MCP table) earns its place.	3 / 3
Actionability	Provides concrete, copy-paste-ready `az` commands with explicit placeholders and a structured MCP tools table, giving fully executable guidance.	3 / 3
Workflow Clarity	Steps are sequenced with branching (file present vs absent) but there are no validation checkpoints, and Step 3 ("Ask the user") interrupts the dynamic-discovery sequence without an explicit verification loop.	2 / 3
Progressive Disclosure	Under 50 lines with no external bundle files, the skill is cleanly split into well-signaled sections; per the simple-skills note this is sufficient for a top score.	3 / 3
	Total	11 / 12 Passed

Description

67%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 distinctive about resolving Koji AKS deployment context, but it omits an explicit 'Use when...' trigger clause and relies on jargon-heavy terms, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when resolving Koji AKS deployment context, resource groups, or monitoring resource names for a deployment.') to satisfy the trigger-guidance requirement.

Include more natural user phrasing alongside the jargon (e.g., 'AKS cluster', 'Azure subscription', 'Log Analytics') so the trigger terms match what users would actually say.

Drop the leading '[Skill]' tag and the redundant 'deployment context, aks, azure, koji' echo to tighten the description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete resources ("resource group, cluster name, subscription, Log Analytics workspace, and monitoring resource names") and two concrete actions ("Resolve ... from deployment_summary.yaml" and "discover them dynamically from Azure").	3 / 3
Completeness	Clearly states what the skill does but offers no explicit "Use when..." trigger; per the guidelines, a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant terms ("aks, azure, koji, deployment context") but leans on jargon and lacks common natural variations a user would say; there is no conversational phrasing.	2 / 3
Distinctiveness Conflict Risk	Tied to a specific niche (Koji AKS deployment context) with distinct product keywords, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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-deployment-context/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.