[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7525Y6DY74SWPXKWDGX4F":3,"skill-same:01M7D7525Y6DY74SWPXKWDGX4F":65},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":5,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7D7525Y6DY74SWPXKWDGX4F","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).","tangyixiao\u002Ftangyixiao-skills","tangyixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115929632?v=4","01M7D582YK6A4M63CAK4CSY4EW","Tang Yixiao","01M7D582Z64DMRSYR872SR34SA",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-platform-security\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-platform-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gke-platform-security\ndescription: Plans, configures, and hardens platform-level Google Kubernetes Engine\n  (GKE) cluster security. Covers cluster add-ons (Secret Manager enablement), RBAC\n  hardening (disabling insecure bindings, audit tools), Binary Authorization, Secrets\n  Encryption (--database-encryption-key), Security Posture (--security-posture), enabling\n  Shielded Nodes, GKE Sandbox cluster enablement, GKE IAM roles, and cross-service\n  authentication IAM patterns. Use when securing cluster control planes, hardening\n  GKE RBAC, enabling Shielded Nodes, enabling GKE Sandbox runtime, enabling cluster-wide\n  security add-ons, or managing GKE IAM roles. Don't use for Workload Identity (use\n  gke-workload-identity) or workload-level security (SecretProviderClass, PSS, NetPol,\n  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":25,"description":7},{"version":26,"category":27},"1.0.2","Security","main","2a870f189175a48c39f5f7e26a6d93b0be9cd13b",0,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills","https:\u002F\u002Ftangyixiao.github.io\u002Ftangyixiao-skills\u002F","https:\u002F\u002Fgithub.com\u002Ftangyixiao","http:\u002F\u002Fwww.sxyz.net\u002F","I am Tang Yixiao, a student in Shaoxing No.1 High School. I am eager to learn on GitHub and contribute my part to this community.","2026-11-11 15:45:59",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-platform-security",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-platform-security",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-platform-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-platform-security\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"INSTALL-SOURCE.json","REFERENCE","参考文档",523,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-platform-security\u002FINSTALL-SOURCE.json",{"path":58,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fattribution.md",1903,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-platform-security\u002Freferences\u002Fattribution.md",[66,74,83,91,99,107],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M7D8JK8FYBFNNAJXWD89CFH7","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M7D8JG8ERGGQQAMX0DWCG9GR","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","MIT","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M7D8JE672GW3EHSE8EF185M4","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M7D8JBK572YDFMND8Q6CEYJW","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7D8J5QPWEXX61EGBKYH73R8","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M7D8J36YWC8WZS5DK5AH03CD","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FSKILL.md",[],[]]