name	aks-manifest-migrate
description	Rewrite vanilla Kubernetes manifests or Helm charts toward AKS best practices. Use for: migrate manifests to aks, migrate helm chart to aks, convert loadbalancer to aks ingress, add workload identity, harden kubernetes for aks.
license	MIT
metadata	{"author":"GitHub Copilot","version":"0.1.0"}

AKS Manifest Migration

Use this skill after assessment is complete.

Activate this skill when the user wants to:

Never mutate the source directory. Write outputs to the -aks directory defined by the assessment skill.
Preserve business behavior while tightening platform behavior.
For HTTP workloads, prefer Service type ClusterIP plus AKS application routing ingress unless a direct LoadBalancer is required.
Prefer Microsoft Entra Workload ID over embedded credentials or pod-managed identity.
Add AKS workload hardening as first-class resources:
- requests and limits
- startup, readiness, and liveness probes
- HPA
- PDB
- topology spread
- network policy
Keep the output CRD-light by default. If Gateway API, service mesh, or Secrets Store CSI Driver are needed, document that dependency explicitly.
If the target cluster is already known, use mcp_azure_mcp_aks to confirm the ingress and networking assumptions before finalizing the result.

Choose the migration path
- raw manifest path
- Helm chart path
Apply the rewrite rules in references/migration-rules.md
Apply the Helm-specific guidance in references/helm-guidance.md when the source is a chart
Generate AKS target artifacts under the -aks output directory
Run aks-migration-harness before claiming completion

name	aks-manifest-migrate
description	Rewrite vanilla Kubernetes manifests or Helm charts toward AKS best practices. Use for: migrate manifests to aks, migrate helm chart to aks, convert loadbalancer to aks ingress, add workload identity, harden kubernetes for aks.
license	MIT
metadata	{"author":"GitHub Copilot","version":"0.1.0"}

Use this skill after assessment is complete.

Activate this skill when the user wants to:

Never mutate the source directory. Write outputs to the -aks directory defined by the assessment skill.
Preserve business behavior while tightening platform behavior.
For HTTP workloads, prefer Service type ClusterIP plus AKS application routing ingress unless a direct LoadBalancer is required.
Prefer Microsoft Entra Workload ID over embedded credentials or pod-managed identity.
Add AKS workload hardening as first-class resources:
- requests and limits
- startup, readiness, and liveness probes
- HPA
- PDB
- topology spread
- network policy
Keep the output CRD-light by default. If Gateway API, service mesh, or Secrets Store CSI Driver are needed, document that dependency explicitly.
If the target cluster is already known, use mcp_azure_mcp_aks to confirm the ingress and networking assumptions before finalizing the result.

Choose the migration path
- raw manifest path
- Helm chart path
Apply the rewrite rules in references/migration-rules.md
Apply the Helm-specific guidance in references/helm-guidance.md when the source is a chart
Generate AKS target artifacts under the -aks output directory
Run aks-migration-harness before claiming completion

aks-manifest-migrate