What problem does it solve? When a GKE dynamic TPU slice fails to form with a SliceCreationFailed status, determining whether the conflict is caused by partition overlap requires manual investigation across multiple Kubernetes resources and Cloud Monitoring metrics. This Skill automates the diagnostic workflow and guides you to the resolution. ## Core Features & Use Cases - Confirm Failure Root Cause: Verify SliceCreationFailed status and rule out unrelated causes (missing nodes, topology mismatches, unhealthy partitions). - Identify Conflicting Slices: Cross-reference partition IDs across all Slice custom resources and query Cloud Monitoring metrics to find which slice is using the same nodes. - Route to Resolution: Determine whether Kueue manages the conflicting slice and provide appropriate remediation (wait for release, select alternative partitions, or re-create with retry annotations). - Use Case: Your TPU slice creation is stuck in SliceCreationFailed. Run this Skill to confirm partition overlap, identify the conflicting slice, and determine whether to wait for it to release or select different partitions. ## Quick Start Describe the failing Slice custom resource and provide the cluster name, location, and project ID so I can check partition availability and identify which other slice is blocking these nodes.