メニュー
Non-blocking cluster status peek — run at the end of Phases 3, 4, 5 to check AKS provisioning progress without hanging.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | kickstart-cluster-status |
| description | Non-blocking cluster status peek — run at the end of Phases 3, 4, 5 to check AKS provisioning progress without hanging. |
| disable-model-invocation | true |
A non-blocking peek at the background cluster provision. Run at the end of Phases 3, 4, and 5. Wrap in timeout to prevent hanging.
timeout 15 az aks show --name <cluster> --resource-group <rg> --subscription <sub> --query "{state:provisioningState, power:powerState.code}" --output json --only-show-errors
If timed out (exit 124), skip and retry next phase.
Succeeded: Attach ACR if not done yet (use the ACR attachment approach from /kickstart-handoff, step 6c). Remember this for Phase 6.Creating: Note it, continue.Failed: Get details from az monitor activity-log list --resource-group <rg> --status Failed --max-events 3. Common failures:
eastus2, westus3, southcentralus, canadacentral, swedencentral. Avoid eastus, westeurope, and southeastasia — they carry the most capacity pressure. Link to quota page: https://portal.azure.com/#view/Microsoft_Azure_Capacity/QuotaMenuBlade/~/myQuotasvscode_askQuestions.az aks create may have failed silently. Check the RG exists, retry creation.Also check ACR:
timeout 15 az acr show --name <acr> --resource-group <rg> --subscription <sub> --query provisioningState --output tsv --only-show-errors
ACR integration for AKS Automatic. Teaches attaching an ACR, image reference conventions (digest pinning, no :latest), and pull-secret-free authentication via the managed identity.
Writing idiomatic, safe, and reviewable Bicep templates for Azure resources.
Voice, tone, and interaction patterns for Kickstart agents.
Configure Infrastructure phase playbook — launch the dedicated Kickstart cluster-setup view, which collects and creates the Azure resources (subscription, resource group, AKS Automatic cluster, ACR) and hands the results back to the chat.
Deploy phase playbook — build, push, apply with Azure CLI and kubectl.
Design phase playbook — propose target architecture on AKS Automatic.