[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79E0T84FPTQWSBA54RJVE3X":3,"skill-same:01M79E0T84FPTQWSBA54RJVE3X":56},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79E0T84FPTQWSBA54RJVE3X","gke-golden-path",null,"Provides GKE golden path configuration defaults, production readiness checklists, and cluster default patterns. Use when designing GKE clusters, verifying GKE production readiness, or checking configurations against GKE defaults. Don't use for setting up node autoscaling specifically (use gke-scaling instead).","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgke-golden-path\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gke-golden-path\ndescription: >-\n  Provides GKE golden path configuration defaults, production readiness\n  checklists, and cluster default patterns. Use when designing GKE clusters,\n  verifying GKE production readiness, or checking configurations against\n  GKE defaults. Don't use for setting up node autoscaling specifically (use\n  gke-scaling instead).\nmetadata:\n  category: Containers\n---\n\n# GKE Golden Path Configuration\n\nThe golden path is the recommended Autopilot configuration for production\nclusters. It defines sensible defaults — when the user requests different\nsettings, apply them and note relevant trade-offs.\n\n> **MCP Tools:** `get_cluster`, `create_cluster`, `update_cluster`\n\n## Rules\n\n1.  **Default to the golden path.** Use golden path values unless the user\n    requests otherwise. When deviating, note trade-offs but respect the user's\n    choice.\n2.  **Day-0 vs Day-1.** Flag Day-0 decisions (networking, private nodes,\n    subnets, IP allocation) prominently — they are hard\u002Fimpossible to change\n    after creation.\n3.  **Tool preference: MCP > gcloud > kubectl.** See the `gke-basics` skill's\n    CLI reference for full coverage matrix and override options. If the user\n    says \"use gcloud\" or \"use kubectl\", respect that for the session.\n4.  **Document decisions and rationale**, especially for Day-0 choices and\n    golden path deviations.\n\n## Required Inputs\n\nIf the user is unsure, use golden path defaults.\n\n-   **Project ID** (required)\n-   **Region** (required, e.g., `us-central1`)\n-   **Cluster name** (required)\n-   **Environment type**: dev\u002Ftest or production (defaults to production)\n-   **Networking**: bring-your-own VPC\u002Fsubnet or auto-create (default:\n    auto-create)\n-   **Scale expectations**: expected node\u002Fpod count, workload types\n-   **Cost constraints**: Spot VM tolerance, budget considerations\n\n## Always-Apply Defaults\n\nRecommended best practices applied by default. If the user requests a different\nsetting, apply it and briefly note the security or operational trade-off.\n\nSetting                                                            | Golden Path Value\n------------------------------------------------------------------ | -----------------\n`autopilot.enabled`                                                | `true`\n`privateClusterConfig.enablePrivateNodes`                          | `true`\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled` | `true`\n`secretManagerConfig.enabled` + `rotationInterval: 120s`           | `true`\n`rbacBindingConfig.enableInsecureBinding*`                         | `false` (both)\n`workloadIdentityConfig.workloadPool`                              | enabled\n`networkConfig.datapathProvider`                                   | `ADVANCED_DATAPATH`\n`networkConfig.dnsConfig.clusterDns`                               | `CLOUD_DNS`\n`autoscaling.autoscalingProfile`                                   | `OPTIMIZE_UTILIZATION`\n`verticalPodAutoscaling.enabled`                                   | `true`\n`monitoringConfig` components                                      | SYSTEM_COMPONENTS, STORAGE, POD, DEPLOYMENT, STATEFULSET, DAEMONSET, HPA, JOBSET, CADVISOR, KUBELET, DCGM, APISERVER, SCHEDULER, CONTROLLER_MANAGER\n`loggingConfig` components                                         | SYSTEM_COMPONENTS, WORKLOADS (enabled by default)\n`advancedDatapathObservabilityConfig.enableMetrics`                | `true`\n`nodeConfig.shieldedInstanceConfig.enableSecureBoot`               | `true`\n`nodeConfig.workloadMetadataConfig.mode`                           | `GKE_METADATA`\n`nodeConfig.gcfsConfig.enabled` \u002F `gvnic.enabled`                  | `true` \u002F `true`\n`addonsConfig.statefulHaConfig.enabled`                            | `true`\nStorage CSI drivers (Filestore, GCS FUSE, Parallelstore)           | enabled\nPod Security Standards                                             | `restricted` on production namespaces\n\n## Customer-Configurable Settings\n\nThese have golden path defaults but customers may deviate with valid\njustification. **Ask before changing.**\n\nSetting                                  | Default                             | Why Deviate\n---------------------------------------- | ----------------------------------- | -----------\n`dnsEndpointConfig.allowExternalTraffic` | `true`                              | Restrict if cluster only accessed from within VPC\n`autoIpamConfig` \u002F `createSubnetwork`    | `true` \u002F `true`                     | Customer has pre-existing VPC\u002Fsubnets\n`maxPodsPerNode`                         | `48`                                | `110` for high pod-density (costs more CIDR space)\n`subnetwork`                             | auto-created                        | Customer brings existing subnets\nMaintenance exclusion windows            | configured (NO_MINOR_UPGRADES, 1yr) | Customer-specific scheduling\n`nodeConfig.bootDisk.diskType`           | `pd-balanced`                       | `pd-ssd` for I\u002FO-intensive, `pd-standard` for cost\n`nodeConfig.machineType`                 | `ek-standard-8` (Autopilot)         | Varies by workload; use ComputeClasses\n\n## Guardrails\n\n-   Do not request or output secrets (tokens, keys, service account JSON).\n-   Discover project\u002Fcluster context via MCP tools or `gcloud config get-value\n    project` — don't ask users to paste project IDs.\n-   For Day-0 decisions, always ask clarifying questions before proceeding.\n-   For Day-1 features, propose golden path defaults with trade-offs and let the\n    customer confirm.\n-   Do not promise zero downtime; advise PDBs, health probes, replicas, and\n    staged upgrades.\n-   When auditing existing clusters, compare against golden path and report\n    deviations with severity and remediation.\n\n## Golden Path Config\n\nSee [golden-path-autopilot.yaml](.\u002Fassets\u002Fgolden-path-autopilot.yaml) for the\nfull cluster-level policy settings.\n","# GKE Golden Path Configuration\n\nThe golden path is the recommended Autopilot configuration for production\nclusters. It defines sensible defaults — when the user requests different\nsettings, apply them and note relevant trade-offs.\n\n> **MCP Tools:** `get_cluster`, `create_cluster`, `update_cluster`\n\n## Rules\n\n1.  **Default to the golden path.** Use golden path values unless the user\n    requests otherwise. When deviating, note trade-offs but respect the user's\n    choice.\n2.  **Day-0 vs Day-1.** Flag Day-0 decisions (networking, private nodes,\n    subnets, IP allocation) prominently — they are hard\u002Fimpossible to change\n    after creation.\n3.  **Tool preference: MCP > gcloud > kubectl.** See the `gke-basics` skill's\n    CLI reference for full coverage matrix and override options. If the user\n    says \"use gcloud\" or \"use kubectl\", respect that for the session.\n4.  **Document decisions and rationale**, especially for Day-0 choices and\n    golden path deviations.\n\n## Required Inputs\n\nIf the user is unsure, use golden path defaults.\n\n-   **Project ID** (required)\n-   **Region** (required, e.g., `us-central1`)\n-   **Cluster name** (required)\n-   **Environment type**: dev\u002Ftest or production (defaults to production)\n-   **Networking**: bring-your-own VPC\u002Fsubnet or auto-create (default:\n    auto-create)\n-   **Scale expectations**: expected node\u002Fpod count, workload types\n-   **Cost constraints**: Spot VM tolerance, budget considerations\n\n## Always-Apply Defaults\n\nRecommended best practices applied by default. If the user requests a different\nsetting, apply it and briefly note the security or operational trade-off.\n\nSetting                                                            | Golden Path Value\n------------------------------------------------------------------ | -----------------\n`autopilot.enabled`                                                | `true`\n`privateClusterConfig.enablePrivateNodes`                          | `true`\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled` | `true`\n`secretManagerConfig.enabled` + `rotationInterval: 120s`           | `true`\n`rbacBindingConfig.enableInsecureBinding*`                         | `false` (both)\n`workloadIdentityConfig.workloadPool`                              | enabled\n`networkConfig.datapathProvider`                                   | `ADVANCED_DATAPATH`\n`networkConfig.dnsConfig.clusterDns`                               | `CLOUD_DNS`\n`autoscaling.autoscalingProfile`                                   | `OPTIMIZE_UTILIZATION`\n`verticalPodAutoscaling.enabled`                                   | `true`\n`monitoringConfig` components                                      | SYSTEM_COMPONENTS, STORAGE, POD, DEPLOYMENT, STATEFULSET, DAEMONSET, HPA, JOBSET, CADVISOR, KUBELET, DCGM, APISERVER, SCHEDULER, CONTROLLER_MANAGER\n`loggingConfig` components                                         | SYSTEM_COMPONENTS, WORKLOADS (enabled by default)\n`advancedDatapathObservabilityConfig.enableMetrics`                | `true`\n`nodeConfig.shieldedInstanceConfig.enableSecureBoot`               | `true`\n`nodeConfig.workloadMetadataConfig.mode`                           | `GKE_METADATA`\n`nodeConfig.gcfsConfig.enabled` \u002F `gvnic.enabled`                  | `true` \u002F `true`\n`addonsConfig.statefulHaConfig.enabled`                            | `true`\nStorage CSI drivers (Filestore, GCS FUSE, Parallelstore)           | enabled\nPod Security Standards                                             | `restricted` on production namespaces\n\n## Customer-Configurable Settings\n\nThese have golden path defaults but customers may deviate with valid\njustification. **Ask before changing.**\n\nSetting                                  | Default                             | Why Deviate\n---------------------------------------- | ----------------------------------- | -----------\n`dnsEndpointConfig.allowExternalTraffic` | `true`                              | Restrict if cluster only accessed from within VPC\n`autoIpamConfig` \u002F `createSubnetwork`    | `true` \u002F `true`                     | Customer has pre-existing VPC\u002Fsubnets\n`maxPodsPerNode`                         | `48`                                | `110` for high pod-density (costs more CIDR space)\n`subnetwork`                             | auto-created                        | Customer brings existing subnets\nMaintenance exclusion windows            | configured (NO_MINOR_UPGRADES, 1yr) | Customer-specific scheduling\n`nodeConfig.bootDisk.diskType`           | `pd-balanced`                       | `pd-ssd` for I\u002FO-intensive, `pd-standard` for cost\n`nodeConfig.machineType`                 | `ek-standard-8` (Autopilot)         | Varies by workload; use ComputeClasses\n\n## Guardrails\n\n-   Do not request or output secrets (tokens, keys, service account JSON).\n-   Discover project\u002Fcluster context via MCP tools or `gcloud config get-value\n    project` — don't ask users to paste project IDs.\n-   For Day-0 decisions, always ask clarifying questions before proceeding.\n-   For Day-1 features, propose golden path defaults with trade-offs and let the\n    customer confirm.\n-   Do not promise zero downtime; advise PDBs, health probes, replicas, and\n    staged upgrades.\n-   When auditing existing clusters, compare against golden path and report\n    deviations with severity and remediation.\n\n## Golden Path Config\n\nSee [golden-path-autopilot.yaml](.\u002Fassets\u002Fgolden-path-autopilot.yaml) for the\nfull cluster-level policy settings.\n",{"name":5,"metadata":24,"description":7},{"category":25},"Containers","main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Programming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgke-golden-path",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill gke-golden-path",{"tool":42,"command":43},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill gke-golden-path",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill gke-golden-path","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgke-golden-path\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fgolden-path-autopilot.yaml","ASSET","资产文件",3733,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgke-golden-path\u002Fassets\u002Fgolden-path-autopilot.yaml",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\u002FSKILL.md",[],[],{"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":98,"publishedAt":19},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]