[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6994AXWWPY3XT608392Y5N9":3,"skill-same:01M6994AXWWPY3XT608392Y5N9":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},"01M6994AXWWPY3XT608392Y5N9","gke-networking",null,"Plans, configures, and manages core GKE cluster networking. Covers private clusters, VPC-native configurations, DNS, node egress, Dataplane V2, and IP planning. Use when designing GKE networking layouts, configuring private clusters, setting up Dataplane V2, planning GKE IP ranges, or managing VPC- native cluster modes. Don't use for application ingress, load balancing, or service networking (use gke-service-networking instead).","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-networking\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"networking","gke","gke networking","load balancing","when","modes","for","load","native","cluster","plans","service","ip","up","use","node","vpc","dns","planning","core","2026-11-10 10:12:30",false,"---\nname: gke-networking\ndescription: >-\n  Plans, configures, and manages core GKE cluster networking. Covers private\n  clusters, VPC-native configurations, DNS, node egress, Dataplane V2, and\n  IP planning. Use when designing GKE networking layouts, configuring private\n  clusters, setting up Dataplane V2, planning GKE IP ranges, or managing VPC-\n  native cluster modes. Don't use for application ingress, load balancing, or\n  service networking (use gke-service-networking instead).\nmetadata:\n  version: \"1.0.1\"\n  category: Networking\n---\n\n# GKE Networking\n\nThis reference covers networking configuration for GKE clusters. The golden path\nenforces private, VPC-native clusters with Dataplane V2.\n\n> **MCP Tools:** `get_cluster`, `update_cluster`, `apply_k8s_manifest`,\n> `get_k8s_resource`\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-networking)\"`\nand append `agent-skills\u002F1.0 (skill:gke-networking)` to `User-Agent` headers.\n\n## Golden Path Networking Defaults\n\nSetting                                                              | Golden Path Value                  | Day-0\u002F1 | Notes\n-------------------------------------------------------------------- | ---------------------------------- | ------- | -----\n`privateClusterConfig.enablePrivateNodes`                            | `true`                             | Day-0   | Nodes have no public IPs\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled`   | `true`                             | Day-0   | Control plane only reachable via private endpoint or DNS\n`controlPlaneEndpointsConfig.dnsEndpointConfig.allowExternalTraffic` | `true`                             | Day-0   | Allows DNS-based access from outside VPC\n`networkConfig.datapathProvider`                                     | `ADVANCED_DATAPATH` (Dataplane V2) | Day-0   | eBPF-based, built-in Network Policy\n`networkConfig.dnsConfig.clusterDns`                                 | `CLOUD_DNS`                        | Day-0   | Managed DNS, more reliable than kube-dns\n`networkConfig.enableIntraNodeVisibility`                            | `true`                             | Day-1   | VPC Flow Logs for intra-node traffic\n`ipAllocationPolicy.autoIpamConfig.enabled`                          | `true`                             | Day-0   | Automatic IP range management\n`ipAllocationPolicy.createSubnetwork`                                | `true`                             | Day-0   | Auto-create dedicated subnet\n`defaultMaxPodsConstraint.maxPodsPerNode`                            | `48`                               | Day-0   | Conservative default; 110 for high density\n\n## Private Cluster Access Patterns\n\nThe golden path creates a private cluster. Users access it via:\n\n1.  **DNS endpoint (default)**: `allowExternalTraffic: true` enables access via\n    the cluster's DNS endpoint from outside the VPC. No VPN required.\n2.  **Private endpoint**: Direct access from within the VPC or via Cloud\n    VPN\u002FInterconnect.\n3.  **Authorized networks**: Add specific CIDRs to\n    `masterAuthorizedNetworksConfig` for IP-based access control.\n\n```bash\n# Access private cluster via DNS endpoint (golden path default)\ngcloud container clusters get-credentials {cluster_name} \\\n  --region {region} --dns-endpoint \\\n  --quiet\n\n# Access via private endpoint (from within VPC)\ngcloud container clusters get-credentials {cluster_name} \\\n  --region {region} --internal-ip \\\n  --quiet\n```\n\n## Bring-Your-Own VPC\u002FSubnet\n\nIf the customer has existing network infrastructure:\n\n```bash\ngcloud container clusters create-auto {cluster_name} \\\n  --region {region} \\\n  --network {vpc_name} \\\n  --subnetwork {subnet_name} \\\n  --cluster-secondary-range-name {pod_range} \\\n  --services-secondary-range-name {svc_range} \\\n  --enable-private-nodes \\\n  --enable-master-authorized-networks \\\n  --quiet\n```\n\n> **Day-0 Warning**: VPC, subnet, and IP ranges cannot be changed after cluster\n> creation.\n\n## VPC-Native Mode Benefits\n\nVPC-native clusters route traffic natively using GCP Alias IP ranges. Key\nbenefits to cover:\n\n1.  **Scalability**: Traffic routes natively inside the VPC, bypassing the need\n    for custom routes and avoiding custom route limit bottlenecks.\n2.  **Direct VPC Integration**: Direct resource integration across GCP networks\n    without complex bridging or routing tunnels.\n3.  **Avoiding IP Exhaustion**: Supports discontiguous IP ranges and optimizes\n    allocation, reducing the risk of exhausting subnet IP ranges.\n\n## IP Planning\n\n| Resource      | Golden Path  | Notes                                      |\n| ------------- | ------------ | ------------------------------------------ |\n| Pod CIDR      | `\u002F17` (auto) | ~32K pod IPs; size based on maxPodsPerNode |\n| Service CIDR  | `\u002F20` (auto) | ~4K service IPs                            |\n| Node subnet   | auto-created | \u002F20 recommended for growth                 |\n| Max pods\u002Fnode | 48           | Each node gets a \u002F25 pod range; set to 110 |\n:               :              : for \u002F24 per node                           :\n\n**Pod CIDR sizing rule of thumb:**\n\n-   `maxPodsPerNode=48` -> each node uses a `\u002F25` (128 IPs) from pod CIDR\n-   `maxPodsPerNode=110` -> each node uses a `\u002F24` (256 IPs) from pod CIDR\n-   Larger maxPodsPerNode = fewer nodes fit in a given CIDR\n\n## Egress\n\n-   Default: nodes use Cloud NAT for outbound internet access (private nodes\n    have no public IPs) to allow private nodes to reach the internet without\n    public IP exposure.\n-   For static egress IPs: configure Cloud NAT with manual IP allocation to\n    maintain a consistent source IP for external allowlists or partner\n    firewalls.\n-   For restricted egress: route through a firewall appliance via custom routes\n    to inspect and filter outbound traffic according to organization security\n    policies.\n\n## Network Policy\n\nDataplane V2 (golden path) provides built-in Network Policy enforcement — no\nadditional addon needed. Apply default-deny per namespace, then allow specific\nflows.\n\n> See the `gke-workload-security` skill for default-deny policy and the\n> `gke-multitenancy` skill for per-team allow policies.\n","# GKE Networking\n\nThis reference covers networking configuration for GKE clusters. The golden path\nenforces private, VPC-native clusters with Dataplane V2.\n\n> **MCP Tools:** `get_cluster`, `update_cluster`, `apply_k8s_manifest`,\n> `get_k8s_resource`\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-networking)\"`\nand append `agent-skills\u002F1.0 (skill:gke-networking)` to `User-Agent` headers.\n\n## Golden Path Networking Defaults\n\nSetting                                                              | Golden Path Value                  | Day-0\u002F1 | Notes\n-------------------------------------------------------------------- | ---------------------------------- | ------- | -----\n`privateClusterConfig.enablePrivateNodes`                            | `true`                             | Day-0   | Nodes have no public IPs\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled`   | `true`                             | Day-0   | Control plane only reachable via private endpoint or DNS\n`controlPlaneEndpointsConfig.dnsEndpointConfig.allowExternalTraffic` | `true`                             | Day-0   | Allows DNS-based access from outside VPC\n`networkConfig.datapathProvider`                                     | `ADVANCED_DATAPATH` (Dataplane V2) | Day-0   | eBPF-based, built-in Network Policy\n`networkConfig.dnsConfig.clusterDns`                                 | `CLOUD_DNS`                        | Day-0   | Managed DNS, more reliable than kube-dns\n`networkConfig.enableIntraNodeVisibility`                            | `true`                             | Day-1   | VPC Flow Logs for intra-node traffic\n`ipAllocationPolicy.autoIpamConfig.enabled`                          | `true`                             | Day-0   | Automatic IP range management\n`ipAllocationPolicy.createSubnetwork`                                | `true`                             | Day-0   | Auto-create dedicated subnet\n`defaultMaxPodsConstraint.maxPodsPerNode`                            | `48`                               | Day-0   | Conservative default; 110 for high density\n\n## Private Cluster Access Patterns\n\nThe golden path creates a private cluster. Users access it via:\n\n1.  **DNS endpoint (default)**: `allowExternalTraffic: true` enables access via\n    the cluster's DNS endpoint from outside the VPC. No VPN required.\n2.  **Private endpoint**: Direct access from within the VPC or via Cloud\n    VPN\u002FInterconnect.\n3.  **Authorized networks**: Add specific CIDRs to\n    `masterAuthorizedNetworksConfig` for IP-based access control.\n\n```bash\n# Access private cluster via DNS endpoint (golden path default)\ngcloud container clusters get-credentials {cluster_name} \\\n  --region {region} --dns-endpoint \\\n  --quiet\n\n# Access via private endpoint (from within VPC)\ngcloud container clusters get-credentials {cluster_name} \\\n  --region {region} --internal-ip \\\n  --quiet\n```\n\n## Bring-Your-Own VPC\u002FSubnet\n\nIf the customer has existing network infrastructure:\n\n```bash\ngcloud container clusters create-auto {cluster_name} \\\n  --region {region} \\\n  --network {vpc_name} \\\n  --subnetwork {subnet_name} \\\n  --cluster-secondary-range-name {pod_range} \\\n  --services-secondary-range-name {svc_range} \\\n  --enable-private-nodes \\\n  --enable-master-authorized-networks \\\n  --quiet\n```\n\n> **Day-0 Warning**: VPC, subnet, and IP ranges cannot be changed after cluster\n> creation.\n\n## VPC-Native Mode Benefits\n\nVPC-native clusters route traffic natively using GCP Alias IP ranges. Key\nbenefits to cover:\n\n1.  **Scalability**: Traffic routes natively inside the VPC, bypassing the need\n    for custom routes and avoiding custom route limit bottlenecks.\n2.  **Direct VPC Integration**: Direct resource integration across GCP networks\n    without complex bridging or routing tunnels.\n3.  **Avoiding IP Exhaustion**: Supports discontiguous IP ranges and optimizes\n    allocation, reducing the risk of exhausting subnet IP ranges.\n\n## IP Planning\n\n| Resource      | Golden Path  | Notes                                      |\n| ------------- | ------------ | ------------------------------------------ |\n| Pod CIDR      | `\u002F17` (auto) | ~32K pod IPs; size based on maxPodsPerNode |\n| Service CIDR  | `\u002F20` (auto) | ~4K service IPs                            |\n| Node subnet   | auto-created | \u002F20 recommended for growth                 |\n| Max pods\u002Fnode | 48           | Each node gets a \u002F25 pod range; set to 110 |\n:               :              : for \u002F24 per node                           :\n\n**Pod CIDR sizing rule of thumb:**\n\n-   `maxPodsPerNode=48` -> each node uses a `\u002F25` (128 IPs) from pod CIDR\n-   `maxPodsPerNode=110` -> each node uses a `\u002F24` (256 IPs) from pod CIDR\n-   Larger maxPodsPerNode = fewer nodes fit in a given CIDR\n\n## Egress\n\n-   Default: nodes use Cloud NAT for outbound internet access (private nodes\n    have no public IPs) to allow private nodes to reach the internet without\n    public IP exposure.\n-   For static egress IPs: configure Cloud NAT with manual IP allocation to\n    maintain a consistent source IP for external allowlists or partner\n    firewalls.\n-   For restricted egress: route through a firewall appliance via custom routes\n    to inspect and filter outbound traffic according to organization security\n    policies.\n\n## Network Policy\n\nDataplane V2 (golden path) provides built-in Network Policy enforcement — no\nadditional addon needed. Apply default-deny per namespace, then allow specific\nflows.\n\n> See the `gke-workload-security` skill for default-deny policy and the\n> `gke-multitenancy` skill for per-team allow policies.\n",{"name":5,"metadata":44,"description":7},{"version":45,"category":46},"1.0.1","Networking","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Fgke-networking",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-networking",{"tool":62,"command":63},"bunx","bunx skills add google\u002Fskills --skill gke-networking",{"tool":65,"command":66},"pnpm","pnpm dlx skills add google\u002Fskills --skill gke-networking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-networking\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fattribution.md","REFERENCE","参考文档",1882,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-networking\u002Freferences\u002Fattribution.md",[77,115,145,174,201,224],{"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,34,142,143,111,114,144,23],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","token","pair","platform",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":157,"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",[151,152,155,156],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":153,"categoryName":154,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[158,159,160,161,100,162,163,164,165,166,167,168,169,23,170,171,172,106,173,107],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"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",[],[181,182,183,184,185,186,187,188,103,189,190,191,192,193,194,167,195,196,197,23,198,199,172,200],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"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",[207,208,209],{"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,211,212,213,214,144,215,216,217,218,219,135,220,32,221,168,33,222,23,223,171],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","decision","database","candidate",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":232,"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",[230,231],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":123,"categoryName":124,"taxonomyType":86,"taxonomyTypeDesc":87},[233,234,110,235,9,161,236,100,162,237,35,238,239,23,240,171,106,241,242,243,244],"workload manager basics","workload","basics","cli","review","resources","inspect","you","create","libraries","server","run"]