[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699390WT2C0D71HN9395FCQ":3,"skill-same:01M699390WT2C0D71HN9395FCQ":76},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M699390WT2C0D71HN9395FCQ","gke-ai-troubleshooting-tpu-slice-mig-stuck-updating",null,"Diagnose and resolve GKE TPU Dynamic Slice creation and JobSet scheduling failures blocked by underlying Compute Engine managed instance groups (MIGs) stuck in an updating or unstable state (isStable=False). Use when TPU slice creation fails with a SliceCreationFailed status reason, when JobSets remain stuck in pending, or when MIG status reflects isStable=False or versionTarget.isReached=False during TPU slice formation. Don't use for SliceCreationFailed causes unrelated to MIG stability (use gke-ai-troubleshooting-tpu-dynamic-slices-monitoring) or general pod scheduling failures unrelated to TPU slices.","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-ai-troubleshooting-tpu-slice-mig-stuck-updating\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"gke ai troubleshooting tpu slice mig stuck updating","tpu","slice","gke","troubleshooting","mig","when","containers","managed","pending","for","false","creation","compute","scheduling","general","use","engine","monitoring","diagnose","2026-11-10 10:12:30",false,"---\nname: gke-ai-troubleshooting-tpu-slice-mig-stuck-updating\ndescription: >-\n  Diagnose and resolve GKE TPU Dynamic Slice creation and JobSet scheduling\n  failures blocked by underlying Compute Engine managed instance groups (MIGs)\n  stuck in an updating or unstable state (isStable=False). Use when TPU slice\n  creation fails with a SliceCreationFailed status reason, when JobSets remain\n  stuck in pending, or when MIG status reflects isStable=False or\n  versionTarget.isReached=False during TPU slice formation. Don't use for\n  SliceCreationFailed causes unrelated to MIG stability (use\n  gke-ai-troubleshooting-tpu-dynamic-slices-monitoring) or general pod\n  scheduling failures unrelated to TPU slices.\nmetadata:\n  version: \"1.0.1\"\n  category: Containers\n---\n\n# Troubleshoot GKE TPU slice creation blocked by an unstable MIG\n\nThis skill helps diagnose GKE TPU Dynamic Slice creation failures and JobSet\nscheduling delays when the Compute Engine managed instance groups (MIGs) that\nback the TPU node pool aren't stable (`status.isStable: false`).\n\nA `SliceCreationFailed` status reason means that slice creation failed because\nprerequisites weren't met (for example, required Compute Engine resources are\nmissing) or preflight checks failed (see\n[Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)).\nA MIG that is still creating, updating, or repairing instances is one cause to\ncheck. This skill checks the slice status first, then the stability of the\nbacking MIGs.\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating)\"`\nand append `agent-skills\u002F1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating)` to `User-Agent` headers.\n\n## Prerequisites\n\n- **Google Cloud SDK & Tools**:\n  - For installing and initializing `gcloud` (project selection and\n    authentication) and enabling the GKE API, follow\n    [Before you begin](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt).\n  - For installing `kubectl` and configuring cluster credentials, follow the\n    \"Install kubectl\", \"Install required plugins\", and \"Store cluster\n    information for kubectl\" sections of\n    [Install kubectl and configure cluster access](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcluster-access-for-kubectl.md.txt).\n- **API Enablement & Billing**:\n  - Verify that the project has an active Cloud Billing account.\n  - Enable APIs: `container.googleapis.com`, `compute.googleapis.com`, and\n    `logging.googleapis.com`.\n- **Required IAM Roles**:\n  - Logs Viewer (`roles\u002Flogging.viewer`): Inspect Cloud Audit Logs for MIG\n    errors.\n  - Compute Viewer (`roles\u002Fcompute.viewer`): Check MIG stability (`isStable`)\n    and instance progress.\n  - Kubernetes Engine Viewer (`roles\u002Fcontainer.viewer`): Inspect Slice custom\n    resources (`slices.accelerator.gke.io`), nodes, and cluster operations.\n- **Documentation**:\n  - [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n    (Sections: \"Before you begin\", \"Create a Slice custom resource\", \"Monitor\n    the status of the Slice custom resource\", \"Verify the status of the nodes\n    and the partitions\", \"Upgrade your node pools\")\n  - [Install kubectl and configure cluster access](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcluster-access-for-kubectl.md.txt)\n    (Sections: \"Install kubectl\", \"Install required plugins\", \"Store cluster\n    information for kubectl\")\n  - [Add and manage node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-pools.md.txt)\n    (Sections: \"View node pools in a Standard cluster\")\n  - [View information about MIGs and managed instances](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt)\n    (Sections: \"Check whether a MIG is stable\", \"Check the status of managed\n    instances\", \"List instance errors\")\n  - [Automatically apply VM configuration updates in a MIG](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Frolling-out-updates-to-managed-instance-groups.md.txt)\n    (Sections: \"Verify whether an update rollout is complete\")\n  - [Manually upgrade a cluster's control plane or node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt)\n    (Sections: \"Check node pool upgrade status\", \"Cancel a node pool upgrade\",\n    \"Resume a node pool upgrade\", \"Roll back a node pool upgrade\")\n  - [Auto-repair nodes](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-auto-repair.md.txt)\n    (Sections: \"Get information about recent automated repair events\")\n  - [Troubleshoot GKE Standard node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Fnode-pools.md.txt)\n    (Sections: \"Issue: Node pool creation fails due to insufficient resources\")\n  - [Troubleshoot TPUs in GKE](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Ftpus.md.txt)\n    (Sections: \"Insufficient quota to satisfy the TPU request\", \"Insufficient\n    TPU resources to satisfy the TPU request\")\n  - [REST Resource: projects.locations.clusters.nodePools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Freference\u002Frest\u002Fv1\u002Fprojects.locations.clusters.nodePools.md.txt)\n    (Sections: \"Resource: NodePool\")\n  - [Schedule dynamic slices with Kueue and TAS](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fuse-gke-dynamic-slicing.md.txt)\n    (Sections: \"Monitor the status of the slice\")\n  - [About TPUs in GKE](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fconcepts\u002Ftpus.md.txt)\n  - [Get support](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fgetting-support.md.txt)\n    (Sections: \"Before you contact support\")\n\n> **Read-only rule**: Run read-only diagnostic commands only. Never drain,\n> delete, or re-create nodes, or run any other command that changes the cluster.\n> Give the user any fix to apply themselves.\n\nWhen you recommend a fix, link the doc section that describes it.\n\n---\n\n## Diagnostic workflow\n\n### Step 0: Collect context and set the investigation window `[Low Risk]`\n\nCollect the necessary contextual parameters from the user prompt or environment:\n- `{project_id}`, `{cluster_name}`, `{location}`, `{nodepool_name}`, and\n  `{issue_time}`.\n- `{mig_name}` and `{zone}`: Name and zone of the managed instance group that\n  backs `{nodepool_name}`, from the node pool's `instanceGroupUrls` field (see\n  [View node pools in a Standard cluster](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-pools.md.txt)\n  and\n  [Resource: NodePool](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Freference\u002Frest\u002Fv1\u002Fprojects.locations.clusters.nodePools.md.txt)).\n  If `{nodepool_name}` or `{mig_name}` isn't already known from a failing\n  `Slice`, find the affected partition, nodes, and backing MIG by following\n  [Verify the status of the nodes and the partitions](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt).\n- **Time window**: By default, query a 60-minute window `[{issue_time} - 30m,\n  {issue_time} + 30m]` (`{start_time}` to `{end_time}`).\n\n---\n\n### Step 1: Detect slice creation failures and MIG errors `[Low Risk]`\n\n1. **Inspect Slice status and partition nodes**: Check the `Slice` custom\n   resource `Status.Conditions` for a `SliceCreationFailed` status reason and\n   identify the affected partitions, nodes, and `{mig_name}` by following the\n   \"Monitor the status of the Slice custom resource\" and \"Verify the status of\n   the nodes and the partitions\" sections of\n   [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt),\n   and\n   [Monitor the status of the slice](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fuse-gke-dynamic-slicing.md.txt).\n2. **Query Cloud Logging for MIG errors**: Once `{mig_name}` is identified (or\n   by narrowing the results to `{mig_name}` once known), run this Cloud Logging\n   query to detect errors on the backing instance group manager across\n   `[{start_time}, {end_time}]`:\n   ```\n   resource.type=\"gce_instance_group_manager\"\n   resource.labels.instance_group_manager_name=\"{mig_name}\"\n   severity>=ERROR\n   timestamp >= \"{start_time}\" AND timestamp \u003C= \"{end_time}\"\n   ```\n- **Findings**:\n  - If the `Slice` status reports `SliceCreationFailed` or the logs show\n    instance group errors, proceed to Step 2.\n  - If no error logs match and the TPU `Slice` status is `ACTIVE`, rule out MIG\n    instability and check workload configuration.\n\n---\n\n### Step 2: Check MIG stability (`status.isStable`) `[Low Risk]`\n\nFollow\n[Check whether a MIG is stable](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt)\nto inspect the stability (`status.isStable`) and version target status\n(`status.versionTarget.isReached`) of `{mig_name}`:\n\n- **What the fields mean**:\n  - `status.isStable: false`: Changes are active or pending, or the MIG itself\n    is being modified. Proceed to Step 3.\n  - `status.versionTarget.isReached: false`: At least one instance isn't running\n    the target version yet (see\n    [Automatically apply VM configuration updates in a MIG](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Frolling-out-updates-to-managed-instance-groups.md.txt)).\n    Proceed to Step 3.\n  - `status.isStable: true` and `status.versionTarget.isReached: true`: No\n    instances are undergoing or scheduled for changes (`currentAction` is `NONE`\n    for all instances), and the MIG itself isn't being modified. This rules out\n    MIG instability. If the `Slice` is still in `SliceCreationFailed`, hand off\n    to `gke-ai-troubleshooting-tpu-dynamic-slices-monitoring`, or follow the\n    \"Create a Slice custom resource\" and \"Verify the status of the nodes and the\n    partitions\" sections of\n    [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt).\n\n---\n\n### Step 3: Find failed or stalled instance operations `[Low Risk]`\n\nDirect the user to the \"Check the status of managed instances\" and \"List\ninstance errors\" sections of\n[View information about MIGs and managed instances](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt)\n(include both section names and the document title) to inspect individual\ninstance states (`currentAction` and `instanceStatus`) and list the most recent\nerrors in `{mig_name}`:\n\n- If the errors show capacity or quota failures such as\n  `ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS` or `QUOTA_EXCEEDED`, go to Step 5,\n  item 2.\n- Otherwise, proceed to Step 4 to check for node pool upgrade or auto-repair\n  operations.\n\n---\n\n### Step 4: Check node pool operations `[Low Risk]`\n\nA MIG that is still changing instances can be the result of a node pool upgrade\nor repair:\n\n1. **Check node pool upgrades**: Follow\n   [Check node pool upgrade status](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt)\n   to list the cluster operations and find upgrade operations targeting\n   `{nodepool_name}` in `[{start_time}, {end_time}]`. Also review\n   [Upgrade your node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n   for dynamic slicing upgrade requirements (required surge settings and\n   deleting active super-slices before upgrading).\n   - If an upgrade operation is still running, go to Step 5, item 1 or item 3.\n   - If an upgrade operation was cancelled, failed, or is incomplete, go to Step\n     5, item 4.\n2. **Check automated node repairs**: Follow\n   [Get information about recent automated repair events](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-auto-repair.md.txt)\n   to check for repair operations on `{nodepool_name}`.\n   - If a node auto-repair operation is running, go to Step 5, item 1.\n3. **If no operation or error explains the unstable MIG**: Go to Step 5, item 5\n   to contact Cloud Customer Care.\n\n---\n\n### Step 5: Resolution `[High Risk]`\n\n> **Guardrail**: Don't modify GKE-managed instance groups or VMs directly\n> through Compute Engine. Manage node pools through GKE.\n\n1. **Wait for an ongoing update or auto-repair to finish**: If a node pool\n   upgrade or automated repair is still making progress, the user can wait until\n   the MIG is stable (`status.isStable: true`) by following\n   [Check whether a MIG is stable](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt).\n2. **Resolve capacity or quota errors**: When Step 3 shows\n   `ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS` or `QUOTA_EXCEEDED`, rolling back\n   an upgrade won't resolve the shortage. Follow\n   [Issue: Node pool creation fails due to insufficient resources](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Fnode-pools.md.txt)\n   and the \"Insufficient quota to satisfy the TPU request\" and \"Insufficient TPU\n   resources to satisfy the TPU request\" sections of\n   [Troubleshoot TPUs in GKE](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Ftpus.md.txt).\n3. **Cancel an in-progress node pool upgrade**: If the user wants to stop an\n   upgrade that is still running, follow\n   [Cancel a node pool upgrade](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt).\n   For dynamic slicing node pools, also check\n   [Upgrade your node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n   for the required surge settings and deleting active super-slices before\n   upgrading.\n4. **Resume or roll back a cancelled, failed, or incomplete node pool upgrade**:\n   - Follow the \"Resume a node pool upgrade\" or \"Roll back a node pool upgrade\"\n     sections of\n     [Manually upgrade a cluster's control plane or node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt).\n     As documented there, rollback applies if an in-progress upgrade was\n     cancelled, the upgrade failed, or the upgrade is incomplete due to a\n     maintenance window timing out (you can't roll back node pools once they\n     have been successfully upgraded); alternatively, a cancelled or failed,\n     partially completed upgrade can be resumed.\n   - Afterwards, verify that the MIG is stable by following\n     [Check whether a MIG is stable](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt).\n5. **Escalate unexplained MIG instability**: If no node pool upgrade, repair\n   operation, or capacity\u002Fquota error explains why `{mig_name}` remains\n   unstable, direct the user to Cloud Customer Care by following\n   [Get support](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fgetting-support.md.txt).\n6. **Verify node pool and slice recovery**: After the instance group is stable\n   (`status.isStable: true`), follow the \"Monitor the status of the Slice custom\n   resource\" and \"Create a Slice custom resource\" sections of\n   [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n   to verify that the `Slice` reaches the `ACTIVE` state. If the `Slice` stays\n   in `SliceCreationFailed` after the MIG stabilizes, check whether the retry\n   annotation documented in \"Create a Slice custom resource\" is set on the\n   `Slice`.\n","# Troubleshoot GKE TPU slice creation blocked by an unstable MIG\n\nThis skill helps diagnose GKE TPU Dynamic Slice creation failures and JobSet\nscheduling delays when the Compute Engine managed instance groups (MIGs) that\nback the TPU node pool aren't stable (`status.isStable: false`).\n\nA `SliceCreationFailed` status reason means that slice creation failed because\nprerequisites weren't met (for example, required Compute Engine resources are\nmissing) or preflight checks failed (see\n[Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)).\nA MIG that is still creating, updating, or repairing instances is one cause to\ncheck. This skill checks the slice status first, then the stability of the\nbacking MIGs.\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating)\"`\nand append `agent-skills\u002F1.0 (skill:gke-ai-troubleshooting-tpu-slice-mig-stuck-updating)` to `User-Agent` headers.\n\n## Prerequisites\n\n- **Google Cloud SDK & Tools**:\n  - For installing and initializing `gcloud` (project selection and\n    authentication) and enabling the GKE API, follow\n    [Before you begin](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt).\n  - For installing `kubectl` and configuring cluster credentials, follow the\n    \"Install kubectl\", \"Install required plugins\", and \"Store cluster\n    information for kubectl\" sections of\n    [Install kubectl and configure cluster access](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcluster-access-for-kubectl.md.txt).\n- **API Enablement & Billing**:\n  - Verify that the project has an active Cloud Billing account.\n  - Enable APIs: `container.googleapis.com`, `compute.googleapis.com`, and\n    `logging.googleapis.com`.\n- **Required IAM Roles**:\n  - Logs Viewer (`roles\u002Flogging.viewer`): Inspect Cloud Audit Logs for MIG\n    errors.\n  - Compute Viewer (`roles\u002Fcompute.viewer`): Check MIG stability (`isStable`)\n    and instance progress.\n  - Kubernetes Engine Viewer (`roles\u002Fcontainer.viewer`): Inspect Slice custom\n    resources (`slices.accelerator.gke.io`), nodes, and cluster operations.\n- **Documentation**:\n  - [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n    (Sections: \"Before you begin\", \"Create a Slice custom resource\", \"Monitor\n    the status of the Slice custom resource\", \"Verify the status of the nodes\n    and the partitions\", \"Upgrade your node pools\")\n  - [Install kubectl and configure cluster access](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcluster-access-for-kubectl.md.txt)\n    (Sections: \"Install kubectl\", \"Install required plugins\", \"Store cluster\n    information for kubectl\")\n  - [Add and manage node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-pools.md.txt)\n    (Sections: \"View node pools in a Standard cluster\")\n  - [View information about MIGs and managed instances](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt)\n    (Sections: \"Check whether a MIG is stable\", \"Check the status of managed\n    instances\", \"List instance errors\")\n  - [Automatically apply VM configuration updates in a MIG](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Frolling-out-updates-to-managed-instance-groups.md.txt)\n    (Sections: \"Verify whether an update rollout is complete\")\n  - [Manually upgrade a cluster's control plane or node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt)\n    (Sections: \"Check node pool upgrade status\", \"Cancel a node pool upgrade\",\n    \"Resume a node pool upgrade\", \"Roll back a node pool upgrade\")\n  - [Auto-repair nodes](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-auto-repair.md.txt)\n    (Sections: \"Get information about recent automated repair events\")\n  - [Troubleshoot GKE Standard node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Fnode-pools.md.txt)\n    (Sections: \"Issue: Node pool creation fails due to insufficient resources\")\n  - [Troubleshoot TPUs in GKE](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Ftpus.md.txt)\n    (Sections: \"Insufficient quota to satisfy the TPU request\", \"Insufficient\n    TPU resources to satisfy the TPU request\")\n  - [REST Resource: projects.locations.clusters.nodePools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Freference\u002Frest\u002Fv1\u002Fprojects.locations.clusters.nodePools.md.txt)\n    (Sections: \"Resource: NodePool\")\n  - [Schedule dynamic slices with Kueue and TAS](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fuse-gke-dynamic-slicing.md.txt)\n    (Sections: \"Monitor the status of the slice\")\n  - [About TPUs in GKE](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fconcepts\u002Ftpus.md.txt)\n  - [Get support](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fgetting-support.md.txt)\n    (Sections: \"Before you contact support\")\n\n> **Read-only rule**: Run read-only diagnostic commands only. Never drain,\n> delete, or re-create nodes, or run any other command that changes the cluster.\n> Give the user any fix to apply themselves.\n\nWhen you recommend a fix, link the doc section that describes it.\n\n---\n\n## Diagnostic workflow\n\n### Step 0: Collect context and set the investigation window `[Low Risk]`\n\nCollect the necessary contextual parameters from the user prompt or environment:\n- `{project_id}`, `{cluster_name}`, `{location}`, `{nodepool_name}`, and\n  `{issue_time}`.\n- `{mig_name}` and `{zone}`: Name and zone of the managed instance group that\n  backs `{nodepool_name}`, from the node pool's `instanceGroupUrls` field (see\n  [View node pools in a Standard cluster](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-pools.md.txt)\n  and\n  [Resource: NodePool](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Freference\u002Frest\u002Fv1\u002Fprojects.locations.clusters.nodePools.md.txt)).\n  If `{nodepool_name}` or `{mig_name}` isn't already known from a failing\n  `Slice`, find the affected partition, nodes, and backing MIG by following\n  [Verify the status of the nodes and the partitions](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt).\n- **Time window**: By default, query a 60-minute window `[{issue_time} - 30m,\n  {issue_time} + 30m]` (`{start_time}` to `{end_time}`).\n\n---\n\n### Step 1: Detect slice creation failures and MIG errors `[Low Risk]`\n\n1. **Inspect Slice status and partition nodes**: Check the `Slice` custom\n   resource `Status.Conditions` for a `SliceCreationFailed` status reason and\n   identify the affected partitions, nodes, and `{mig_name}` by following the\n   \"Monitor the status of the Slice custom resource\" and \"Verify the status of\n   the nodes and the partitions\" sections of\n   [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt),\n   and\n   [Monitor the status of the slice](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fuse-gke-dynamic-slicing.md.txt).\n2. **Query Cloud Logging for MIG errors**: Once `{mig_name}` is identified (or\n   by narrowing the results to `{mig_name}` once known), run this Cloud Logging\n   query to detect errors on the backing instance group manager across\n   `[{start_time}, {end_time}]`:\n   ```\n   resource.type=\"gce_instance_group_manager\"\n   resource.labels.instance_group_manager_name=\"{mig_name}\"\n   severity>=ERROR\n   timestamp >= \"{start_time}\" AND timestamp \u003C= \"{end_time}\"\n   ```\n- **Findings**:\n  - If the `Slice` status reports `SliceCreationFailed` or the logs show\n    instance group errors, proceed to Step 2.\n  - If no error logs match and the TPU `Slice` status is `ACTIVE`, rule out MIG\n    instability and check workload configuration.\n\n---\n\n### Step 2: Check MIG stability (`status.isStable`) `[Low Risk]`\n\nFollow\n[Check whether a MIG is stable](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt)\nto inspect the stability (`status.isStable`) and version target status\n(`status.versionTarget.isReached`) of `{mig_name}`:\n\n- **What the fields mean**:\n  - `status.isStable: false`: Changes are active or pending, or the MIG itself\n    is being modified. Proceed to Step 3.\n  - `status.versionTarget.isReached: false`: At least one instance isn't running\n    the target version yet (see\n    [Automatically apply VM configuration updates in a MIG](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Frolling-out-updates-to-managed-instance-groups.md.txt)).\n    Proceed to Step 3.\n  - `status.isStable: true` and `status.versionTarget.isReached: true`: No\n    instances are undergoing or scheduled for changes (`currentAction` is `NONE`\n    for all instances), and the MIG itself isn't being modified. This rules out\n    MIG instability. If the `Slice` is still in `SliceCreationFailed`, hand off\n    to `gke-ai-troubleshooting-tpu-dynamic-slices-monitoring`, or follow the\n    \"Create a Slice custom resource\" and \"Verify the status of the nodes and the\n    partitions\" sections of\n    [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt).\n\n---\n\n### Step 3: Find failed or stalled instance operations `[Low Risk]`\n\nDirect the user to the \"Check the status of managed instances\" and \"List\ninstance errors\" sections of\n[View information about MIGs and managed instances](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt)\n(include both section names and the document title) to inspect individual\ninstance states (`currentAction` and `instanceStatus`) and list the most recent\nerrors in `{mig_name}`:\n\n- If the errors show capacity or quota failures such as\n  `ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS` or `QUOTA_EXCEEDED`, go to Step 5,\n  item 2.\n- Otherwise, proceed to Step 4 to check for node pool upgrade or auto-repair\n  operations.\n\n---\n\n### Step 4: Check node pool operations `[Low Risk]`\n\nA MIG that is still changing instances can be the result of a node pool upgrade\nor repair:\n\n1. **Check node pool upgrades**: Follow\n   [Check node pool upgrade status](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt)\n   to list the cluster operations and find upgrade operations targeting\n   `{nodepool_name}` in `[{start_time}, {end_time}]`. Also review\n   [Upgrade your node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n   for dynamic slicing upgrade requirements (required surge settings and\n   deleting active super-slices before upgrading).\n   - If an upgrade operation is still running, go to Step 5, item 1 or item 3.\n   - If an upgrade operation was cancelled, failed, or is incomplete, go to Step\n     5, item 4.\n2. **Check automated node repairs**: Follow\n   [Get information about recent automated repair events](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnode-auto-repair.md.txt)\n   to check for repair operations on `{nodepool_name}`.\n   - If a node auto-repair operation is running, go to Step 5, item 1.\n3. **If no operation or error explains the unstable MIG**: Go to Step 5, item 5\n   to contact Cloud Customer Care.\n\n---\n\n### Step 5: Resolution `[High Risk]`\n\n> **Guardrail**: Don't modify GKE-managed instance groups or VMs directly\n> through Compute Engine. Manage node pools through GKE.\n\n1. **Wait for an ongoing update or auto-repair to finish**: If a node pool\n   upgrade or automated repair is still making progress, the user can wait until\n   the MIG is stable (`status.isStable: true`) by following\n   [Check whether a MIG is stable](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt).\n2. **Resolve capacity or quota errors**: When Step 3 shows\n   `ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS` or `QUOTA_EXCEEDED`, rolling back\n   an upgrade won't resolve the shortage. Follow\n   [Issue: Node pool creation fails due to insufficient resources](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Fnode-pools.md.txt)\n   and the \"Insufficient quota to satisfy the TPU request\" and \"Insufficient TPU\n   resources to satisfy the TPU request\" sections of\n   [Troubleshoot TPUs in GKE](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Ftroubleshooting\u002Ftpus.md.txt).\n3. **Cancel an in-progress node pool upgrade**: If the user wants to stop an\n   upgrade that is still running, follow\n   [Cancel a node pool upgrade](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt).\n   For dynamic slicing node pools, also check\n   [Upgrade your node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n   for the required surge settings and deleting active super-slices before\n   upgrading.\n4. **Resume or roll back a cancelled, failed, or incomplete node pool upgrade**:\n   - Follow the \"Resume a node pool upgrade\" or \"Roll back a node pool upgrade\"\n     sections of\n     [Manually upgrade a cluster's control plane or node pools](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fupgrading-a-cluster.md.txt).\n     As documented there, rollback applies if an in-progress upgrade was\n     cancelled, the upgrade failed, or the upgrade is incomplete due to a\n     maintenance window timing out (you can't roll back node pools once they\n     have been successfully upgraded); alternatively, a cancelled or failed,\n     partially completed upgrade can be resumed.\n   - Afterwards, verify that the MIG is stable by following\n     [Check whether a MIG is stable](https:\u002F\u002Fdocs.cloud.google.com\u002Fcompute\u002Fdocs\u002Finstance-groups\u002Fgetting-info-about-migs.md.txt).\n5. **Escalate unexplained MIG instability**: If no node pool upgrade, repair\n   operation, or capacity\u002Fquota error explains why `{mig_name}` remains\n   unstable, direct the user to Cloud Customer Care by following\n   [Get support](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fgetting-support.md.txt).\n6. **Verify node pool and slice recovery**: After the instance group is stable\n   (`status.isStable: true`), follow the \"Monitor the status of the Slice custom\n   resource\" and \"Create a Slice custom resource\" sections of\n   [Use dynamic slicing with a custom scheduler](https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fcreate-dynamic-slices.md.txt)\n   to verify that the `Slice` reaches the `ACTIVE` state. If the `Slice` stays\n   in `SliceCreationFailed` after the MIG stabilizes, check whether the retry\n   annotation documented in \"Create a Slice custom resource\" is set on the\n   `Slice`.\n",{"name":5,"metadata":44,"description":7},{"version":45,"category":46},"1.0.1","Containers","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Fgke-ai-troubleshooting-tpu-slice-mig-stuck-updating",2005,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 01:51:35",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add google\u002Fskills --skill gke-ai-troubleshooting-tpu-slice-mig-stuck-updating",{"tool":62,"command":63},"bunx","bunx skills add google\u002Fskills --skill gke-ai-troubleshooting-tpu-slice-mig-stuck-updating",{"tool":65,"command":66},"pnpm","pnpm dlx skills add google\u002Fskills --skill gke-ai-troubleshooting-tpu-slice-mig-stuck-updating","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-ai-troubleshooting-tpu-slice-mig-stuck-updating\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fattribution.md","REFERENCE","参考文档",2001,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-ai-troubleshooting-tpu-slice-mig-stuck-updating\u002Freferences\u002Fattribution.md",[77,115,146,175,202,226],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":39},"01M6998S2EZKD3GEJ7F943RZTE","sign-in-with-google-web","Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS \u002F `https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fclient`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React\u002FNext.js\u002FAngular\u002FHTML, verifying ID tokens on backend runtimes (Python\u002FNode.js\u002FGo\u002FJava), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fintermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android\u002FiOS native Credential Manager.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fsign-in-with-google-web\u002FSKILL.md",[83,88],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000010","后端与接口",[9,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114],"sign in with google web","sign","with","web","android","go","security","google workspace","google cloud","implement","policy","python","implementing","react","iam","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":130,"publishedAt":39},"01M6998PHPDCAD684VW5WRG83D","dpop-adoption","Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com\u002Ftoken. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM \u002F service account authentication.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fdpop-adoption\u002FSKILL.md",[121,122,125],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[131,132,9,100,133,134,135,136,137,138,106,139,140,141,142,143,144,111,114,145,25],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":158,"publishedAt":39},"01M6998M72TC73EEAQH4XC7EXW","retrieving-developer-knowledge","Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI\u002FGemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fretrieving-developer-knowledge\u002FSKILL.md",[152,153,156,157],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":154,"categoryName":155,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[159,160,161,162,100,163,164,165,166,167,168,169,170,25,171,172,173,106,174,107],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":39},"01M6998J2CZEXS9BES9S3WWFKC","migrate-to-rust","Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure\u002Ffix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fmigrate-to-rust\u002FSKILL.md",[],[182,183,184,185,186,187,188,189,103,190,191,192,193,194,195,168,196,197,198,25,199,200,173,201],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":211,"publishedAt":39},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills","Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[208,209,210],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[9,212,213,214,215,145,216,217,218,219,220,135,221,222,223,169,35,224,25,225,172],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","database","candidate",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":234,"publishedAt":39},"01M6998DWNHTH0BS6W1CY8ZXMP","workload-manager-basics","Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fworkload-manager-basics\u002FSKILL.md",[232,233],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},[235,236,110,237,9,162,238,100,163,239,240,241,242,25,243,172,106,244,245,246,247],"workload manager basics","workload","basics","cli","review","vpc","resources","inspect","you","create","libraries","server","run"]