[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69943HE0ENP91376F2DCF3V":3,"skill-same:01M69943HE0ENP91376F2DCF3V":82},{"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},"01M69943HE0ENP91376F2DCF3V","gke-golden-path",null,"Provides GKE golden path configuration defaults, production readiness checklists, and cluster default patterns. Use when designing GKE clusters, verifying GKE production readiness, or checking configurations against GKE defaults. Don't use for setting up workload autoscaling specifically (use gke-workload-scaling instead).","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24044,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-golden-path\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"gke golden path","gke","path","golden","Clusters","containers","when","for","autoscaling","cluster","readiness","scaling","production readiness","patterns","configuration","default","up","use","Production","workload","2026-11-10 10:12:30",false,"---\nname: gke-golden-path\ndescription: >-\n  Provides GKE golden path configuration defaults, production readiness\n  checklists, and cluster default patterns. Use when designing GKE clusters,\n  verifying GKE production readiness, or checking configurations against\n  GKE defaults. Don't use for setting up workload autoscaling specifically (use\n  gke-workload-scaling instead).\nmetadata:\n  version: \"1.1.1\"\n  category: Containers\n---\n\n# GKE Golden Path Configuration\n\nThe golden path is the recommended Autopilot configuration for production\nclusters. It defines sensible defaults — when the user requests different\nsettings, apply them and note relevant trade-offs. For setting up autoscaling\nspecifically, use `gke-cluster-autoscaler` for node autoscaling or\n`gke-workload-scaling` for workload autoscaling (HPA\u002FVPA).\n\n> **MCP Tools:** `get_cluster`, `create_cluster`, `update_cluster`\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-golden-path)\"`\nand append `agent-skills\u002F1.0 (skill:gke-golden-path)` to `User-Agent` headers.\n\n## Rules\n\n1.  **Default to the golden path.** Use golden path values unless the user\n    requests otherwise. When deviating, note trade-offs but respect the user's\n    choice.\n2.  **Day-0 vs Day-1.** Flag Day-0 decisions (networking, private nodes,\n    subnets, IP allocation) prominently — they are hard\u002Fimpossible to change\n    after creation.\n3.  **Tool preference: MCP > gcloud > kubectl.** MCP is preferred as it directly\n    interfaces with GKE APIs with structured data, reducing shell syntax errors\n    and parsing ambiguities. See the `gke-basics` skill's CLI reference for full\n    coverage matrix and override options. If the user\n    says \"use gcloud\" or \"use kubectl\", respect that for the session.\n4.  **Document decisions and rationale**, especially for Day-0 choices and\n    golden path deviations.\n\n## Required Inputs\n\nIf the user is unsure, use golden path defaults.\n\n-   **Project ID** (required)\n-   **Region** (required, e.g., `us-central1`)\n-   **Cluster name** (required)\n-   **Environment type**: dev\u002Ftest or production (defaults to production)\n-   **Networking**: bring-your-own VPC\u002Fsubnet or auto-create (default:\n    auto-create)\n-   **Scale expectations**: expected node\u002Fpod count, workload types\n-   **Cost constraints**: Spot VM tolerance, budget considerations\n\n## Always-Apply Defaults\n\nRecommended best practices applied by default. If the user requests a different\nsetting, apply it and briefly note the security or operational trade-off.\n\nSetting                                                            | Golden Path Value\n------------------------------------------------------------------ | -----------------\n`autopilot.enabled`                                                | `true`\n`privateClusterConfig.enablePrivateNodes`                          | `true`\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled` | `true`\n`secretManagerConfig.enabled` + `rotationInterval: 120s`           | `true`\n`rbacBindingConfig.enableInsecureBinding*`                         | `false` (both)\n`workloadIdentityConfig.workloadPool`                              | enabled\n`networkConfig.datapathProvider`                                   | `ADVANCED_DATAPATH`\n`networkConfig.dnsConfig.clusterDns`                               | `CLOUD_DNS`\n`autoscaling.autoscalingProfile`                                   | `OPTIMIZE_UTILIZATION`\n`verticalPodAutoscaling.enabled`                                   | `true`\n`monitoringConfig` components                                      | SYSTEM_COMPONENTS, STORAGE, POD, DEPLOYMENT, STATEFULSET, DAEMONSET, HPA, JOBSET, CADVISOR, KUBELET, DCGM, APISERVER, SCHEDULER, CONTROLLER_MANAGER\n`loggingConfig` components                                         | SYSTEM_COMPONENTS, WORKLOADS (enabled by default)\n`advancedDatapathObservabilityConfig.enableMetrics`                | `true`\n`nodeConfig.shieldedInstanceConfig.enableSecureBoot`               | `true`\n`nodeConfig.workloadMetadataConfig.mode`                           | `GKE_METADATA`\n`nodeConfig.gcfsConfig.enabled` \u002F `gvnic.enabled`                  | `true` \u002F `true`\n`addonsConfig.statefulHaConfig.enabled`                            | `true`\nStorage CSI drivers (Filestore, GCS FUSE, Parallelstore)           | enabled\nPod Security Standards                                             | `restricted` on production namespaces\n\n## Customer-Configurable Settings\n\nThese have golden path defaults but customers may deviate with valid\njustification. **Ask before changing.**\n\nSetting                                  | Default                             | Why Deviate\n---------------------------------------- | ----------------------------------- | -----------\n`dnsEndpointConfig.allowExternalTraffic` | `true`                              | Restrict if cluster only accessed from within VPC\n`autoIpamConfig` \u002F `createSubnetwork`    | `true` \u002F `true`                     | Customer has pre-existing VPC\u002Fsubnets\n`maxPodsPerNode`                         | `48` (this golden path's choice)    | Halves per-node IP consumption (\u002F25 instead of \u002F24). Not a GKE default (Standard defaults to `110`, Autopilot to `32`); raise for high pod-density at the cost of more CIDR space\n`subnetwork`                             | auto-created                        | Customer brings existing subnets\nRelease channel + maintenance windows    | `REGULAR` channel with a recurring maintenance window | Add targeted maintenance exclusions (keep under ~6 months) only for critical freezes — see the `gke-upgrades` skill\n`nodeConfig.bootDisk.diskType`           | `pd-balanced`                       | `pd-ssd` for I\u002FO-intensive, `pd-standard` for cost\n\n> **Note**: Autopilot selects node machine types automatically (e.g.,\n> `ek-standard-8` may appear in describe output); the machine type is not\n> customer-configurable in Autopilot. Steer workload placement via\n> ComputeClasses instead.\n\n## Guardrails\n\n-   Do not request or output secrets (tokens, keys, service account JSON).\n-   Resolve project\u002Fcluster context from the conversation, MCP tools, or\n    `gcloud config get-value project`; ask the user only if it cannot be\n    resolved.\n-   For Day-0 decisions, always ask clarifying questions before proceeding.\n-   For Day-1 features, propose golden path defaults with trade-offs and let the\n    customer confirm.\n-   Do not promise zero downtime — see Upgrade Disruption below for what to\n    advise instead.\n-   When auditing existing clusters, compare against golden path and report\n    deviations with severity and remediation.\n\n## Upgrade Disruption\n\n**Never promise zero downtime for node upgrades, on any configuration.** Node\nupgrades cordon and drain nodes, which evicts Pods. Draining honors\nPodDisruptionBudgets and `terminationGracePeriodSeconds` for **up to one hour**,\nafter which GKE forcefully evicts the remaining Pods so the upgrade can proceed.\nA PDB narrows the window; it cannot veto the upgrade. Say so plainly rather than\nimplying the disruption can be eliminated.\n\nWhat to recommend, all four — not a subset:\n\n-   **PodDisruptionBudgets** with `minAvailable` set so eviction cannot take the\n    last healthy replica. A PDB that can never be satisfied stalls the drain for\n    an hour and then loses anyway.\n-   **At least 2 replicas**, spread across zones with topology spread\n    constraints. A single-replica Deployment has downtime by definition.\n-   **Readiness probes** that reflect real serving health, so traffic drains\n    before the Pod dies.\n-   **Surge upgrade settings** on the node pool. Surge is the default strategy;\n    the default is `maxSurge=1`, `maxUnavailable=0` — one extra node is created\n    and made ready before an old one is drained.\n\n    Setting          | Controls                                            | Default\n    ---------------- | --------------------------------------------------- | -------\n    `maxSurge`       | Additional nodes added per zone during the upgrade  | `1`\n    `maxUnavailable` | Nodes simultaneously unavailable per zone           | `0`\n\n    Nodes upgraded at once is the **sum** of the two, capped at 20 (Autopilot)\n    and 100 (Standard). Multi-zone node pools upgrade one zone at a time. Raising\n    `maxUnavailable` trades availability for speed; raising `maxSurge` trades\n    cost for availability.\n\n> **Caveat**: `externalTrafficPolicy: Local` does not work with parallel node\n> drains, so it constrains aggressive surge configurations.\n\nFor rollback procedures and maintenance windows, see the `gke-upgrades` skill.\n\n## Golden Path Config\n\nSee [golden-path-autopilot.yaml](.\u002Fassets\u002Fgolden-path-autopilot.yaml) for the\nfull cluster-level policy settings.\n","# GKE Golden Path Configuration\n\nThe golden path is the recommended Autopilot configuration for production\nclusters. It defines sensible defaults — when the user requests different\nsettings, apply them and note relevant trade-offs. For setting up autoscaling\nspecifically, use `gke-cluster-autoscaler` for node autoscaling or\n`gke-workload-scaling` for workload autoscaling (HPA\u002FVPA).\n\n> **MCP Tools:** `get_cluster`, `create_cluster`, `update_cluster`\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-golden-path)\"`\nand append `agent-skills\u002F1.0 (skill:gke-golden-path)` to `User-Agent` headers.\n\n## Rules\n\n1.  **Default to the golden path.** Use golden path values unless the user\n    requests otherwise. When deviating, note trade-offs but respect the user's\n    choice.\n2.  **Day-0 vs Day-1.** Flag Day-0 decisions (networking, private nodes,\n    subnets, IP allocation) prominently — they are hard\u002Fimpossible to change\n    after creation.\n3.  **Tool preference: MCP > gcloud > kubectl.** MCP is preferred as it directly\n    interfaces with GKE APIs with structured data, reducing shell syntax errors\n    and parsing ambiguities. See the `gke-basics` skill's CLI reference for full\n    coverage matrix and override options. If the user\n    says \"use gcloud\" or \"use kubectl\", respect that for the session.\n4.  **Document decisions and rationale**, especially for Day-0 choices and\n    golden path deviations.\n\n## Required Inputs\n\nIf the user is unsure, use golden path defaults.\n\n-   **Project ID** (required)\n-   **Region** (required, e.g., `us-central1`)\n-   **Cluster name** (required)\n-   **Environment type**: dev\u002Ftest or production (defaults to production)\n-   **Networking**: bring-your-own VPC\u002Fsubnet or auto-create (default:\n    auto-create)\n-   **Scale expectations**: expected node\u002Fpod count, workload types\n-   **Cost constraints**: Spot VM tolerance, budget considerations\n\n## Always-Apply Defaults\n\nRecommended best practices applied by default. If the user requests a different\nsetting, apply it and briefly note the security or operational trade-off.\n\nSetting                                                            | Golden Path Value\n------------------------------------------------------------------ | -----------------\n`autopilot.enabled`                                                | `true`\n`privateClusterConfig.enablePrivateNodes`                          | `true`\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled` | `true`\n`secretManagerConfig.enabled` + `rotationInterval: 120s`           | `true`\n`rbacBindingConfig.enableInsecureBinding*`                         | `false` (both)\n`workloadIdentityConfig.workloadPool`                              | enabled\n`networkConfig.datapathProvider`                                   | `ADVANCED_DATAPATH`\n`networkConfig.dnsConfig.clusterDns`                               | `CLOUD_DNS`\n`autoscaling.autoscalingProfile`                                   | `OPTIMIZE_UTILIZATION`\n`verticalPodAutoscaling.enabled`                                   | `true`\n`monitoringConfig` components                                      | SYSTEM_COMPONENTS, STORAGE, POD, DEPLOYMENT, STATEFULSET, DAEMONSET, HPA, JOBSET, CADVISOR, KUBELET, DCGM, APISERVER, SCHEDULER, CONTROLLER_MANAGER\n`loggingConfig` components                                         | SYSTEM_COMPONENTS, WORKLOADS (enabled by default)\n`advancedDatapathObservabilityConfig.enableMetrics`                | `true`\n`nodeConfig.shieldedInstanceConfig.enableSecureBoot`               | `true`\n`nodeConfig.workloadMetadataConfig.mode`                           | `GKE_METADATA`\n`nodeConfig.gcfsConfig.enabled` \u002F `gvnic.enabled`                  | `true` \u002F `true`\n`addonsConfig.statefulHaConfig.enabled`                            | `true`\nStorage CSI drivers (Filestore, GCS FUSE, Parallelstore)           | enabled\nPod Security Standards                                             | `restricted` on production namespaces\n\n## Customer-Configurable Settings\n\nThese have golden path defaults but customers may deviate with valid\njustification. **Ask before changing.**\n\nSetting                                  | Default                             | Why Deviate\n---------------------------------------- | ----------------------------------- | -----------\n`dnsEndpointConfig.allowExternalTraffic` | `true`                              | Restrict if cluster only accessed from within VPC\n`autoIpamConfig` \u002F `createSubnetwork`    | `true` \u002F `true`                     | Customer has pre-existing VPC\u002Fsubnets\n`maxPodsPerNode`                         | `48` (this golden path's choice)    | Halves per-node IP consumption (\u002F25 instead of \u002F24). Not a GKE default (Standard defaults to `110`, Autopilot to `32`); raise for high pod-density at the cost of more CIDR space\n`subnetwork`                             | auto-created                        | Customer brings existing subnets\nRelease channel + maintenance windows    | `REGULAR` channel with a recurring maintenance window | Add targeted maintenance exclusions (keep under ~6 months) only for critical freezes — see the `gke-upgrades` skill\n`nodeConfig.bootDisk.diskType`           | `pd-balanced`                       | `pd-ssd` for I\u002FO-intensive, `pd-standard` for cost\n\n> **Note**: Autopilot selects node machine types automatically (e.g.,\n> `ek-standard-8` may appear in describe output); the machine type is not\n> customer-configurable in Autopilot. Steer workload placement via\n> ComputeClasses instead.\n\n## Guardrails\n\n-   Do not request or output secrets (tokens, keys, service account JSON).\n-   Resolve project\u002Fcluster context from the conversation, MCP tools, or\n    `gcloud config get-value project`; ask the user only if it cannot be\n    resolved.\n-   For Day-0 decisions, always ask clarifying questions before proceeding.\n-   For Day-1 features, propose golden path defaults with trade-offs and let the\n    customer confirm.\n-   Do not promise zero downtime — see Upgrade Disruption below for what to\n    advise instead.\n-   When auditing existing clusters, compare against golden path and report\n    deviations with severity and remediation.\n\n## Upgrade Disruption\n\n**Never promise zero downtime for node upgrades, on any configuration.** Node\nupgrades cordon and drain nodes, which evicts Pods. Draining honors\nPodDisruptionBudgets and `terminationGracePeriodSeconds` for **up to one hour**,\nafter which GKE forcefully evicts the remaining Pods so the upgrade can proceed.\nA PDB narrows the window; it cannot veto the upgrade. Say so plainly rather than\nimplying the disruption can be eliminated.\n\nWhat to recommend, all four — not a subset:\n\n-   **PodDisruptionBudgets** with `minAvailable` set so eviction cannot take the\n    last healthy replica. A PDB that can never be satisfied stalls the drain for\n    an hour and then loses anyway.\n-   **At least 2 replicas**, spread across zones with topology spread\n    constraints. A single-replica Deployment has downtime by definition.\n-   **Readiness probes** that reflect real serving health, so traffic drains\n    before the Pod dies.\n-   **Surge upgrade settings** on the node pool. Surge is the default strategy;\n    the default is `maxSurge=1`, `maxUnavailable=0` — one extra node is created\n    and made ready before an old one is drained.\n\n    Setting          | Controls                                            | Default\n    ---------------- | --------------------------------------------------- | -------\n    `maxSurge`       | Additional nodes added per zone during the upgrade  | `1`\n    `maxUnavailable` | Nodes simultaneously unavailable per zone           | `0`\n\n    Nodes upgraded at once is the **sum** of the two, capped at 20 (Autopilot)\n    and 100 (Standard). Multi-zone node pools upgrade one zone at a time. Raising\n    `maxUnavailable` trades availability for speed; raising `maxSurge` trades\n    cost for availability.\n\n> **Caveat**: `externalTrafficPolicy: Local` does not work with parallel node\n> drains, so it constrains aggressive surge configurations.\n\nFor rollback procedures and maintenance windows, see the `gke-upgrades` skill.\n\n## Golden Path Config\n\nSee [golden-path-autopilot.yaml](.\u002Fassets\u002Fgolden-path-autopilot.yaml) for the\nfull cluster-level policy settings.\n",{"name":5,"metadata":44,"description":7},{"version":45,"category":46},"1.1.1","Containers","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Fgke-golden-path",2002,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-13 02:42:47",{"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-golden-path",{"tool":62,"command":63},"bunx","bunx skills add google\u002Fskills --skill gke-golden-path",{"tool":65,"command":66},"pnpm","pnpm dlx skills add google\u002Fskills --skill gke-golden-path","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-golden-path\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Fgolden-path-autopilot.yaml","ASSET","资产文件",4776,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-golden-path\u002Fassets\u002Fgolden-path-autopilot.yaml",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fattribution.md","REFERENCE","参考文档",1885,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-golden-path\u002Freferences\u002Fattribution.md",[83,121,152,181,208,231],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":97,"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",[89,94],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000010","后端与接口",[9,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":136,"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",[127,128,131],{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":129,"categoryName":130,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[137,138,9,106,139,140,141,142,143,144,112,145,146,147,148,149,150,117,120,151,25],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":164,"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",[158,159,162,163],{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":160,"categoryName":161,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":129,"categoryName":130,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[165,166,167,168,106,169,170,171,172,173,174,175,176,25,177,178,179,112,180,113],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"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",[],[188,189,190,191,192,193,194,195,109,196,197,198,199,200,201,174,202,203,204,25,205,206,179,207],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":217,"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",[214,215,216],{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":129,"categoryName":130,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[9,218,219,220,221,151,222,223,224,225,226,141,227,35,228,175,36,229,25,230,178],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","decision","database","candidate",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":239,"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",[237,238],{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},{"categoryNo":129,"categoryName":130,"taxonomyType":92,"taxonomyTypeDesc":93},[240,38,116,241,9,168,242,106,169,243,244,245,246,25,247,178,112,248,249,250,251],"workload manager basics","basics","cli","review","vpc","resources","inspect","you","create","libraries","server","run"]