CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-kubernetes

Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS, optimize AKS, AKS spot nodes, AKS cluster-autoscaler, rightsize AKS pod, pod rightsizing, over-provisioned AKS pod, pod resource requests and limits, Vertical Pod Autoscaler, VPA recommendations.

Quality

89%

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

The canonical home for this skill is azure-kubernetes in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-organized, appropriately split AKS planning skill that assumes reader competence and routes focused cost/operations workflows to real, one-level-deep reference files with keyword-triggered navigation. The main weaknesses are minor: several recommendations name features without their enabling flags, and the workflow lacks an explicit post-provision validation checkpoint.

Suggestions

Add the enabling CLI flags (or a pointer to the specific cli-reference.md section) for recommendations that currently name features only, such as Azure CNI powered by Cilium, App Routing addon with Gateway API, and Deployment Safeguards.

Add an explicit post-provision validation checkpoint at the end of the Workflow section (e.g., az aks show to confirm zones, SKU, and tier match the documented Day-0 decisions) to close the workflow-clarity gap.

Trim the 'MANDATORY COMPLIANCE' framing, the uncontextualized observability tool list, and the 'When to Use' triggers that duplicate the frontmatter description to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is efficient and assumes AKS competence ("Avoid B-series VMs — burstable SKUs cause performance/reliability issues", "Use Ephemeral OS disks (--node-osdisk-type Ephemeral)") with no basic-concept explanations. Minor trimmable spots keep it below the 'every token earns its place' anchor: the "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" framing, the uncontextualized tool list "Agentic CLI for AKS, Application Insights, Resource Health Center, AppLens detectors, and Azure Advisors", and redundancy between Quick Reference, When to Use, and Rules. It is clearly above anchor 3 since padding is minor, not a pattern.

4 / 5

Actionability

Concrete, executable guidance where it counts: "az aks stop/start", "--zones 1 2 3", "--enable-oidc-issuer --enable-workload-identity", an error-handling table with remediation commands, and a linked CLI reference with full az aks create commands. Minor gaps keep it below anchor 5: several recommendations name features without their enabling flags ("Azure CNI powered by Cilium", "App Routing addon with Gateway API", "Azure Policy + Deployment Safeguards").

4 / 5

Workflow Clarity

Rules 1–4 give a clear sequence (requirements → MCP tool discovery → SKU decision → document Day-0 rationale), decision areas are organized under a numbered Workflow, and checkpoints exist via the Guardrails ("If requirements are ambiguous for day-0 critical decisions, ask the user clarifying questions") and the Error Handling recovery table. Not anchor 5 because there is no explicit post-provision validation step (e.g., verifying the created cluster's zones/SKU/tier with az aks show); not anchor 3 because sequence and error-recovery paths are present, not merely listed steps with no checkpoints.

4 / 5

Progressive Disclosure

A clear overview body with 7 reference files (all verified to exist) linked with explicit load conditions: the Focused Cost Workflows table maps trigger keywords ("over-provisioned pods", "vertical pod autoscaler", "Spot VMs") to specific files, and "Load optional-aks-operations.md only when a focused optional AKS operational skill could improve the current task". References are one level deep — the reference files cross-link only to sibling files for shared steps (e.g., autoscaler → rightsizing metrics discovery) and to external Microsoft docs, not nested indirection — and focused workflow content (rightsizing queries, spot budget checks) is appropriately split out of the overview. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

96%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.

A strong description that explicitly states concrete capabilities across the AKS provisioning domain and pairs them with an explicit WHEN clause containing comprehensive, natural trigger terms with synonyms. The only weakness is minor overlap risk with the closely related sibling Azure skills, which the description does not disambiguate against.

DimensionReasoningScore

Specificity

Multiple concrete actions ("Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters") plus comprehensive, specifically enumerated coverage ("Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis)") match the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require noticeable coverage gaps, which are absent.

5 / 5

Completeness

Both questions are explicitly answered: a clear 'what' ("Plan, create, and configure production-ready AKS clusters" with the enumerated coverage areas) and a concrete explicit 'when' ("WHEN: create AKS environment, provision AKS, ..."). This matches the anchor for clearly and explicitly answering both what AND when with concrete trigger phrases; the missing-'when' cap at 3 clearly does not apply.

5 / 5

Trigger Term Quality

The WHEN clause covers natural trigger phrases comprehensively including synonyms: "create AKS environment, provision AKS, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS, optimize AKS, AKS spot nodes, AKS cluster-autoscaler, rightsize AKS pod, pod rightsizing, over-provisioned AKS pod, pod resource requests and limits, Vertical Pod Autoscaler, VPA recommendations" — matching the anchor for comprehensive coverage of natural terms including synonyms.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (AKS cluster provisioning/configuration) and triggers are AKS-prefixed, but broad phrases like "optimize AKS" and "secure AKS" carry minor overlap risk with closely related sibling Azure skills (azure-diagnostics, azure-kubernetes-app-deploy, aks-cost-optimization) that the body itself acknowledges; anchor 4 ('mostly distinct; minor overlap risk with closely related skills') fits better than 5, and it is clearly above anchor 3 since the domain is not generic.

4 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/azure-kubernetes/SKILL.md

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.