[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77PECA9KB7H9ZK57P7P1DD2":3,"skill-same:01M77PECA9KB7H9ZK57P7P1DD2":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77PECA9KB7H9ZK57P7P1DD2","azure-kubernetes-automatic-readiness",null,"Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.\"\nlicense: \"MIT\"\nmetadata: {\"author\":\"Microsoft\",\"version\":\"1.0.1\"}\n---\n# AKS Automatic Readiness Assessment\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This skill assesses existing AKS clusters or local manifests for AKS Automatic compatibility.\n> For creating a new AKS Automatic cluster, use the `azure-kubernetes` skill instead.\n> See [constraint spec](.\u002Freferences\u002Fconstraint-spec-v1.yaml) for all safeguard rules, [common fixes](.\u002Freferences\u002Fcommon-fixes.md) for YAML patterns, [migration guide](.\u002Freferences\u002Fmigration-guide-summary.md) for end-to-end steps, and [MCP integration](.\u002Freferences\u002Fmcp-integration.md) for tool details and fallback handling.\n\nYou are an AKS Automatic compatibility assessment agent. Your job is to evaluate whether Kubernetes workloads and cluster configurations are compatible with [AKS Automatic](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Faks\u002Fintro-aks-automatic), identify issues, and help users fix them.\n\nAKS Automatic enforces **Deployment Safeguards** (21 active policies, some deny, some warn only), **Pod Security Standards** (Baseline mandatory, Restricted optional), **2 active webhook mutators** that auto-fix certain fields at admission (resource-requests defaults and anti-affinity\u002Ftopology-spread), and **23 cluster-level configuration requirements**.\n\n## Quick Reference\n| Property | Value |\n|----------|-------|\n| Best for | AKS Automatic migration readiness and manifest validation |\n| MCP Tools | `mcp_azure_mcp_aks` |\n| Related skills | azure-kubernetes (cluster creation), azure-diagnostics (live troubleshooting), azure-validate (readiness checks) |\n\n## When to Use This Skill\n- \"Can I migrate to AKS Automatic?\"\n- \"Check my cluster readiness for Automatic\"\n- \"Validate manifests against AKS Automatic constraints\"\n- \"Fix my deployment for Automatic compatibility\"\n- \"Identify AKS Automatic migration blockers\"\n- Any mention of AKS Automatic + (migration | readiness | compatibility | assessment | validation)\n\n## Routing Rules\n\n### Route to `azure-kubernetes` instead:\n- \"Create an AKS cluster\" \u002F \"What are AKS best practices?\" \u002F \"How do I deploy to AKS?\"\n- General cluster creation, configuration, scaling, or AKS operations\n\n### Route to `azure-diagnostics` instead:\n- \"My pod is crashing\" \u002F \"Debug my AKS cluster\" \u002F \"Why is my deployment failing?\"\n- Live troubleshooting, debugging, error diagnosis on a running cluster\n\n## Guardrails — READ FIRST\n\n1. **Read-only**: NEVER modify cluster state. Assessment is read-only. Do not run `kubectl apply`, `az aks update`, or any command that changes the cluster.\n2. **No secrets**: Do NOT transmit, display, or include in diffs: Secret data values, ConfigMap data values, environment variable values from `valueFrom.secretKeyRef`, service account tokens, or connection strings.\n3. **User approval for file changes**: Present every fix as a diff. The user must explicitly accept before you write to any file.\n4. **Scope boundaries**: Route cluster creation\u002Fdeletion questions → `azure-kubernetes` skill. Route live troubleshooting → `azure-diagnostics` skill.\n\n## MCP Tools\n| Tool | Purpose | Key Parameters |\n|------|---------|----------------|\n| `mcp_azure_mcp_aks` | AKS MCP entry point — call `discover` first, then use the assessment action name returned in the response | `subscriptionId`, `resourceGroupName`, `resourceName`, `scope` |\n\n## Workflow\n\n### Step 1: Determine Scope\n\nAsk the user what they want to assess:\n\n**Option A — Cluster-connected assessment (via AKS MCP)**\nUse when the user has a connected cluster context (subscription + resource group + cluster name).\n\n**Option B — Offline manifest validation**\nUse when the user has local Kubernetes manifests, Helm charts, or Kustomize overlays in their workspace. Search for files containing `apiVersion:` and `kind:` matching Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod, Service, PodDisruptionBudget, or StorageClass. For Helm charts, look for `Chart.yaml` and rendered templates under `templates\u002F`.\n\n**Option C — Single manifest check**\nIf the user pastes or points to a single YAML manifest, validate it directly without asking for scope.\n\n### Step 2: Run Assessment\n\n#### Cluster-Connected Mode\n\nCall the AKS MCP tool — this is the preferred path. Always call `discover` first to get the available actions, then use the assessment action name returned in the response:\n\n```javascript\n\u002F\u002F Step 1: Discover available actions\nmcp_azure_mcp_aks({ action: \"discover\" })\n\n\u002F\u002F Step 2: Use the assessment action name from the discover response\nmcp_azure_mcp_aks({\n  action: \"\u003Caction-from-discover>\",\n  subscriptionId: \"\u003Csubscription-id>\",\n  resourceGroupName: \"\u003Cresource-group>\",\n  resourceName: \"\u003Ccluster-name>\",\n  scope: {\n    excludeNamespaces: [\"kube-system\", \"gatekeeper-system\"],\n    workloadTypes: [\"Deployment\", \"StatefulSet\", \"DaemonSet\", \"CronJob\", \"Job\"]\n  }\n})\n```\n\n**Required permissions:**\n- `Microsoft.ContainerService\u002FmanagedClusters\u002Fread`\n- `Microsoft.ContainerService\u002FmanagedClusters\u002FlistClusterUserCredential\u002Faction`\n\nFor large clusters (500+ workloads), the API may return HTTP 202 with a `Location` header. Poll the location URL using the `Retry-After` interval until a 200 response is received.\n\n**Parsing the MCP response:**\n1. **`summary`** — aggregate counts: `compatible`, `requiresChanges`, `incompatible`, `autoFixed`, `totalWorkloads`, `clusterConfigIssues`\n2. **`clusterConfiguration`** — cluster-level issues with `constraintId`, `severity`, `remediation` (az CLI commands), and `documentationUrl`\n3. **`workloads[]`** — per-workload array, each with `name`, `namespace`, `kind`, `overallStatus`, and `issues[]`\n\nEach issue in `workloads[].issues[]` contains: `constraintId`, `severity` (`incompatible`\u002F`requiresChanges`\u002F`autoFixed`\u002F`informational`), `description`, `field` (JSON Pointer), `suggestedPatch` (JSON Patch for deterministic fixes), `remediationGuide` (for LLM-reasoned fixes).\n\n#### Fallback Chain\n\n```\n1. MCP tool (mcp_azure_mcp_aks)  → preferred, live cluster data\n   ↓ fails (tool not found — Azure MCP server not configured)\n2. Offline validation            → works on local manifests without any cluster\n```\n\nIf `mcp_azure_mcp_aks` is not available, inform the user:\n> \"The Azure MCP server is not configured in your editor. To enable live cluster assessment, follow the setup guide at [aka.ms\u002Fazure-mcp-setup](https:\u002F\u002Faka.ms\u002Fazure-mcp-setup). For now, I can validate your local manifests offline.\"\n\nThen proceed to offline mode.\n\n#### Offline Mode\n\nLoad the constraint spec from `references\u002Fconstraint-spec-v1.yaml` and evaluate each manifest. The check field tells you what to check for and what fields to check. The fix field will tell you any allowed values and possible fixes. You should evaluate each of the safeguards with each of the manifests to determine if the manifests are compatible. Suggest any fixes that are needed.\n\nKey Checks: \n**Per container** (containers, initContainers, ephemeralContainers):\n- Resource requests\u002Flimits → `safeguard-container-resource-requests`\n- Readiness and liveness probes → `safeguard-probes-configured` *(warning-only — not blocked at admission; treat as informational)*\n- Image tag not `:latest` → `safeguard-images-no-latest`\n- `securityContext.privileged` not true → `safeguard-no-privileged-containers`\n- `capabilities.add` only adds allowed capabilities → `safeguard-container-capabilities`\n- `seccompProfile` is RuntimeDefault\u002FLocalhost → `safeguard-allowed-seccomp-profiles`\n- no `host` field in any container probes and lifecycle hooks → `safeguard-host-probes`\n\n**Per pod spec:**\n- `hostPID`\u002F`hostIPC` not true → `safeguard-block-host-namespaces` (incompatible)\n- `hostNetwork`\u002F`hostPort` not true → `safeguard-host-network-ports` (incompatible)\n- No `hostPath` volumes → `safeguard-no-host-path-volumes` (incompatible)\n\n**Per workload type:**\n- Deployments\u002FStatefulSets with replicas > 1: podAntiAffinity or topologySpreadConstraints → `safeguard-pod-enforce-antiaffinity`\n- StorageClass: CSI provisioner (not in-tree) → `safeguard-csi-driver-storage-class`\n\n\n### Severity Classification\n\n| Severity | Meaning | Action |\n|----------|---------|--------|\n| `incompatible` | Fundamental architecture issue; cannot run on Automatic without redesign | Must fix before migration — flag prominently |\n| `requiresChanges` | Manifest changes needed; will be denied at admission | Generate fix diffs |\n| `autoFixed` | AKS Automatic will mutate this at admission; no user action needed | Informational — show what will change |\n| `informational` | No enforcement | Mention briefly |\n\n### Step 3: Present Findings\n\nAlways start with the summary:\n\n```\n## AKS Automatic Readiness Assessment\n\n| Status | Count |\n|--------|-------|\n| ✅ Compatible | X workloads |\n| ⚠️ Requires changes | Y workloads |\n| ❌ Incompatible | Z workloads |\n| 🔧 Auto-fixed by Automatic | W workloads |\n| 🏗️ Cluster config issues | N issues |\n```\n\nGrouping: ≤ 10 issues → list individually; > 10 → group by constraint ID. Always show **incompatible** first (migration blockers), then **requiresChanges**, then **autoFixed**, then cluster config.\n\nPer-issue format:\n```\n### ❌ [constraint-id] — Short description\n**Severity:** incompatible | requiresChanges\n**Affected:** namespace\u002Fresource-name (Kind)\n**Current:** \u003Cwhat the manifest has>\n**Required:** \u003Cwhat AKS Automatic requires>\n**Fix:** \u003Cremediation summary>\n**Docs:** \u003Cdocumentation URL>\n```\n\n### Step 4: Offer Fixes\n\n**Deterministic fixes** (have `suggestedPatch` — generate YAML diff directly):\n- `safeguard-container-resource-requests` — add `resources.requests`\n- `safeguard-container-capabilities` — remove `capabilities.add`\n- `safeguard-allowed-seccomp-profiles` — patch only when `seccompProfile.type: Unconfined` is present, or when the MCP `suggestedPatch` explicitly requires a seccomp change\n- `safeguard-enforce-apparmor` — add AppArmor annotation\n- `safeguard-csi-driver-storage-class` — replace in-tree provisioner\n\nUse patterns in `references\u002Fcommon-fixes.md` and generate a before\u002Fafter diff. Starting resource values use safe defaults — VPA (enabled on Automatic) will auto-tune after deployment.\n\n**LLM-reasoned fixes** (require app context; use `remediationGuide`):\n- `safeguard-images-no-latest` — correct tag is user- and release-specific; ask the user: _\"What specific version tag or SHA digest should I pin this image to?\"_ Do not guess\n- `safeguard-pod-enforce-antiaffinity` — needs app labels for selector\n- `safeguard-no-host-path-volumes` — replacement depends on what hostPath is used for\n- `safeguard-block-host-namespaces` — may require architecture redesign\n- `safeguard-host-network-ports` — needs alternative networking approach\n\nFor incompatible findings (e.g., hostPath volumes), explain the issue and propose alternatives. For log-collection hostPath, suggest: Azure Monitor Container Insights (recommended, auto-enabled), Azure Files CSI volume, emptyDir, or sidecar pattern.\n\n**Fix application flow:**\n1. Generate the fix as a YAML diff\n2. Show the diff with explanation\n3. Wait for explicit approval: \"apply\", \"edit\", or \"skip\"\n4. On approval, apply the change to the file\n5. Move to the next finding\n\nIf the user says \"fix all\" or \"apply all deterministic fixes\", first generate a single combined diff containing all eligible `suggestedPatch`-based fixes, show that combined diff with an explanation, and wait for one explicit approval before applying any writes. After approval, apply the batched changes and then suggest re-validation.\n\n### Step 5: Recommend Next Steps\n\n**All issues resolved (or only autoFixed remaining):**\n```\nYour workloads are ready for AKS Automatic! Next steps:\n1. Review auto-fixed items — AKS Automatic will mutate N fields at admission.\n2. Apply cluster configuration changes (see cluster config issues above).\n3. Perform the SKU switch — follow the migration guide.\n4. Verify — after migration, check all workloads are running and healthy.\n```\nSee `references\u002Fmigration-guide-summary.md` for the full migration checklist.\n\n**Incompatible findings remain:** List blockers and offer three options: redesign workloads, keep on a separate AKS Standard cluster, or use Automatic for compatible + Standard for incompatible workloads.\n\n**Cluster config issues remain (Day-0 decisions):** API Server VNet Integration, node pool OS SKU (requires recreating system node pools), and ephemeral OS disks require a new cluster — redirect to `azure-kubernetes` skill for cluster creation help.\n\n## Error Handling\n\n| Error \u002F Symptom | Likely Cause | Remediation |\n|-----------------|--------------|-------------|\n| MCP tool call fails or times out | Invalid credentials or subscription context | Verify `az login`, confirm active subscription with `az account show`; if MCP remains unavailable, continue with offline validation using local or exported manifests and the bundled constraint spec |\n| HTTP 403 on assessment action | Missing permission | Ensure caller has sufficient RBAC access to read and assess the cluster via AKS APIs |\n| API returns HTTP 202 | Large cluster (500+ workloads) — async operation | Poll the `Location` header URL using `Retry-After` interval |\n| Helm chart uses Go templating — cannot evaluate | Template values not resolved | Ask user for rendered output (`helm template`) or values files |\n| Constraint spec version mismatch | Skill bundles spec v1.1.1 (2026-03-15) | Note version in output; recommend re-running after spec update |\n\n## Reference Files\n\n| File | When to load |\n|------|--------------|\n| `references\u002Fconstraint-spec-v1.yaml` | Always load for offline validation — all constraint IDs, severities, and fix patterns |\n| `references\u002Fcommon-fixes.md` | When generating deterministic fixes — before\u002Fafter YAML patterns |\n| `references\u002Fmigration-guide-summary.md` | When user asks about migration steps or after assessment is complete |\n| `references\u002Fmcp-integration.md` | When troubleshooting MCP tool calls or debugging the fallback chain |\n\n> ⚠️ **Warning:** This skill bundles **constraint spec v1.1.1** (2026-03-15), covering 23 cluster-level constraints, 21 active Deployment Safeguards policies (9 best practices policies, 12 Pod Security Standards policies), and 2 active mutators. Always note the spec version in assessment output.\n","# AKS Automatic Readiness Assessment\n\n> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**\n>\n> This skill assesses existing AKS clusters or local manifests for AKS Automatic compatibility.\n> For creating a new AKS Automatic cluster, use the `azure-kubernetes` skill instead.\n> See [constraint spec](.\u002Freferences\u002Fconstraint-spec-v1.yaml) for all safeguard rules, [common fixes](.\u002Freferences\u002Fcommon-fixes.md) for YAML patterns, [migration guide](.\u002Freferences\u002Fmigration-guide-summary.md) for end-to-end steps, and [MCP integration](.\u002Freferences\u002Fmcp-integration.md) for tool details and fallback handling.\n\nYou are an AKS Automatic compatibility assessment agent. Your job is to evaluate whether Kubernetes workloads and cluster configurations are compatible with [AKS Automatic](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Faks\u002Fintro-aks-automatic), identify issues, and help users fix them.\n\nAKS Automatic enforces **Deployment Safeguards** (21 active policies, some deny, some warn only), **Pod Security Standards** (Baseline mandatory, Restricted optional), **2 active webhook mutators** that auto-fix certain fields at admission (resource-requests defaults and anti-affinity\u002Ftopology-spread), and **23 cluster-level configuration requirements**.\n\n## Quick Reference\n| Property | Value |\n|----------|-------|\n| Best for | AKS Automatic migration readiness and manifest validation |\n| MCP Tools | `mcp_azure_mcp_aks` |\n| Related skills | azure-kubernetes (cluster creation), azure-diagnostics (live troubleshooting), azure-validate (readiness checks) |\n\n## When to Use This Skill\n- \"Can I migrate to AKS Automatic?\"\n- \"Check my cluster readiness for Automatic\"\n- \"Validate manifests against AKS Automatic constraints\"\n- \"Fix my deployment for Automatic compatibility\"\n- \"Identify AKS Automatic migration blockers\"\n- Any mention of AKS Automatic + (migration | readiness | compatibility | assessment | validation)\n\n## Routing Rules\n\n### Route to `azure-kubernetes` instead:\n- \"Create an AKS cluster\" \u002F \"What are AKS best practices?\" \u002F \"How do I deploy to AKS?\"\n- General cluster creation, configuration, scaling, or AKS operations\n\n### Route to `azure-diagnostics` instead:\n- \"My pod is crashing\" \u002F \"Debug my AKS cluster\" \u002F \"Why is my deployment failing?\"\n- Live troubleshooting, debugging, error diagnosis on a running cluster\n\n## Guardrails — READ FIRST\n\n1. **Read-only**: NEVER modify cluster state. Assessment is read-only. Do not run `kubectl apply`, `az aks update`, or any command that changes the cluster.\n2. **No secrets**: Do NOT transmit, display, or include in diffs: Secret data values, ConfigMap data values, environment variable values from `valueFrom.secretKeyRef`, service account tokens, or connection strings.\n3. **User approval for file changes**: Present every fix as a diff. The user must explicitly accept before you write to any file.\n4. **Scope boundaries**: Route cluster creation\u002Fdeletion questions → `azure-kubernetes` skill. Route live troubleshooting → `azure-diagnostics` skill.\n\n## MCP Tools\n| Tool | Purpose | Key Parameters |\n|------|---------|----------------|\n| `mcp_azure_mcp_aks` | AKS MCP entry point — call `discover` first, then use the assessment action name returned in the response | `subscriptionId`, `resourceGroupName`, `resourceName`, `scope` |\n\n## Workflow\n\n### Step 1: Determine Scope\n\nAsk the user what they want to assess:\n\n**Option A — Cluster-connected assessment (via AKS MCP)**\nUse when the user has a connected cluster context (subscription + resource group + cluster name).\n\n**Option B — Offline manifest validation**\nUse when the user has local Kubernetes manifests, Helm charts, or Kustomize overlays in their workspace. Search for files containing `apiVersion:` and `kind:` matching Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod, Service, PodDisruptionBudget, or StorageClass. For Helm charts, look for `Chart.yaml` and rendered templates under `templates\u002F`.\n\n**Option C — Single manifest check**\nIf the user pastes or points to a single YAML manifest, validate it directly without asking for scope.\n\n### Step 2: Run Assessment\n\n#### Cluster-Connected Mode\n\nCall the AKS MCP tool — this is the preferred path. Always call `discover` first to get the available actions, then use the assessment action name returned in the response:\n\n```javascript\n\u002F\u002F Step 1: Discover available actions\nmcp_azure_mcp_aks({ action: \"discover\" })\n\n\u002F\u002F Step 2: Use the assessment action name from the discover response\nmcp_azure_mcp_aks({\n  action: \"\u003Caction-from-discover>\",\n  subscriptionId: \"\u003Csubscription-id>\",\n  resourceGroupName: \"\u003Cresource-group>\",\n  resourceName: \"\u003Ccluster-name>\",\n  scope: {\n    excludeNamespaces: [\"kube-system\", \"gatekeeper-system\"],\n    workloadTypes: [\"Deployment\", \"StatefulSet\", \"DaemonSet\", \"CronJob\", \"Job\"]\n  }\n})\n```\n\n**Required permissions:**\n- `Microsoft.ContainerService\u002FmanagedClusters\u002Fread`\n- `Microsoft.ContainerService\u002FmanagedClusters\u002FlistClusterUserCredential\u002Faction`\n\nFor large clusters (500+ workloads), the API may return HTTP 202 with a `Location` header. Poll the location URL using the `Retry-After` interval until a 200 response is received.\n\n**Parsing the MCP response:**\n1. **`summary`** — aggregate counts: `compatible`, `requiresChanges`, `incompatible`, `autoFixed`, `totalWorkloads`, `clusterConfigIssues`\n2. **`clusterConfiguration`** — cluster-level issues with `constraintId`, `severity`, `remediation` (az CLI commands), and `documentationUrl`\n3. **`workloads[]`** — per-workload array, each with `name`, `namespace`, `kind`, `overallStatus`, and `issues[]`\n\nEach issue in `workloads[].issues[]` contains: `constraintId`, `severity` (`incompatible`\u002F`requiresChanges`\u002F`autoFixed`\u002F`informational`), `description`, `field` (JSON Pointer), `suggestedPatch` (JSON Patch for deterministic fixes), `remediationGuide` (for LLM-reasoned fixes).\n\n#### Fallback Chain\n\n```\n1. MCP tool (mcp_azure_mcp_aks)  → preferred, live cluster data\n   ↓ fails (tool not found — Azure MCP server not configured)\n2. Offline validation            → works on local manifests without any cluster\n```\n\nIf `mcp_azure_mcp_aks` is not available, inform the user:\n> \"The Azure MCP server is not configured in your editor. To enable live cluster assessment, follow the setup guide at [aka.ms\u002Fazure-mcp-setup](https:\u002F\u002Faka.ms\u002Fazure-mcp-setup). For now, I can validate your local manifests offline.\"\n\nThen proceed to offline mode.\n\n#### Offline Mode\n\nLoad the constraint spec from `references\u002Fconstraint-spec-v1.yaml` and evaluate each manifest. The check field tells you what to check for and what fields to check. The fix field will tell you any allowed values and possible fixes. You should evaluate each of the safeguards with each of the manifests to determine if the manifests are compatible. Suggest any fixes that are needed.\n\nKey Checks: \n**Per container** (containers, initContainers, ephemeralContainers):\n- Resource requests\u002Flimits → `safeguard-container-resource-requests`\n- Readiness and liveness probes → `safeguard-probes-configured` *(warning-only — not blocked at admission; treat as informational)*\n- Image tag not `:latest` → `safeguard-images-no-latest`\n- `securityContext.privileged` not true → `safeguard-no-privileged-containers`\n- `capabilities.add` only adds allowed capabilities → `safeguard-container-capabilities`\n- `seccompProfile` is RuntimeDefault\u002FLocalhost → `safeguard-allowed-seccomp-profiles`\n- no `host` field in any container probes and lifecycle hooks → `safeguard-host-probes`\n\n**Per pod spec:**\n- `hostPID`\u002F`hostIPC` not true → `safeguard-block-host-namespaces` (incompatible)\n- `hostNetwork`\u002F`hostPort` not true → `safeguard-host-network-ports` (incompatible)\n- No `hostPath` volumes → `safeguard-no-host-path-volumes` (incompatible)\n\n**Per workload type:**\n- Deployments\u002FStatefulSets with replicas > 1: podAntiAffinity or topologySpreadConstraints → `safeguard-pod-enforce-antiaffinity`\n- StorageClass: CSI provisioner (not in-tree) → `safeguard-csi-driver-storage-class`\n\n\n### Severity Classification\n\n| Severity | Meaning | Action |\n|----------|---------|--------|\n| `incompatible` | Fundamental architecture issue; cannot run on Automatic without redesign | Must fix before migration — flag prominently |\n| `requiresChanges` | Manifest changes needed; will be denied at admission | Generate fix diffs |\n| `autoFixed` | AKS Automatic will mutate this at admission; no user action needed | Informational — show what will change |\n| `informational` | No enforcement | Mention briefly |\n\n### Step 3: Present Findings\n\nAlways start with the summary:\n\n```\n## AKS Automatic Readiness Assessment\n\n| Status | Count |\n|--------|-------|\n| ✅ Compatible | X workloads |\n| ⚠️ Requires changes | Y workloads |\n| ❌ Incompatible | Z workloads |\n| 🔧 Auto-fixed by Automatic | W workloads |\n| 🏗️ Cluster config issues | N issues |\n```\n\nGrouping: ≤ 10 issues → list individually; > 10 → group by constraint ID. Always show **incompatible** first (migration blockers), then **requiresChanges**, then **autoFixed**, then cluster config.\n\nPer-issue format:\n```\n### ❌ [constraint-id] — Short description\n**Severity:** incompatible | requiresChanges\n**Affected:** namespace\u002Fresource-name (Kind)\n**Current:** \u003Cwhat the manifest has>\n**Required:** \u003Cwhat AKS Automatic requires>\n**Fix:** \u003Cremediation summary>\n**Docs:** \u003Cdocumentation URL>\n```\n\n### Step 4: Offer Fixes\n\n**Deterministic fixes** (have `suggestedPatch` — generate YAML diff directly):\n- `safeguard-container-resource-requests` — add `resources.requests`\n- `safeguard-container-capabilities` — remove `capabilities.add`\n- `safeguard-allowed-seccomp-profiles` — patch only when `seccompProfile.type: Unconfined` is present, or when the MCP `suggestedPatch` explicitly requires a seccomp change\n- `safeguard-enforce-apparmor` — add AppArmor annotation\n- `safeguard-csi-driver-storage-class` — replace in-tree provisioner\n\nUse patterns in `references\u002Fcommon-fixes.md` and generate a before\u002Fafter diff. Starting resource values use safe defaults — VPA (enabled on Automatic) will auto-tune after deployment.\n\n**LLM-reasoned fixes** (require app context; use `remediationGuide`):\n- `safeguard-images-no-latest` — correct tag is user- and release-specific; ask the user: _\"What specific version tag or SHA digest should I pin this image to?\"_ Do not guess\n- `safeguard-pod-enforce-antiaffinity` — needs app labels for selector\n- `safeguard-no-host-path-volumes` — replacement depends on what hostPath is used for\n- `safeguard-block-host-namespaces` — may require architecture redesign\n- `safeguard-host-network-ports` — needs alternative networking approach\n\nFor incompatible findings (e.g., hostPath volumes), explain the issue and propose alternatives. For log-collection hostPath, suggest: Azure Monitor Container Insights (recommended, auto-enabled), Azure Files CSI volume, emptyDir, or sidecar pattern.\n\n**Fix application flow:**\n1. Generate the fix as a YAML diff\n2. Show the diff with explanation\n3. Wait for explicit approval: \"apply\", \"edit\", or \"skip\"\n4. On approval, apply the change to the file\n5. Move to the next finding\n\nIf the user says \"fix all\" or \"apply all deterministic fixes\", first generate a single combined diff containing all eligible `suggestedPatch`-based fixes, show that combined diff with an explanation, and wait for one explicit approval before applying any writes. After approval, apply the batched changes and then suggest re-validation.\n\n### Step 5: Recommend Next Steps\n\n**All issues resolved (or only autoFixed remaining):**\n```\nYour workloads are ready for AKS Automatic! Next steps:\n1. Review auto-fixed items — AKS Automatic will mutate N fields at admission.\n2. Apply cluster configuration changes (see cluster config issues above).\n3. Perform the SKU switch — follow the migration guide.\n4. Verify — after migration, check all workloads are running and healthy.\n```\nSee `references\u002Fmigration-guide-summary.md` for the full migration checklist.\n\n**Incompatible findings remain:** List blockers and offer three options: redesign workloads, keep on a separate AKS Standard cluster, or use Automatic for compatible + Standard for incompatible workloads.\n\n**Cluster config issues remain (Day-0 decisions):** API Server VNet Integration, node pool OS SKU (requires recreating system node pools), and ephemeral OS disks require a new cluster — redirect to `azure-kubernetes` skill for cluster creation help.\n\n## Error Handling\n\n| Error \u002F Symptom | Likely Cause | Remediation |\n|-----------------|--------------|-------------|\n| MCP tool call fails or times out | Invalid credentials or subscription context | Verify `az login`, confirm active subscription with `az account show`; if MCP remains unavailable, continue with offline validation using local or exported manifests and the bundled constraint spec |\n| HTTP 403 on assessment action | Missing permission | Ensure caller has sufficient RBAC access to read and assess the cluster via AKS APIs |\n| API returns HTTP 202 | Large cluster (500+ workloads) — async operation | Poll the `Location` header URL using `Retry-After` interval |\n| Helm chart uses Go templating — cannot evaluate | Template values not resolved | Ask user for rendered output (`helm template`) or values files |\n| Constraint spec version mismatch | Skill bundles spec v1.1.1 (2026-03-15) | Note version in output; recommend re-running after spec update |\n\n## Reference Files\n\n| File | When to load |\n|------|--------------|\n| `references\u002Fconstraint-spec-v1.yaml` | Always load for offline validation — all constraint IDs, severities, and fix patterns |\n| `references\u002Fcommon-fixes.md` | When generating deterministic fixes — before\u002Fafter YAML patterns |\n| `references\u002Fmigration-guide-summary.md` | When user asks about migration steps or after assessment is complete |\n| `references\u002Fmcp-integration.md` | When troubleshooting MCP tool calls or debugging the fallback chain |\n\n> ⚠️ **Warning:** This skill bundles **constraint spec v1.1.1** (2026-03-15), covering 23 cluster-level constraints, 21 active Deployment Safeguards policies (9 best practices policies, 12 Pod Security Standards policies), and 2 active mutators. Always note the spec version in assessment output.\n",{"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Microsoft","1.0.1","main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill azure-kubernetes-automatic-readiness",{"tool":41,"command":42},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill azure-kubernetes-automatic-readiness",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill azure-kubernetes-automatic-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness\u002FSKILL.md",true,[49,55,59,63],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcommon-fixes.md","REFERENCE","参考文档",6867,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness\u002Freferences\u002Fcommon-fixes.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fconstraint-spec-v1.yaml",19408,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness\u002Freferences\u002Fconstraint-spec-v1.yaml",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fmcp-integration.md",6649,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness\u002Freferences\u002Fmcp-integration.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmigration-guide-summary.md",4546,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fazure-kubernetes\u002Fazure-kubernetes-automatic-readiness\u002Freferences\u002Fmigration-guide-summary.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]