[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69952BPHJNJPM17JCAYT8N0":3,"skill-same:01M69952BPHJNJPM17JCAYT8N0":91},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M69952BPHJNJPM17JCAYT8N0","gke-workload-security",null,"Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (`audit_cluster.sh`), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (`gVisor`), enforcing Pod Security Standards (`restricted` labeling) and pod securityContext, and mounting Secret Manager secrets via CSI (`SecretProviderClass`). Use when auditing workload security posture, isolating namespaces, applying pod security standards, or configuring network policies and secret volume mounts. Don't use for Workload Identity (use gke-workload-identity), cluster-wide control plane security, RBAC hardening, Binary Authorization, Shielded Nodes, or enabling platform-level GKE add-ons (use gke-platform-security 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-workload-security\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,9],"security","gke workload security","gke","workload","standards","logging","add","identity","manager","network","secrets","rbac","secret manager","audit","plane","when","security standards","default","volume","2026-11-10 10:12:30",false,"---\nname: gke-workload-security\ndescription: >-\n  Audits, configures, and hardens workload-level security controls for Google\n  Kubernetes Engine (GKE) applications and namespaces. Covers running security\n  audits (`audit_cluster.sh`), enforcing Network Policies (default-deny and Dataplane\n  V2 logging), isolating high-risk pods inside GKE Sandbox (`gVisor`), enforcing Pod\n  Security Standards (`restricted` labeling) and pod securityContext, and mounting Secret Manager secrets via\n  CSI (`SecretProviderClass`). Use when auditing workload security posture, isolating\n  namespaces, applying pod security standards, or\n  configuring network policies and secret volume mounts. Don't use for Workload Identity (use gke-workload-identity), cluster-wide\n  control plane security, RBAC hardening, Binary Authorization, Shielded Nodes,\n  or enabling platform-level GKE add-ons (use gke-platform-security instead).\nmetadata:\n  version: \"1.0.3\"\n  category: Security\n---\n\n# GKE Workload Security\n\n> **Routing Note:** For Workload Identity IAM and KSA\u002FGSA bindings, use the `gke-workload-identity` skill. For cluster-level security flags (`--database-encryption-key`, `--security-posture`, RBAC, Shielded Nodes, Binary Authorization), use the `gke-platform-security` skill.\n\nThis skill provides workflows and best practices for securing GKE workloads. It\ncovers security auditing, Identity and Access Management (Workload Identity),\nNetwork Security (Network Policies), and Node Security.\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-workload-security)\"`\nand append `agent-skills\u002F1.0 (skill:gke-workload-security)` to `User-Agent` headers.\n\n## Workflows\n\n### 1. Security Audit\n\nAssess the current security posture of your cluster using the provided audit\nscript.\n\n**Prerequisites:**\n\n-   `gcloud` CLI authenticated.\n-   `jq` command-line JSON processor installed.\n\n**Capabilities:**\n\n-   Checks for Workload Identity.\n-   Verifies Network Policy is enabled.\n-   Checks if Shielded Nodes are enabled.\n-   Checks if Binary Authorization is enabled.\n-   Checks for Private Cluster configuration.\n\n**Command:**\n\n```bash\nscripts\u002Faudit_cluster.sh \u003Ccluster-name> \u003Cregion> \u003Cproject-id>\n```\n\n### 2. Configure Workload Identity\n\nWorkload Identity allows Kubernetes Service Accounts (KSAs) to impersonate\nGoogle Service Accounts (GSAs). Use this method when workloads require a\ndedicated GSA to access Google Cloud APIs; for most workloads, direct IAM\nprincipal binding (covered in the `gke-workload-identity` skill) is the\nrecommended method.\n\n**Steps:**\n\n1.  **Create Namespace and KSA:**\n\n    ```bash\n    kubectl create namespace workload-identity-test-ns\n    kubectl create serviceaccount \u003Cksa-name> \\\n        --namespace workload-identity-test-ns\n    ```\n\n2.  **Bind KSA to GSA:**\n\n    ```bash\n    gcloud iam service-accounts add-iam-policy-binding \u003Cgsa-name>@\u003Cproject-id>.iam.gserviceaccount.com \\\n        --role roles\u002Fiam.workloadIdentityUser \\\n        --member \"serviceAccount:\u003Cproject-id>.svc.id.goog[workload-identity-test-ns\u002F\u003Cksa-name>]\"\n    ```\n\n3.  **Annotate KSA:**\n\n    ```bash\n    kubectl annotate serviceaccount \u003Cksa-name> \\\n        --namespace workload-identity-test-ns \\\n        iam.gke.io\u002Fgcp-service-account=\u003Cgsa-name>@\u003Cproject-id>.iam.gserviceaccount.com\n    ```\n\n4.  **Verify Example Pod:** Use existing asset\n    `assets\u002Fworkload-identity-pod.yaml` to test the configuration. Update the\n    `\u003Cksa-name>` in the file first.\n\n    ```bash\n    kubectl apply -f assets\u002Fworkload-identity-pod.yaml -n workload-identity-test-ns\n    ```\n\n### 3. Implement Network Policies\n\nControl traffic flow between Pods using Network Policies. By default, all\ntraffic is allowed.\n\n**Enable Network Policy Enforcement:**\n\n```bash\ngcloud container clusters update \u003Ccluster-name> \\\n    --update-addons=NetworkPolicy=ENABLED \\\n    --region \u003Cregion>\n```\n\n> [!NOTE] If your cluster uses Dataplane V2 (`--enable-dataplane-v2`), Network\n> Policy enforcement is built-in and this step is not required (and may fail).\n\n**Apply Default Deny Policy:** Isolate namespaces by denying all ingress and\negress traffic by default.\n\n**Replace `\u003Ctarget-namespace>` with the namespace you want to isolate.**\n\n```bash\nkubectl apply -f assets\u002Fdefault-deny-netpol.yaml -n \u003Ctarget-namespace>\n```\n\n### 4. GKE Sandbox (gVisor) Pod Isolation\n\nRun untrusted workloads in a sandbox for extra kernel isolation. *(Note:\nEnabling Shielded Nodes (`--enable-shielded-nodes`) and GKE Sandbox\n(`--enable-gke-sandbox`) at the cluster control plane level are platform-level\nactions covered in the `gke-platform-security` skill.)*\n\n**Run a Sandboxed Pod:** Add `runtimeClassName: gvisor` to your Pod spec:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: sandboxed-pod\nspec:\n  runtimeClassName: gvisor\n  containers:\n  - name: app\n    image: nginx\n```\n\n### 5. Pod Security Standards\n\nEnforce security policies on namespaces using labels.\n\n**Enforce Restricted Profile:**\n\n```bash\nkubectl label --overwrite ns \u003Cnamespace> \\\n    pod-security.kubernetes.io\u002Fenforce=restricted \\\n    pod-security.kubernetes.io\u002Fenforce-version=latest\n```\n\n> [!NOTE] Using `latest` ensures you use the policies corresponding to the\n> cluster's current version. You can pin it to a specific version (e.g.,\n> `v1.30`) to lock down the namespace to policies of a specific release.\n\n### 6. Secret Manager Integration (CSI Driver)\n\nMount secrets from Google Cloud Secret Manager directly as volumes in your pods.\n\n**Prerequisites**: Secret Manager CSI driver must be enabled on the cluster.\n\n**Example SecretProviderClass:**\n\n```yaml\napiVersion: secrets-store.csi.x-k8s.io\u002Fv1\nkind: SecretProviderClass\nmetadata:\n  name: my-secret-provider\nspec:\n  provider: gcp\n  parameters:\n    secrets: |\n      - resourceName: \"projects\u002F\u003Cproject-id>\u002Fsecrets\u002Fmy-secret\u002Fversions\u002Flatest\"\n        fileName: \"my-secret-file\"\n```\n\n**Example Pod Spec excerpt:**\n\n```yaml\nspec:\n  containers:\n    - name: my-app\n      volumeMounts:\n        - name: secrets-store-inline\n          mountPath: \"\u002Fmnt\u002Fsecrets\"\n          readOnly: true\n  volumes:\n    - name: secrets-store-inline\n      csi:\n        driver: secrets-store.csi.k8s.io\n        readOnly: true\n        volumeAttributes:\n          secretProviderClass: \"my-secret-provider\"\n```\n\n### 7. Enable Network Policy Logging\n\nIf using GKE Dataplane V2, you can log allowed and denied connections.\n\n**Steps:**\n\n1.  Configure the `NetworkLogging` custom resource.\n\n**Example NetworkLogging Manifest:**\n\n```yaml\napiVersion: networking.gke.io\u002Fv1alpha1\nkind: NetworkLogging\nmetadata:\n  name: default\nspec:\n  cluster:\n    allow:\n      log: true\n      delegate: true\n    deny:\n      log: true\n      delegate: true\n```\n\nThis will log connection details to Cloud Logging.\n\n## Best Practices\n\n1.  **Least Privilege:** Always use Workload Identity with minimal IAM roles.\n    Avoid using Node default service accounts.\n2.  **Network Isolation:** Use Network Policies to restrict Pod-to-Pod\n    communication. Enable Network Policy Logging for visibility.\n3.  **Image Security:** Use Binary Authorization to ensure only trusted images\n    are deployed.\n4.  **Secret Management**: Use Secret Manager CSI driver instead of default\n    Kubernetes secrets for sensitive data.\n5.  **Pod Security**: Enforce `baseline` or `restricted` Pod Security Standards\n    on all non-system namespaces.\n6.  **Policy Enforcement**: Consider using **Policy Controller** (Gatekeeper) to\n    enforce custom security and compliance policies across the cluster.\n\n## Resources\n\n-   [Workload Identity Federation for GKE](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fworkload-identity)\n-   [GKE Network Policies](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnetwork-policy)\n-   [Pod Security Standards in GKE](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fpodsecurityadmission)\n-   [Google Secret Manager CSI Driver](https:\u002F\u002Fcloud.google.com\u002Fsecret-manager\u002Fdocs\u002Fsecret-manager-managed-csi-component)\n-   [GKE Dataplane V2 Network Logging](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnetwork-policy-logging)\n","# GKE Workload Security\n\n> **Routing Note:** For Workload Identity IAM and KSA\u002FGSA bindings, use the `gke-workload-identity` skill. For cluster-level security flags (`--database-encryption-key`, `--security-posture`, RBAC, Shielded Nodes, Binary Authorization), use the `gke-platform-security` skill.\n\nThis skill provides workflows and best practices for securing GKE workloads. It\ncovers security auditing, Identity and Access Management (Workload Identity),\nNetwork Security (Network Policies), and Node Security.\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-workload-security)\"`\nand append `agent-skills\u002F1.0 (skill:gke-workload-security)` to `User-Agent` headers.\n\n## Workflows\n\n### 1. Security Audit\n\nAssess the current security posture of your cluster using the provided audit\nscript.\n\n**Prerequisites:**\n\n-   `gcloud` CLI authenticated.\n-   `jq` command-line JSON processor installed.\n\n**Capabilities:**\n\n-   Checks for Workload Identity.\n-   Verifies Network Policy is enabled.\n-   Checks if Shielded Nodes are enabled.\n-   Checks if Binary Authorization is enabled.\n-   Checks for Private Cluster configuration.\n\n**Command:**\n\n```bash\nscripts\u002Faudit_cluster.sh \u003Ccluster-name> \u003Cregion> \u003Cproject-id>\n```\n\n### 2. Configure Workload Identity\n\nWorkload Identity allows Kubernetes Service Accounts (KSAs) to impersonate\nGoogle Service Accounts (GSAs). Use this method when workloads require a\ndedicated GSA to access Google Cloud APIs; for most workloads, direct IAM\nprincipal binding (covered in the `gke-workload-identity` skill) is the\nrecommended method.\n\n**Steps:**\n\n1.  **Create Namespace and KSA:**\n\n    ```bash\n    kubectl create namespace workload-identity-test-ns\n    kubectl create serviceaccount \u003Cksa-name> \\\n        --namespace workload-identity-test-ns\n    ```\n\n2.  **Bind KSA to GSA:**\n\n    ```bash\n    gcloud iam service-accounts add-iam-policy-binding \u003Cgsa-name>@\u003Cproject-id>.iam.gserviceaccount.com \\\n        --role roles\u002Fiam.workloadIdentityUser \\\n        --member \"serviceAccount:\u003Cproject-id>.svc.id.goog[workload-identity-test-ns\u002F\u003Cksa-name>]\"\n    ```\n\n3.  **Annotate KSA:**\n\n    ```bash\n    kubectl annotate serviceaccount \u003Cksa-name> \\\n        --namespace workload-identity-test-ns \\\n        iam.gke.io\u002Fgcp-service-account=\u003Cgsa-name>@\u003Cproject-id>.iam.gserviceaccount.com\n    ```\n\n4.  **Verify Example Pod:** Use existing asset\n    `assets\u002Fworkload-identity-pod.yaml` to test the configuration. Update the\n    `\u003Cksa-name>` in the file first.\n\n    ```bash\n    kubectl apply -f assets\u002Fworkload-identity-pod.yaml -n workload-identity-test-ns\n    ```\n\n### 3. Implement Network Policies\n\nControl traffic flow between Pods using Network Policies. By default, all\ntraffic is allowed.\n\n**Enable Network Policy Enforcement:**\n\n```bash\ngcloud container clusters update \u003Ccluster-name> \\\n    --update-addons=NetworkPolicy=ENABLED \\\n    --region \u003Cregion>\n```\n\n> [!NOTE] If your cluster uses Dataplane V2 (`--enable-dataplane-v2`), Network\n> Policy enforcement is built-in and this step is not required (and may fail).\n\n**Apply Default Deny Policy:** Isolate namespaces by denying all ingress and\negress traffic by default.\n\n**Replace `\u003Ctarget-namespace>` with the namespace you want to isolate.**\n\n```bash\nkubectl apply -f assets\u002Fdefault-deny-netpol.yaml -n \u003Ctarget-namespace>\n```\n\n### 4. GKE Sandbox (gVisor) Pod Isolation\n\nRun untrusted workloads in a sandbox for extra kernel isolation. *(Note:\nEnabling Shielded Nodes (`--enable-shielded-nodes`) and GKE Sandbox\n(`--enable-gke-sandbox`) at the cluster control plane level are platform-level\nactions covered in the `gke-platform-security` skill.)*\n\n**Run a Sandboxed Pod:** Add `runtimeClassName: gvisor` to your Pod spec:\n\n```yaml\napiVersion: v1\nkind: Pod\nmetadata:\n  name: sandboxed-pod\nspec:\n  runtimeClassName: gvisor\n  containers:\n  - name: app\n    image: nginx\n```\n\n### 5. Pod Security Standards\n\nEnforce security policies on namespaces using labels.\n\n**Enforce Restricted Profile:**\n\n```bash\nkubectl label --overwrite ns \u003Cnamespace> \\\n    pod-security.kubernetes.io\u002Fenforce=restricted \\\n    pod-security.kubernetes.io\u002Fenforce-version=latest\n```\n\n> [!NOTE] Using `latest` ensures you use the policies corresponding to the\n> cluster's current version. You can pin it to a specific version (e.g.,\n> `v1.30`) to lock down the namespace to policies of a specific release.\n\n### 6. Secret Manager Integration (CSI Driver)\n\nMount secrets from Google Cloud Secret Manager directly as volumes in your pods.\n\n**Prerequisites**: Secret Manager CSI driver must be enabled on the cluster.\n\n**Example SecretProviderClass:**\n\n```yaml\napiVersion: secrets-store.csi.x-k8s.io\u002Fv1\nkind: SecretProviderClass\nmetadata:\n  name: my-secret-provider\nspec:\n  provider: gcp\n  parameters:\n    secrets: |\n      - resourceName: \"projects\u002F\u003Cproject-id>\u002Fsecrets\u002Fmy-secret\u002Fversions\u002Flatest\"\n        fileName: \"my-secret-file\"\n```\n\n**Example Pod Spec excerpt:**\n\n```yaml\nspec:\n  containers:\n    - name: my-app\n      volumeMounts:\n        - name: secrets-store-inline\n          mountPath: \"\u002Fmnt\u002Fsecrets\"\n          readOnly: true\n  volumes:\n    - name: secrets-store-inline\n      csi:\n        driver: secrets-store.csi.k8s.io\n        readOnly: true\n        volumeAttributes:\n          secretProviderClass: \"my-secret-provider\"\n```\n\n### 7. Enable Network Policy Logging\n\nIf using GKE Dataplane V2, you can log allowed and denied connections.\n\n**Steps:**\n\n1.  Configure the `NetworkLogging` custom resource.\n\n**Example NetworkLogging Manifest:**\n\n```yaml\napiVersion: networking.gke.io\u002Fv1alpha1\nkind: NetworkLogging\nmetadata:\n  name: default\nspec:\n  cluster:\n    allow:\n      log: true\n      delegate: true\n    deny:\n      log: true\n      delegate: true\n```\n\nThis will log connection details to Cloud Logging.\n\n## Best Practices\n\n1.  **Least Privilege:** Always use Workload Identity with minimal IAM roles.\n    Avoid using Node default service accounts.\n2.  **Network Isolation:** Use Network Policies to restrict Pod-to-Pod\n    communication. Enable Network Policy Logging for visibility.\n3.  **Image Security:** Use Binary Authorization to ensure only trusted images\n    are deployed.\n4.  **Secret Management**: Use Secret Manager CSI driver instead of default\n    Kubernetes secrets for sensitive data.\n5.  **Pod Security**: Enforce `baseline` or `restricted` Pod Security Standards\n    on all non-system namespaces.\n6.  **Policy Enforcement**: Consider using **Policy Controller** (Gatekeeper) to\n    enforce custom security and compliance policies across the cluster.\n\n## Resources\n\n-   [Workload Identity Federation for GKE](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fworkload-identity)\n-   [GKE Network Policies](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnetwork-policy)\n-   [Pod Security Standards in GKE](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fpodsecurityadmission)\n-   [Google Secret Manager CSI Driver](https:\u002F\u002Fcloud.google.com\u002Fsecret-manager\u002Fdocs\u002Fsecret-manager-managed-csi-component)\n-   [GKE Dataplane V2 Network Logging](https:\u002F\u002Fcloud.google.com\u002Fkubernetes-engine\u002Fdocs\u002Fhow-to\u002Fnetwork-policy-logging)\n",{"name":5,"metadata":43,"description":7},{"version":44,"category":45},"1.0.3","Security","main","2194d3b8b1f31975fef2f1a0ae6b9ab55bd7ceee","skills\u002Fcloud\u002Fgke-workload-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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add google\u002Fskills --skill gke-workload-security",{"tool":61,"command":62},"bunx","bunx skills add google\u002Fskills --skill gke-workload-security",{"tool":64,"command":65},"pnpm","pnpm dlx skills add google\u002Fskills --skill gke-workload-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-workload-security\u002FSKILL.md",true,[69,75,79,85],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Fdefault-deny-netpol.yaml","ASSET","资产文件",235,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-workload-security\u002Fassets\u002Fdefault-deny-netpol.yaml",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Fworkload-identity-pod.yaml",1207,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-workload-security\u002Fassets\u002Fworkload-identity-pod.yaml",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fattribution.md","REFERENCE","参考文档",1903,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-workload-security\u002Freferences\u002Fattribution.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Faudit_cluster.sh","SCRIPT","脚本",2261,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fgke-workload-security\u002Fscripts\u002Faudit_cluster.sh",[92,127,158,187,214,239],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":106,"publishedAt":38},"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",[98,103],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000010","后端与接口",[9,107,108,109,110,111,112,19,113,114,115,116,117,118,119,120,121,122,123,27,26,124,125,126],"sign in with google web","sign","with","web","android","go","google workspace","google cloud","implement","policy","python","implementing","react","iam","permissions","buttons","secure","architectures","domain","runtimes",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":142,"publishedAt":38},"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",[133,134,137],{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":135,"categoryName":136,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[143,144,9,114,145,146,147,148,149,150,120,151,152,153,154,155,156,26,126,157,34],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":170,"publishedAt":38},"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",[164,165,168,169],{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":166,"categoryName":167,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":135,"categoryName":136,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},[171,172,173,174,114,175,176,177,178,179,180,181,182,34,183,184,185,120,186,121],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":38},"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",[],[194,195,196,197,198,199,200,201,117,202,203,204,205,206,207,180,208,209,210,34,211,212,185,213],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":223,"publishedAt":38},"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",[220,221,222],{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":135,"categoryName":136,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},[9,224,225,226,227,157,228,229,230,231,232,147,233,234,235,181,236,237,34,238,184],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","use","database","candidate",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":243,"categories":244,"keywords":247,"publishedAt":38},"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",[245,246],{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":135,"categoryName":136,"taxonomyType":101,"taxonomyTypeDesc":102},[248,22,27,249,9,174,250,114,175,251,252,253,254,34,255,184,120,256,257,258,259],"workload manager basics","basics","cli","review","vpc","resources","inspect","you","create","libraries","server","run"]