[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6994G026XSE104YDYPPJMQE":3,"skill-same:01M6994G026XSE104YDYPPJMQE":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},"01M6994G026XSE104YDYPPJMQE","gke-platform-security",null,"Plans, configures, and hardens platform-level Google Kubernetes Engine (GKE) cluster security. Covers cluster add-ons (Secret Manager enablement), RBAC hardening (disabling insecure bindings, audit tools), Binary Authorization, Secrets Encryption (--database-encryption-key), Security Posture (--security-posture), enabling Shielded Nodes, GKE Sandbox cluster enablement, GKE IAM roles, and cross-service authentication IAM patterns. Use when securing cluster control planes, hardening GKE RBAC, enabling Shielded Nodes, enabling GKE Sandbox runtime, enabling cluster-wide security add-ons, or managing GKE IAM roles. Don't use for Workload Identity (use gke-workload-identity) or workload-level security (SecretProviderClass, PSS, NetPol, gVisor pod runtimeClassName; use gke-workload-security).","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-platform-security\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,9,33,34,35,36,37,38],"security","gke platform security","gke","platform","engine","when","for","enablement","cluster","plans","roles","runtime","Nodes","use","iam","encryption","database","authentication","sandbox","kubernetes","2026-11-10 10:12:30",false,"---\nname: gke-platform-security\ndescription: >-\n  Plans, configures, and hardens platform-level Google Kubernetes Engine (GKE)\n  cluster security. Covers cluster add-ons (Secret Manager enablement), RBAC\n  hardening (disabling insecure bindings, audit tools), Binary Authorization,\n  Secrets Encryption (--database-encryption-key), Security Posture (--security-posture),\n  enabling Shielded Nodes, GKE Sandbox cluster enablement, GKE IAM roles, and\n  cross-service authentication IAM patterns. Use when securing cluster control\n  planes, hardening GKE RBAC, enabling Shielded Nodes, enabling GKE Sandbox runtime,\n  enabling cluster-wide security add-ons, or managing GKE IAM roles. Don't use\n  for Workload Identity (use gke-workload-identity) or workload-level security\n  (SecretProviderClass, PSS, NetPol, gVisor pod runtimeClassName; use gke-workload-security).\nmetadata:\n  version: \"1.0.2\"\n  category: Security\n---\n\n# GKE Platform Security\n\nThis reference covers platform-level security hardening and cluster\nconfiguration for Google Kubernetes Engine (GKE). For workload-level security\ncontrols (such as Workload Identity Service Account bindings,\nSecretProviderClass volume mounts, Network Policies, and Pod Security\nStandards), refer to the `gke-workload-security` skill.\n\n> **MCP Tools:** `gke:get_cluster`, `k8s:check_k8s_auth`,\n> `k8s:get_k8s_resource`, `k8s:apply_k8s_manifest`, `gke: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-platform-security)\"`\nand append `agent-skills\u002F1.0 (skill:gke-platform-security)` to `User-Agent` headers.\n\n## Golden Path Security Defaults\n\nSetting                                                        | Golden Path Value                       | Day-0\u002F1 | Notes\n-------------------------------------------------------------- | --------------------------------------- | ------- | -----\n`workloadIdentityConfig.workloadPool`                          | `\u003CPROJECT>.svc.id.goog`                 | Day-0   | Workload Identity Federation for cluster pods\n`secretManagerConfig.enabled`                                  | `true`                                  | Day-1   | Google Secret Manager cluster add-on integration\n`secretManagerConfig.rotationConfig`                           | `enabled: true, rotationInterval: 120s` | Day-1   | Automatic secret rotation at the cluster level\n`rbacBindingConfig.enableInsecureBindingSystemAuthenticated`   | `false`                                 | Day-0   | Blocks legacy `system:authenticated` bindings\n`rbacBindingConfig.enableInsecureBindingSystemUnauthenticated` | `false`                                 | Day-0   | Blocks legacy `system:unauthenticated` bindings\n`nodeConfig.shieldedInstanceConfig.enableSecureBoot`           | `true`                                  | Day-0   | Verifiable boot integrity\n`nodeConfig.shieldedInstanceConfig.enableIntegrityMonitoring`  | `true`                                  | Day-0   | Runtime integrity checks\n`nodeConfig.workloadMetadataConfig.mode`                       | `GKE_METADATA`                          | Day-0   | Blocks legacy metadata API, enforces Workload Identity\nPrivate cluster + Dataplane V2 settings                        | See the `gke-networking` skill          | Day-0   | Private nodes, private endpoint enforcement, ADVANCED_DATAPATH\n\n## Secret Manager Add-on Enablement\n\nThe golden path enables Secret Manager at the cluster level with automatic\nsecret rotation.\n\n```bash\n# Verify Secret Manager is enabled on cluster\ngcloud container clusters describe \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --format=\"value(secretManagerConfig.enabled)\" \\\n  --quiet\n\n# Enable if not already (Day-1 change)\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-secret-manager \\\n  --secret-manager-rotation-interval=120s \\\n  --quiet\n```\n\n> **Note:** For configuring `SecretProviderClass` manifests and mounting secrets\n> as volumes inside application deployments, see the `gke-workload-security`\n> skill.\n\n## RBAC Hardening\n\nThe golden path disables insecure legacy RBAC bindings that grant broad access\nto `system:authenticated` and `system:unauthenticated` groups.\n\n```bash\n# Verify insecure bindings are disabled\ngcloud container clusters describe \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --format=\"yaml(rbacBindingConfig)\" \\\n  --quiet\n```\n\n**Best practices for RBAC:**\n\n-   Use namespace-scoped Roles over cluster-wide ClusterRoles.\n-   Bind to specific Groups or ServiceAccounts, never to `system:authenticated`\n    or `system:unauthenticated`.\n-   Audit permissions via MCP: `k8s:check_k8s_auth(parent=\"...\", verb=\"list\",\n    resourceType=\"pods\", namespace=\"...\")` (or `kubectl auth can-i --list\n    --as=\u003Cuser>`).\n-   Review bindings via MCP: `k8s:get_k8s_resource(parent=\"...\",\n    resourceType=\"clusterrolebinding\")` (or `kubectl get\n    clusterrolebindings,rolebindings --all-namespaces`).\n\n> See the `gke-multitenancy` skill for enterprise RBAC planning and\n> https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fbest-practices\u002Frbac.md.txt\n\n## Binary Authorization\n\nNot enabled in golden path by default but recommended for enforcing production\nimage provenance across the cluster:\n\n```bash\n# Enable Binary Authorization\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE \\\n  --quiet\n```\n\n## Shielded Nodes & GKE Sandbox Enablement\n\nEnabling verifiable node boot integrity and kernel isolation features at the\ncluster level:\n\n```bash\n# Enable Shielded Nodes on an existing cluster\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-shielded-nodes \\\n  --quiet\n\n# Enable GKE Sandbox (gVisor) runtime on an existing cluster\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-gke-sandbox \\\n  --quiet\n```\n\n> **Note:** To run workloads inside the gVisor sandbox, specify\n> `runtimeClassName: gvisor` in your Pod specs as detailed in the\n> `gke-workload-security` skill.\n\n## Common IAM Roles\n\nThe five most common predefined IAM roles for GKE platform and cluster access:\n\n| Role                            | Purpose             | When to Use          |\n| ------------------------------- | ------------------- | -------------------- |\n| `roles\u002Fcontainer.admin`         | Full control over   | Platform team admins |\n:                                 : clusters and        : managing cluster     :\n:                                 : Kubernetes          : lifecycle            :\n:                                 : resources           :                      :\n| `roles\u002Fcontainer.clusterAdmin`  | Manage clusters but | Cluster operators    |\n:                                 : not project-level   : who create\u002Fdelete    :\n:                                 : IAM                 : clusters             :\n| `roles\u002Fcontainer.developer`     | Deploy workloads    | Application          |\n:                                 : (pods, services,    : developers deploying :\n:                                 : deployments)        : to existing clusters :\n| `roles\u002Fcontainer.viewer`        | Read-only access to | Monitoring,          |\n:                                 : clusters and        : auditing, or         :\n:                                 : Kubernetes          : read-only dashboards :\n:                                 : resources           :                      :\n| `roles\u002Fcontainer.clusterViewer` | List and get        | CI\u002FCD pipelines that |\n:                                 : cluster details     : need cluster         :\n:                                 : only                : metadata             :\n\n> **Principle of least privilege**: Start with `roles\u002Fcontainer.viewer` or\n> `roles\u002Fcontainer.developer` and escalate only as needed. Avoid granting\n> `roles\u002Fcontainer.admin` broadly across teams.\n\n## Service Accounts & Agents\n\n-   **GKE Service Agent**\n    (`service-\u003CPROJECT_NUMBER>@container-engine-robot.iam.gserviceaccount.com`):\n    Automatically created. Manages nodes, networking, and cluster operations on\n    your behalf. Do not remove or modify its permissions.\n-   **Node Service Account**: By default, nodes use the Compute Engine default\n    service account. For production platforms, create a dedicated Google Service\n    Account with minimal required permissions (`roles\u002Fmonitoring.metricWriter`,\n    `roles\u002Flogging.logWriter`) and assign it at node pool creation time.\n-   **Workload Identity**: For binding Google Service Accounts to Kubernetes\n    Service Accounts (`roles\u002Fiam.workloadIdentityUser`), refer to the\n    `gke-workload-security` skill.\n\n## Cross-Service Authentication Patterns\n\nCommon project-level IAM policy binding patterns for granting backend Google\nService Accounts (GSAs) access to external Google Cloud services before linking\nvia Workload Identity:\n\n```bash\n# Grant a GSA access to Cloud Storage objects\ngcloud projects add-iam-policy-binding \u003CPROJECT_ID> \\\n  --member \"serviceAccount:\u003CGSA_NAME>@\u003CPROJECT_ID>.iam.gserviceaccount.com\" \\\n  --role \"roles\u002Fstorage.objectViewer\" \\\n  --quiet\n\n# Grant a GSA access to Cloud SQL databases\ngcloud projects add-iam-policy-binding \u003CPROJECT_ID> \\\n  --member \"serviceAccount:\u003CGSA_NAME>@\u003CPROJECT_ID>.iam.gserviceaccount.com\" \\\n  --role \"roles\u002Fcloudsql.client\" \\\n  --quiet\n\n# Grant a GSA access to Pub\u002FSub subscriptions\ngcloud projects add-iam-policy-binding \u003CPROJECT_ID> \\\n  --member \"serviceAccount:\u003CGSA_NAME>@\u003CPROJECT_ID>.iam.gserviceaccount.com\" \\\n  --role \"roles\u002Fpubsub.subscriber\" \\\n  --quiet\n\n## Resources\n\n- [GKE Cluster Hardening Guide](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fhardening-your-cluster)\n- [GKE RBAC Best Practices](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fbest-practices\u002Frbac)\n- [Secret Manager Add-on for GKE](https:\u002F\u002Fcloud.google.com\u002Fsecret-manager\u002Fdocs\u002Fsecret-manager-managed-csi-component)\n- [Binary Authorization on GKE](https:\u002F\u002Fcloud.google.com\u002Fbinary-authorization\u002Fdocs\u002Fsetting-up)\n- [Shielded GKE Nodes](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fshielded-gke-nodes)\n- [GKE Sandbox (gVisor)](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fsandbox-pods)\n```\n","# GKE Platform Security\n\nThis reference covers platform-level security hardening and cluster\nconfiguration for Google Kubernetes Engine (GKE). For workload-level security\ncontrols (such as Workload Identity Service Account bindings,\nSecretProviderClass volume mounts, Network Policies, and Pod Security\nStandards), refer to the `gke-workload-security` skill.\n\n> **MCP Tools:** `gke:get_cluster`, `k8s:check_k8s_auth`,\n> `k8s:get_k8s_resource`, `k8s:apply_k8s_manifest`, `gke: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-platform-security)\"`\nand append `agent-skills\u002F1.0 (skill:gke-platform-security)` to `User-Agent` headers.\n\n## Golden Path Security Defaults\n\nSetting                                                        | Golden Path Value                       | Day-0\u002F1 | Notes\n-------------------------------------------------------------- | --------------------------------------- | ------- | -----\n`workloadIdentityConfig.workloadPool`                          | `\u003CPROJECT>.svc.id.goog`                 | Day-0   | Workload Identity Federation for cluster pods\n`secretManagerConfig.enabled`                                  | `true`                                  | Day-1   | Google Secret Manager cluster add-on integration\n`secretManagerConfig.rotationConfig`                           | `enabled: true, rotationInterval: 120s` | Day-1   | Automatic secret rotation at the cluster level\n`rbacBindingConfig.enableInsecureBindingSystemAuthenticated`   | `false`                                 | Day-0   | Blocks legacy `system:authenticated` bindings\n`rbacBindingConfig.enableInsecureBindingSystemUnauthenticated` | `false`                                 | Day-0   | Blocks legacy `system:unauthenticated` bindings\n`nodeConfig.shieldedInstanceConfig.enableSecureBoot`           | `true`                                  | Day-0   | Verifiable boot integrity\n`nodeConfig.shieldedInstanceConfig.enableIntegrityMonitoring`  | `true`                                  | Day-0   | Runtime integrity checks\n`nodeConfig.workloadMetadataConfig.mode`                       | `GKE_METADATA`                          | Day-0   | Blocks legacy metadata API, enforces Workload Identity\nPrivate cluster + Dataplane V2 settings                        | See the `gke-networking` skill          | Day-0   | Private nodes, private endpoint enforcement, ADVANCED_DATAPATH\n\n## Secret Manager Add-on Enablement\n\nThe golden path enables Secret Manager at the cluster level with automatic\nsecret rotation.\n\n```bash\n# Verify Secret Manager is enabled on cluster\ngcloud container clusters describe \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --format=\"value(secretManagerConfig.enabled)\" \\\n  --quiet\n\n# Enable if not already (Day-1 change)\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-secret-manager \\\n  --secret-manager-rotation-interval=120s \\\n  --quiet\n```\n\n> **Note:** For configuring `SecretProviderClass` manifests and mounting secrets\n> as volumes inside application deployments, see the `gke-workload-security`\n> skill.\n\n## RBAC Hardening\n\nThe golden path disables insecure legacy RBAC bindings that grant broad access\nto `system:authenticated` and `system:unauthenticated` groups.\n\n```bash\n# Verify insecure bindings are disabled\ngcloud container clusters describe \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --format=\"yaml(rbacBindingConfig)\" \\\n  --quiet\n```\n\n**Best practices for RBAC:**\n\n-   Use namespace-scoped Roles over cluster-wide ClusterRoles.\n-   Bind to specific Groups or ServiceAccounts, never to `system:authenticated`\n    or `system:unauthenticated`.\n-   Audit permissions via MCP: `k8s:check_k8s_auth(parent=\"...\", verb=\"list\",\n    resourceType=\"pods\", namespace=\"...\")` (or `kubectl auth can-i --list\n    --as=\u003Cuser>`).\n-   Review bindings via MCP: `k8s:get_k8s_resource(parent=\"...\",\n    resourceType=\"clusterrolebinding\")` (or `kubectl get\n    clusterrolebindings,rolebindings --all-namespaces`).\n\n> See the `gke-multitenancy` skill for enterprise RBAC planning and\n> https:\u002F\u002Fdocs.cloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fbest-practices\u002Frbac.md.txt\n\n## Binary Authorization\n\nNot enabled in golden path by default but recommended for enforcing production\nimage provenance across the cluster:\n\n```bash\n# Enable Binary Authorization\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE \\\n  --quiet\n```\n\n## Shielded Nodes & GKE Sandbox Enablement\n\nEnabling verifiable node boot integrity and kernel isolation features at the\ncluster level:\n\n```bash\n# Enable Shielded Nodes on an existing cluster\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-shielded-nodes \\\n  --quiet\n\n# Enable GKE Sandbox (gVisor) runtime on an existing cluster\ngcloud container clusters update \u003CCLUSTER_NAME> --region \u003CREGION> \\\n  --enable-gke-sandbox \\\n  --quiet\n```\n\n> **Note:** To run workloads inside the gVisor sandbox, specify\n> `runtimeClassName: gvisor` in your Pod specs as detailed in the\n> `gke-workload-security` skill.\n\n## Common IAM Roles\n\nThe five most common predefined IAM roles for GKE platform and cluster access:\n\n| Role                            | Purpose             | When to Use          |\n| ------------------------------- | ------------------- | -------------------- |\n| `roles\u002Fcontainer.admin`         | Full control over   | Platform team admins |\n:                                 : clusters and        : managing cluster     :\n:                                 : Kubernetes          : lifecycle            :\n:                                 : resources           :                      :\n| `roles\u002Fcontainer.clusterAdmin`  | Manage clusters but | Cluster operators    |\n:                                 : not project-level   : who create\u002Fdelete    :\n:                                 : IAM                 : clusters             :\n| `roles\u002Fcontainer.developer`     | Deploy workloads    | Application          |\n:                                 : (pods, services,    : developers deploying :\n:                                 : deployments)        : to existing clusters :\n| `roles\u002Fcontainer.viewer`        | Read-only access to | Monitoring,          |\n:                                 : clusters and        : auditing, or         :\n:                                 : Kubernetes          : read-only dashboards :\n:                                 : resources           :                      :\n| `roles\u002Fcontainer.clusterViewer` | List and get        | CI\u002FCD pipelines that |\n:                                 : cluster details     : need cluster         :\n:                                 : only                : metadata             :\n\n> **Principle of least privilege**: Start with `roles\u002Fcontainer.viewer` or\n> `roles\u002Fcontainer.developer` and escalate only as needed. Avoid granting\n> `roles\u002Fcontainer.admin` broadly across teams.\n\n## Service Accounts & Agents\n\n-   **GKE Service Agent**\n    (`service-\u003CPROJECT_NUMBER>@container-engine-robot.iam.gserviceaccount.com`):\n    Automatically created. Manages nodes, networking, and cluster operations on\n    your behalf. Do not remove or modify its permissions.\n-   **Node Service Account**: By default, nodes use the Compute Engine default\n    service account. For production platforms, create a dedicated Google Service\n    Account with minimal required permissions (`roles\u002Fmonitoring.metricWriter`,\n    `roles\u002Flogging.logWriter`) and assign it at node pool creation time.\n-   **Workload Identity**: For binding Google Service Accounts to Kubernetes\n    Service Accounts (`roles\u002Fiam.workloadIdentityUser`), refer to the\n    `gke-workload-security` skill.\n\n## Cross-Service Authentication Patterns\n\nCommon project-level IAM policy binding patterns for granting backend Google\nService Accounts (GSAs) access to external Google Cloud services before linking\nvia Workload Identity:\n\n```bash\n# Grant a GSA access to Cloud Storage objects\ngcloud projects add-iam-policy-binding \u003CPROJECT_ID> \\\n  --member \"serviceAccount:\u003CGSA_NAME>@\u003CPROJECT_ID>.iam.gserviceaccount.com\" \\\n  --role \"roles\u002Fstorage.objectViewer\" \\\n  --quiet\n\n# Grant a GSA access to Cloud SQL databases\ngcloud projects add-iam-policy-binding \u003CPROJECT_ID> \\\n  --member \"serviceAccount:\u003CGSA_NAME>@\u003CPROJECT_ID>.iam.gserviceaccount.com\" \\\n  --role \"roles\u002Fcloudsql.client\" \\\n  --quiet\n\n# Grant a GSA access to Pub\u002FSub subscriptions\ngcloud projects add-iam-policy-binding \u003CPROJECT_ID> \\\n  --member \"serviceAccount:\u003CGSA_NAME>@\u003CPROJECT_ID>.iam.gserviceaccount.com\" \\\n  --role \"roles\u002Fpubsub.subscriber\" \\\n  --quiet\n\n## Resources\n\n- [GKE Cluster Hardening Guide](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fhardening-your-cluster)\n- [GKE RBAC Best Practices](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fbest-practices\u002Frbac)\n- [Secret Manager Add-on for GKE](https:\u002F\u002Fcloud.google.com\u002Fsecret-manager\u002Fdocs\u002Fsecret-manager-managed-csi-component)\n- [Binary Authorization on GKE](https:\u002F\u002Fcloud.google.com\u002Fbinary-authorization\u002Fdocs\u002Fsetting-up)\n- [Shielded GKE Nodes](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fshielded-gke-nodes)\n- [GKE Sandbox (gVisor)](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fsandbox-pods)\n```\n",{"name":5,"metadata":44,"description":7},{"version":45,"category":46},"1.0.2","Security","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Fgke-platform-security",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-platform-security",{"tool":62,"command":63},"bunx","bunx skills add google\u002Fskills --skill gke-platform-security",{"tool":65,"command":66},"pnpm","pnpm dlx skills add google\u002Fskills --skill gke-platform-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-platform-security\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fattribution.md","REFERENCE","参考文档",1903,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-platform-security\u002Freferences\u002Fattribution.md",[77,113,142,171,198,221],{"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,19,98,99,100,101,102,103,104,33,105,106,107,108,109,110,111,112],"sign in with google web","sign","with","web","android","go","google workspace","google cloud","implement","policy","python","implementing","react","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":128,"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",[119,120,123],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":121,"categoryName":122,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[129,130,9,99,131,132,36,133,134,135,33,136,137,138,139,140,141,109,112,22,24],"dpop adoption","adoption","es6","retry","flows","challenge","code","browser","loops","at","node","token","pair",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":154,"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",[148,149,152,153],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":150,"categoryName":151,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":121,"categoryName":122,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},[155,156,157,158,99,159,160,161,162,163,164,165,166,24,167,168,169,33,170,105],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"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",[],[178,179,180,181,182,183,184,185,102,186,187,188,189,190,191,164,192,193,194,24,195,196,169,197],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":207,"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",[204,205,206],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":121,"categoryName":122,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},[9,208,209,210,211,22,212,213,214,215,216,36,217,218,219,165,32,35,24,220,168],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","candidate",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":229,"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",[227,228],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":121,"categoryName":122,"taxonomyType":86,"taxonomyTypeDesc":87},[230,231,108,232,9,158,233,99,159,234,235,236,237,24,238,168,33,239,240,241,242],"workload manager basics","workload","basics","cli","review","vpc","resources","inspect","you","create","libraries","server","run"]