[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6994MHQS3KA8D9Z1160T3RA":3,"skill-same:01M6994MHQS3KA8D9Z1160T3RA":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},"01M6994MHQS3KA8D9Z1160T3RA","gke-reliability",null,"Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery and cluster backups (use gke-backup-dr).","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-reliability\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"gke reliability","reliability","gke","up","when","for","manifests","cluster","readiness","k8s","disaster recovery","generation","yaml","containers","use","health","recovery","backup","manifest","workload","2026-11-10 10:12:30",false,"---\nname: gke-reliability\ndescription: >-\n  Improves GKE workload reliability, using PDBs, health probes, and topology\n  spread constraints. Use when configuring GKE workload reliability, setting up\n  PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't\n  use for generating K8s YAML manifests (use gke-manifest-generation) or\n  disaster recovery and cluster backups (use gke-backup-dr).\nmetadata:\n  version: \"1.0.2\"\n  category: Containers\n---\n\n# GKE Reliability\n\n> **Routing Note:** To generate Kubernetes YAML manifests (`Deployment`, `StatefulSet`, `Service`, `ConfigMap`, `HTTPRoute`, `PodDisruptionBudget`), open `gke-manifest-generation\u002FSKILL.md`.\n\nThis reference covers high availability and reliability configuration for GKE\nclusters and workloads.\n\n> **MCP Tools:** `get_cluster`, `get_k8s_resource`, `describe_k8s_resource`,\n> `apply_k8s_manifest`, `list_k8s_events`\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-reliability)\"`\nand append `agent-skills\u002F1.0 (skill:gke-reliability)` to `User-Agent` headers.\n\n## Golden Path Reliability Defaults\n\n| Setting          | Golden Path Value     | Notes                            |\n| ---------------- | --------------------- | -------------------------------- |\n| Cluster type     | Regional (4 zones:    | Control plane replicated across  |\n:                  : us-central1-a\u002Fb\u002Fc\u002Ff)  : zones                            :\n| Upgrade strategy | SURGE (`maxSurge: 1`) | Rolling upgrades with extra      |\n:                  :                       : capacity                         :\n| Auto-repair      | `true`                | Unhealthy nodes replaced         |\n:                  :                       : automatically                    :\n| Auto-upgrade     | `true`                | Nodes follow control plane       |\n:                  :                       : version                          :\n| Release channel  | REGULAR               | Balanced freshness and stability |\n| Stateful HA      | Enabled               | Leader election for stateful     |\n:                  :                       : workloads                        :\n\n## Workflows\n\n### 1. Verify Cluster High Availability\n\n```\n# MCP (preferred)\nget_cluster(name=\"projects\u002F\u003CPROJECT>\u002Flocations\u002F\u003CREGION>\u002Fclusters\u002F\u003CCLUSTER>\",\n  readMask=\"location,locations,nodePools.locations\")\n\n# gcloud fallback\ngcloud container clusters describe \u003CCLUSTER> --region \u003CREGION> \\\n  --format=\"json(location, locations)\" \\\n  --quiet\n```\n\n-   If `location` is a region (e.g., `us-central1`), the control plane is\n    regional\n-   If `locations` has multiple entries, nodes span multiple zones\n\n### 2. Pod Disruption Budgets (PDBs)\n\nPDBs ensure minimum pod availability during voluntary disruptions (node\nupgrades, autoscaler scale-down).\n\n**Check existing PDBs:**\n\n```\n# MCP (preferred)\nget_k8s_resource(parent=\"...\", resourceType=\"poddisruptionbudget\")\n\n# kubectl fallback\nkubectl get pdb --all-namespaces\n```\n\n**Create PDB:**\n\n```yaml\napiVersion: policy\u002Fv1\nkind: PodDisruptionBudget\nmetadata:\n  name: my-app-pdb\n  namespace: default\nspec:\n  minAvailable: 2       # Or use maxUnavailable: 1\n  selector:\n    matchLabels:\n      app: my-app\n```\n\n> Every production Deployment with 2+ replicas should have a PDB.\n\n### 3. Health Probes\n\nEvery production container should have liveness and readiness probes. Startup\nprobes are recommended for slow-starting apps.\n\n**Check existing probes:**\n\n```\n# MCP (preferred)\ndescribe_k8s_resource(parent=\"...\", resourceType=\"deployment\", name=\"\u003CAPP>\", namespace=\"\u003CNS>\")\n\n# kubectl fallback\nkubectl get deployment \u003CAPP> -n \u003CNS> -o yaml | grep -E \"livenessProbe|readinessProbe|startupProbe\"\n```\n\n**Recommended probe configuration:**\n\n```yaml\nspec:\n  containers:\n  - name: app\n    livenessProbe:\n      httpGet:\n        path: \u002Fhealthz\n        port: 8080\n      initialDelaySeconds: 15\n      periodSeconds: 10\n      timeoutSeconds: 2\n      failureThreshold: 3\n    readinessProbe:\n      httpGet:\n        path: \u002Freadyz\n        port: 8080\n      initialDelaySeconds: 5\n      periodSeconds: 5\n      timeoutSeconds: 2\n      failureThreshold: 3\n    startupProbe:             # For slow-starting apps\n      httpGet:\n        path: \u002Fhealthz\n        port: 8080\n      initialDelaySeconds: 10\n      periodSeconds: 5\n      timeoutSeconds: 2\n      failureThreshold: 30    # 30 * 5s = 150s max startup time\n```\n\n-   **Readiness**: Determines when a pod can accept traffic\n-   **Liveness**: Determines when to restart a container\n-   **Startup**: Disables liveness\u002Freadiness until the app is ready (prevents\n    premature restarts)\n\n### 4. Graceful Shutdown\n\nEnsure applications handle `SIGTERM` and drain in-flight requests:\n\n```yaml\nspec:\n  terminationGracePeriodSeconds: 30    # Default; increase for long-running requests\n  containers:\n  - name: app\n    lifecycle:\n      preStop:\n        exec:\n          command: [\"\u002Fbin\u002Fsh\", \"-c\", \"sleep 5\"]  # Allow LB to deregister\n```\n\n### 5. Topology Spread Constraints\n\nDistribute pods across zones and nodes to survive failures:\n\n```yaml\nspec:\n  topologySpreadConstraints:\n  - maxSkew: 1\n    topologyKey: topology.kubernetes.io\u002Fzone\n    whenUnsatisfiable: DoNotSchedule\n    labelSelector:\n      matchLabels:\n        app: my-app\n  - maxSkew: 1\n    topologyKey: kubernetes.io\u002Fhostname\n    whenUnsatisfiable: ScheduleAnyway\n    labelSelector:\n      matchLabels:\n        app: my-app\n```\n\n-   **Zone spread** (`DoNotSchedule`): Hard requirement -- pods must be balanced\n    across zones\n-   **Node spread** (`ScheduleAnyway`): Best-effort -- prefer distribution but\n    don't block scheduling\n\n### 6. Replicas\n\n| Workload Type        | Minimum Replicas     | Reason                         |\n| -------------------- | -------------------- | ------------------------------ |\n| Stateless web\u002FAPI    | 2                    | Survive single pod\u002Fnode        |\n:                      :                      : failure                        :\n| Critical services    | 3                    | Survive zone failure with zone |\n:                      :                      : spread                         :\n| Stateful (databases) | 3 (with replication) | Application-level quorum       |\n| Batch\u002Fjobs           | 1                    | Ephemeral by nature            |\n\n## Best Practices & Production Guidelines\n\n1.  **Regional clusters for production**: Always use regional clusters to\n    survive zone failures.\n2.  **PDBs for everything**: Every production workload with 2+ replicas needs a\n    PodDisruptionBudget (PDB) to protect against voluntary disruptions.\n3.  **Probes with Explicit Timeouts**: Every production container must have both\n    liveness and readiness probes defined. **Always explicitly define\n    `initialDelaySeconds`, `periodSeconds`, and `timeoutSeconds`** for all\n    probes. Never rely on the Kubernetes default timeout of 1 second if your\n    application requires more, but always set a strict limit to prevent hanging\n    connections.\n4.  **Zone spreading**: Use topology spread constraints to distribute pods\n    across failure domains (zones and nodes).\n5.  **Graceful shutdown**: Handle `SIGTERM` and set appropriate\n    `terminationGracePeriodSeconds` with a `preStop` sleep hook to allow load\n    balancer deregistration.\n6.  **Maintenance windows**: Schedule upgrades during low-traffic periods (see\n    the `gke-upgrades` skill).\n","# GKE Reliability\n\n> **Routing Note:** To generate Kubernetes YAML manifests (`Deployment`, `StatefulSet`, `Service`, `ConfigMap`, `HTTPRoute`, `PodDisruptionBudget`), open `gke-manifest-generation\u002FSKILL.md`.\n\nThis reference covers high availability and reliability configuration for GKE\nclusters and workloads.\n\n> **MCP Tools:** `get_cluster`, `get_k8s_resource`, `describe_k8s_resource`,\n> `apply_k8s_manifest`, `list_k8s_events`\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-reliability)\"`\nand append `agent-skills\u002F1.0 (skill:gke-reliability)` to `User-Agent` headers.\n\n## Golden Path Reliability Defaults\n\n| Setting          | Golden Path Value     | Notes                            |\n| ---------------- | --------------------- | -------------------------------- |\n| Cluster type     | Regional (4 zones:    | Control plane replicated across  |\n:                  : us-central1-a\u002Fb\u002Fc\u002Ff)  : zones                            :\n| Upgrade strategy | SURGE (`maxSurge: 1`) | Rolling upgrades with extra      |\n:                  :                       : capacity                         :\n| Auto-repair      | `true`                | Unhealthy nodes replaced         |\n:                  :                       : automatically                    :\n| Auto-upgrade     | `true`                | Nodes follow control plane       |\n:                  :                       : version                          :\n| Release channel  | REGULAR               | Balanced freshness and stability |\n| Stateful HA      | Enabled               | Leader election for stateful     |\n:                  :                       : workloads                        :\n\n## Workflows\n\n### 1. Verify Cluster High Availability\n\n```\n# MCP (preferred)\nget_cluster(name=\"projects\u002F\u003CPROJECT>\u002Flocations\u002F\u003CREGION>\u002Fclusters\u002F\u003CCLUSTER>\",\n  readMask=\"location,locations,nodePools.locations\")\n\n# gcloud fallback\ngcloud container clusters describe \u003CCLUSTER> --region \u003CREGION> \\\n  --format=\"json(location, locations)\" \\\n  --quiet\n```\n\n-   If `location` is a region (e.g., `us-central1`), the control plane is\n    regional\n-   If `locations` has multiple entries, nodes span multiple zones\n\n### 2. Pod Disruption Budgets (PDBs)\n\nPDBs ensure minimum pod availability during voluntary disruptions (node\nupgrades, autoscaler scale-down).\n\n**Check existing PDBs:**\n\n```\n# MCP (preferred)\nget_k8s_resource(parent=\"...\", resourceType=\"poddisruptionbudget\")\n\n# kubectl fallback\nkubectl get pdb --all-namespaces\n```\n\n**Create PDB:**\n\n```yaml\napiVersion: policy\u002Fv1\nkind: PodDisruptionBudget\nmetadata:\n  name: my-app-pdb\n  namespace: default\nspec:\n  minAvailable: 2       # Or use maxUnavailable: 1\n  selector:\n    matchLabels:\n      app: my-app\n```\n\n> Every production Deployment with 2+ replicas should have a PDB.\n\n### 3. Health Probes\n\nEvery production container should have liveness and readiness probes. Startup\nprobes are recommended for slow-starting apps.\n\n**Check existing probes:**\n\n```\n# MCP (preferred)\ndescribe_k8s_resource(parent=\"...\", resourceType=\"deployment\", name=\"\u003CAPP>\", namespace=\"\u003CNS>\")\n\n# kubectl fallback\nkubectl get deployment \u003CAPP> -n \u003CNS> -o yaml | grep -E \"livenessProbe|readinessProbe|startupProbe\"\n```\n\n**Recommended probe configuration:**\n\n```yaml\nspec:\n  containers:\n  - name: app\n    livenessProbe:\n      httpGet:\n        path: \u002Fhealthz\n        port: 8080\n      initialDelaySeconds: 15\n      periodSeconds: 10\n      timeoutSeconds: 2\n      failureThreshold: 3\n    readinessProbe:\n      httpGet:\n        path: \u002Freadyz\n        port: 8080\n      initialDelaySeconds: 5\n      periodSeconds: 5\n      timeoutSeconds: 2\n      failureThreshold: 3\n    startupProbe:             # For slow-starting apps\n      httpGet:\n        path: \u002Fhealthz\n        port: 8080\n      initialDelaySeconds: 10\n      periodSeconds: 5\n      timeoutSeconds: 2\n      failureThreshold: 30    # 30 * 5s = 150s max startup time\n```\n\n-   **Readiness**: Determines when a pod can accept traffic\n-   **Liveness**: Determines when to restart a container\n-   **Startup**: Disables liveness\u002Freadiness until the app is ready (prevents\n    premature restarts)\n\n### 4. Graceful Shutdown\n\nEnsure applications handle `SIGTERM` and drain in-flight requests:\n\n```yaml\nspec:\n  terminationGracePeriodSeconds: 30    # Default; increase for long-running requests\n  containers:\n  - name: app\n    lifecycle:\n      preStop:\n        exec:\n          command: [\"\u002Fbin\u002Fsh\", \"-c\", \"sleep 5\"]  # Allow LB to deregister\n```\n\n### 5. Topology Spread Constraints\n\nDistribute pods across zones and nodes to survive failures:\n\n```yaml\nspec:\n  topologySpreadConstraints:\n  - maxSkew: 1\n    topologyKey: topology.kubernetes.io\u002Fzone\n    whenUnsatisfiable: DoNotSchedule\n    labelSelector:\n      matchLabels:\n        app: my-app\n  - maxSkew: 1\n    topologyKey: kubernetes.io\u002Fhostname\n    whenUnsatisfiable: ScheduleAnyway\n    labelSelector:\n      matchLabels:\n        app: my-app\n```\n\n-   **Zone spread** (`DoNotSchedule`): Hard requirement -- pods must be balanced\n    across zones\n-   **Node spread** (`ScheduleAnyway`): Best-effort -- prefer distribution but\n    don't block scheduling\n\n### 6. Replicas\n\n| Workload Type        | Minimum Replicas     | Reason                         |\n| -------------------- | -------------------- | ------------------------------ |\n| Stateless web\u002FAPI    | 2                    | Survive single pod\u002Fnode        |\n:                      :                      : failure                        :\n| Critical services    | 3                    | Survive zone failure with zone |\n:                      :                      : spread                         :\n| Stateful (databases) | 3 (with replication) | Application-level quorum       |\n| Batch\u002Fjobs           | 1                    | Ephemeral by nature            |\n\n## Best Practices & Production Guidelines\n\n1.  **Regional clusters for production**: Always use regional clusters to\n    survive zone failures.\n2.  **PDBs for everything**: Every production workload with 2+ replicas needs a\n    PodDisruptionBudget (PDB) to protect against voluntary disruptions.\n3.  **Probes with Explicit Timeouts**: Every production container must have both\n    liveness and readiness probes defined. **Always explicitly define\n    `initialDelaySeconds`, `periodSeconds`, and `timeoutSeconds`** for all\n    probes. Never rely on the Kubernetes default timeout of 1 second if your\n    application requires more, but always set a strict limit to prevent hanging\n    connections.\n4.  **Zone spreading**: Use topology spread constraints to distribute pods\n    across failure domains (zones and nodes).\n5.  **Graceful shutdown**: Handle `SIGTERM` and set appropriate\n    `terminationGracePeriodSeconds` with a `preStop` sleep hook to allow load\n    balancer deregistration.\n6.  **Maintenance windows**: Schedule upgrades during low-traffic periods (see\n    the `gke-upgrades` skill).\n",{"name":5,"metadata":44,"description":7},{"version":45,"category":46},"1.0.2","Containers","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Fgke-reliability",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-reliability",{"tool":62,"command":63},"bunx","bunx skills add google\u002Fskills --skill gke-reliability",{"tool":65,"command":66},"pnpm","pnpm dlx skills add google\u002Fskills --skill gke-reliability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-reliability\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fattribution.md","REFERENCE","参考文档",1885,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-reliability\u002Freferences\u002Fattribution.md",[77,115,146,175,202,225],{"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,23],"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,23,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,23,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,22,222,169,33,223,23,224,172],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","decision","database","candidate",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":233,"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",[231,232],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},[234,38,110,235,9,162,236,100,163,237,238,239,240,23,241,172,106,242,243,244,245],"workload manager basics","basics","cli","review","vpc","resources","inspect","you","create","libraries","server","run"]