[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D77Q9V095ESBFPPE46YAEB":3,"skill-same:01M7D77Q9V095ESBFPPE46YAEB":81},{"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},"01M7D77Q9V095ESBFPPE46YAEB","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).","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-workload-security\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gke-workload-security\ndescription: Audits, configures, and hardens workload-level security controls for\n  Google 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\n  Secret Manager secrets via CSI (`SecretProviderClass`). Use when auditing workload\n  security posture, isolating namespaces, applying pod security standards, or configuring\n  network policies and secret volume mounts. Don't use for Workload Identity (use\n  gke-workload-identity), cluster-wide control plane security, RBAC hardening, Binary\n  Authorization, Shielded Nodes, or enabling platform-level GKE add-ons (use gke-platform-security\n  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":25,"description":7},{"version":26,"category":27},"1.0.3","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-workload-security",{"tool":43,"command":44},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-workload-security",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill gke-workload-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002FSKILL.md",true,[51,57,61,67,71,75],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Fdefault-deny-netpol.yaml","ASSET","资产文件",235,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002Fassets\u002Fdefault-deny-netpol.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fworkload-identity-pod.yaml",1207,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002Fassets\u002Fworkload-identity-pod.yaml",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"INSTALL-SOURCE.json","REFERENCE","参考文档",523,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002FINSTALL-SOURCE.json",{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":16},"LICENSE","许可证",11358,{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fattribution.md",1903,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002Freferences\u002Fattribution.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Faudit_cluster.sh","SCRIPT","脚本",2261,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fgke-workload-security\u002Fscripts\u002Faudit_cluster.sh",[82,90,99,107,115,123],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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",[],[]]