[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79E15WC6MDVJ9JVDJS1KD7B":3,"skill-same:01M79E15WC6MDVJ9JVDJS1KD7B":50},{"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},"01M79E15WC6MDVJ9JVDJS1KD7B","gke-networking",null,"Plans, configures, and manages GKE networking. Covers private clusters, VPC- native configurations, Gateway API, DNS, ingress\u002Fegress, Dataplane V2, and IP planning. Use when designing GKE networking layouts, configuring private clusters, setting up Gateway API, planning GKE IP ranges, or configuring GKE ingress\u002Fegress. Don't use for basic application routing that does not require dedicated network configuration.","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-networking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gke-networking\ndescription: >-\n  Plans, configures, and manages GKE networking. Covers private clusters, VPC-\n  native configurations, Gateway API, DNS, ingress\u002Fegress, Dataplane V2, and\n  IP planning. Use when designing GKE networking layouts, configuring private\n  clusters, setting up Gateway API, planning GKE IP ranges, or configuring GKE\n  ingress\u002Fegress. Don't use for basic application routing that does not\n  require dedicated network configuration.\nmetadata:\n  category: Networking\n---\n\n# GKE Networking\n\nThis reference covers networking configuration for GKE clusters. The golden path\nenforces private, VPC-native clusters with Dataplane V2.\n\n> **MCP Tools:** `get_cluster`, `update_cluster`, `apply_k8s_manifest`,\n> `get_k8s_resource`\n\n## Golden Path Networking Defaults\n\nSetting                                                              | Golden Path Value                  | Day-0\u002F1 | Notes\n-------------------------------------------------------------------- | ---------------------------------- | ------- | -----\n`privateClusterConfig.enablePrivateNodes`                            | `true`                             | Day-0   | Nodes have no public IPs\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled`   | `true`                             | Day-0   | Control plane only reachable via private endpoint or DNS\n`controlPlaneEndpointsConfig.dnsEndpointConfig.allowExternalTraffic` | `true`                             | Day-0   | Allows DNS-based access from outside VPC\n`networkConfig.datapathProvider`                                     | `ADVANCED_DATAPATH` (Dataplane V2) | Day-0   | eBPF-based, built-in Network Policy\n`networkConfig.dnsConfig.clusterDns`                                 | `CLOUD_DNS`                        | Day-0   | Managed DNS, more reliable than kube-dns\n`networkConfig.enableIntraNodeVisibility`                            | `true`                             | Day-1   | VPC Flow Logs for intra-node traffic\n`networkConfig.gatewayApiConfig.channel`                             | `CHANNEL_STANDARD`                 | Day-1   | Gateway API support\n`ipAllocationPolicy.autoIpamConfig.enabled`                          | `true`                             | Day-0   | Automatic IP range management\n`ipAllocationPolicy.createSubnetwork`                                | `true`                             | Day-0   | Auto-create dedicated subnet\n`defaultMaxPodsConstraint.maxPodsPerNode`                            | `48`                               | Day-0   | Conservative default; 110 for high density\n\n## Private Cluster Access Patterns\n\nThe golden path creates a private cluster. Users access it via:\n\n1.  **DNS endpoint (default)**: `allowExternalTraffic: true` enables access via\n    the cluster's DNS endpoint from outside the VPC. No VPN required.\n2.  **Private endpoint**: Direct access from within the VPC or via Cloud\n    VPN\u002FInterconnect.\n3.  **Authorized networks**: Add specific CIDRs to\n    `masterAuthorizedNetworksConfig` for IP-based access control.\n\n```bash\n# Access private cluster via DNS endpoint (golden path default)\ngcloud container clusters get-credentials \u003CCLUSTER_NAME> \\\n  --region \u003CREGION> --dns-endpoint \\\n  --quiet\n\n# Access via private endpoint (from within VPC)\ngcloud container clusters get-credentials \u003CCLUSTER_NAME> \\\n  --region \u003CREGION> --internal-ip \\\n  --quiet\n```\n\n## Bring-Your-Own VPC\u002FSubnet\n\nIf the customer has existing network infrastructure:\n\n```bash\ngcloud container clusters create-auto \u003CCLUSTER_NAME> \\\n  --region \u003CREGION> \\\n  --network \u003CVPC_NAME> \\\n  --subnetwork \u003CSUBNET_NAME> \\\n  --cluster-secondary-range-name \u003CPOD_RANGE> \\\n  --services-secondary-range-name \u003CSVC_RANGE> \\\n  --enable-private-nodes \\\n  --enable-master-authorized-networks \\\n  --quiet\n```\n\n> **Day-0 Warning**: VPC, subnet, and IP ranges cannot be changed after cluster\n> creation.\n\n## VPC-Native Mode Benefits\n\nVPC-native clusters route traffic natively using GCP Alias IP ranges. Key\nbenefits to cover:\n\n1.  **Scalability**: Traffic routes natively inside the VPC, bypassing the need\n    for custom routes and avoiding custom route limit bottlenecks.\n2.  **Direct VPC Integration**: Direct resource integration (e.g.\n    container-native load balancing).\n3.  **Avoiding IP Exhaustion**: Supports discontiguous IP ranges and optimizes\n    allocation, reducing the risk of exhausting subnet IP ranges.\n\n## IP Planning\n\n| Resource      | Golden Path  | Notes                                      |\n| ------------- | ------------ | ------------------------------------------ |\n| Pod CIDR      | `\u002F17` (auto) | ~32K pod IPs; size based on maxPodsPerNode |\n| Service CIDR  | `\u002F20` (auto) | ~4K service IPs                            |\n| Node subnet   | auto-created | \u002F20 recommended for growth                 |\n| Max pods\u002Fnode | 48           | Each node gets a \u002F25 pod range; set to 110 |\n:               :              : for \u002F24 per node                           :\n\n**Pod CIDR sizing rule of thumb:**\n\n-   `maxPodsPerNode=48` -> each node uses a `\u002F25` (128 IPs) from pod CIDR\n-   `maxPodsPerNode=110` -> each node uses a `\u002F24` (256 IPs) from pod CIDR\n-   Larger maxPodsPerNode = fewer nodes fit in a given CIDR\n\n## Ingress\n\n**Gateway API** (golden path, enabled via `gatewayApiConfig.channel:\nCHANNEL_STANDARD`):\n\n```yaml\napiVersion: gateway.networking.k8s.io\u002Fv1\nkind: Gateway\nmetadata:\n  name: external-http\nspec:\n  gatewayClassName: gke-l7-global-external-managed\n  listeners:\n  - name: http\n    protocol: HTTP\n    port: 80\n```\n\n**Alternatives:**\n\n-   `gke-l7-regional-external-managed` — regional external\n-   `gke-l7-rilb` — internal load balancer\n-   Istio service mesh — for advanced traffic management, mTLS\n\n## Egress\n\n-   Default: nodes use Cloud NAT for outbound internet access (private nodes\n    have no public IPs)\n-   For static egress IPs: configure Cloud NAT with manual IP allocation\n-   For restricted egress: route through a firewall appliance via custom routes\n\n## Network Policy\n\nDataplane V2 (golden path) provides built-in Network Policy enforcement — no\nadditional addon needed. Apply default-deny per namespace, then allow specific\nflows.\n\n> See the `gke-security` skill for default-deny policy and the\n> `gke-multitenancy` skill for per-team allow policies.\n\n## Cloud Armor (Recommended for Public-Facing Services)\n\nCloud Armor provides WAF and DDoS protection. **Not a golden path default** —\nrecommended for any service with public ingress. Link via `BackendConfig`:\n\n```yaml\n# 1. Create BackendConfig referencing your Cloud Armor policy\napiVersion: cloud.google.com\u002Fv1\nkind: BackendConfig\nmetadata:\n  name: my-backend-config\nspec:\n  securityPolicy:\n    name: my-cloud-armor-policy\n---\n# 2. Annotate your Service\n# cloud.google.com\u002Fbackend-config: '{\"default\": \"my-backend-config\"}'\n```\n\n## SSL, Container-Native LB, and PSC\n\n-   **Google-managed SSL certificates**: Use `ManagedCertificate` CRD with\n    Gateway API. Auto-provisions and renews.\n-   **Container-native LB**: Enabled by default on VPC-native clusters (golden\n    path). Targets pods via NEGs, bypassing iptables. Annotation:\n    `cloud.google.com\u002Fneg: '{\"ingress\": true}'`.\n-   **Private Service Connect (PSC)**: Use `ServiceAttachment` CRD to expose\n    services across VPCs without peering.\n","# GKE Networking\n\nThis reference covers networking configuration for GKE clusters. The golden path\nenforces private, VPC-native clusters with Dataplane V2.\n\n> **MCP Tools:** `get_cluster`, `update_cluster`, `apply_k8s_manifest`,\n> `get_k8s_resource`\n\n## Golden Path Networking Defaults\n\nSetting                                                              | Golden Path Value                  | Day-0\u002F1 | Notes\n-------------------------------------------------------------------- | ---------------------------------- | ------- | -----\n`privateClusterConfig.enablePrivateNodes`                            | `true`                             | Day-0   | Nodes have no public IPs\n`masterAuthorizedNetworksConfig.privateEndpointEnforcementEnabled`   | `true`                             | Day-0   | Control plane only reachable via private endpoint or DNS\n`controlPlaneEndpointsConfig.dnsEndpointConfig.allowExternalTraffic` | `true`                             | Day-0   | Allows DNS-based access from outside VPC\n`networkConfig.datapathProvider`                                     | `ADVANCED_DATAPATH` (Dataplane V2) | Day-0   | eBPF-based, built-in Network Policy\n`networkConfig.dnsConfig.clusterDns`                                 | `CLOUD_DNS`                        | Day-0   | Managed DNS, more reliable than kube-dns\n`networkConfig.enableIntraNodeVisibility`                            | `true`                             | Day-1   | VPC Flow Logs for intra-node traffic\n`networkConfig.gatewayApiConfig.channel`                             | `CHANNEL_STANDARD`                 | Day-1   | Gateway API support\n`ipAllocationPolicy.autoIpamConfig.enabled`                          | `true`                             | Day-0   | Automatic IP range management\n`ipAllocationPolicy.createSubnetwork`                                | `true`                             | Day-0   | Auto-create dedicated subnet\n`defaultMaxPodsConstraint.maxPodsPerNode`                            | `48`                               | Day-0   | Conservative default; 110 for high density\n\n## Private Cluster Access Patterns\n\nThe golden path creates a private cluster. Users access it via:\n\n1.  **DNS endpoint (default)**: `allowExternalTraffic: true` enables access via\n    the cluster's DNS endpoint from outside the VPC. No VPN required.\n2.  **Private endpoint**: Direct access from within the VPC or via Cloud\n    VPN\u002FInterconnect.\n3.  **Authorized networks**: Add specific CIDRs to\n    `masterAuthorizedNetworksConfig` for IP-based access control.\n\n```bash\n# Access private cluster via DNS endpoint (golden path default)\ngcloud container clusters get-credentials \u003CCLUSTER_NAME> \\\n  --region \u003CREGION> --dns-endpoint \\\n  --quiet\n\n# Access via private endpoint (from within VPC)\ngcloud container clusters get-credentials \u003CCLUSTER_NAME> \\\n  --region \u003CREGION> --internal-ip \\\n  --quiet\n```\n\n## Bring-Your-Own VPC\u002FSubnet\n\nIf the customer has existing network infrastructure:\n\n```bash\ngcloud container clusters create-auto \u003CCLUSTER_NAME> \\\n  --region \u003CREGION> \\\n  --network \u003CVPC_NAME> \\\n  --subnetwork \u003CSUBNET_NAME> \\\n  --cluster-secondary-range-name \u003CPOD_RANGE> \\\n  --services-secondary-range-name \u003CSVC_RANGE> \\\n  --enable-private-nodes \\\n  --enable-master-authorized-networks \\\n  --quiet\n```\n\n> **Day-0 Warning**: VPC, subnet, and IP ranges cannot be changed after cluster\n> creation.\n\n## VPC-Native Mode Benefits\n\nVPC-native clusters route traffic natively using GCP Alias IP ranges. Key\nbenefits to cover:\n\n1.  **Scalability**: Traffic routes natively inside the VPC, bypassing the need\n    for custom routes and avoiding custom route limit bottlenecks.\n2.  **Direct VPC Integration**: Direct resource integration (e.g.\n    container-native load balancing).\n3.  **Avoiding IP Exhaustion**: Supports discontiguous IP ranges and optimizes\n    allocation, reducing the risk of exhausting subnet IP ranges.\n\n## IP Planning\n\n| Resource      | Golden Path  | Notes                                      |\n| ------------- | ------------ | ------------------------------------------ |\n| Pod CIDR      | `\u002F17` (auto) | ~32K pod IPs; size based on maxPodsPerNode |\n| Service CIDR  | `\u002F20` (auto) | ~4K service IPs                            |\n| Node subnet   | auto-created | \u002F20 recommended for growth                 |\n| Max pods\u002Fnode | 48           | Each node gets a \u002F25 pod range; set to 110 |\n:               :              : for \u002F24 per node                           :\n\n**Pod CIDR sizing rule of thumb:**\n\n-   `maxPodsPerNode=48` -> each node uses a `\u002F25` (128 IPs) from pod CIDR\n-   `maxPodsPerNode=110` -> each node uses a `\u002F24` (256 IPs) from pod CIDR\n-   Larger maxPodsPerNode = fewer nodes fit in a given CIDR\n\n## Ingress\n\n**Gateway API** (golden path, enabled via `gatewayApiConfig.channel:\nCHANNEL_STANDARD`):\n\n```yaml\napiVersion: gateway.networking.k8s.io\u002Fv1\nkind: Gateway\nmetadata:\n  name: external-http\nspec:\n  gatewayClassName: gke-l7-global-external-managed\n  listeners:\n  - name: http\n    protocol: HTTP\n    port: 80\n```\n\n**Alternatives:**\n\n-   `gke-l7-regional-external-managed` — regional external\n-   `gke-l7-rilb` — internal load balancer\n-   Istio service mesh — for advanced traffic management, mTLS\n\n## Egress\n\n-   Default: nodes use Cloud NAT for outbound internet access (private nodes\n    have no public IPs)\n-   For static egress IPs: configure Cloud NAT with manual IP allocation\n-   For restricted egress: route through a firewall appliance via custom routes\n\n## Network Policy\n\nDataplane V2 (golden path) provides built-in Network Policy enforcement — no\nadditional addon needed. Apply default-deny per namespace, then allow specific\nflows.\n\n> See the `gke-security` skill for default-deny policy and the\n> `gke-multitenancy` skill for per-team allow policies.\n\n## Cloud Armor (Recommended for Public-Facing Services)\n\nCloud Armor provides WAF and DDoS protection. **Not a golden path default** —\nrecommended for any service with public ingress. Link via `BackendConfig`:\n\n```yaml\n# 1. Create BackendConfig referencing your Cloud Armor policy\napiVersion: cloud.google.com\u002Fv1\nkind: BackendConfig\nmetadata:\n  name: my-backend-config\nspec:\n  securityPolicy:\n    name: my-cloud-armor-policy\n---\n# 2. Annotate your Service\n# cloud.google.com\u002Fbackend-config: '{\"default\": \"my-backend-config\"}'\n```\n\n## SSL, Container-Native LB, and PSC\n\n-   **Google-managed SSL certificates**: Use `ManagedCertificate` CRD with\n    Gateway API. Auto-provisions and renews.\n-   **Container-native LB**: Enabled by default on VPC-native clusters (golden\n    path). Targets pods via NEGs, bypassing iptables. Annotation:\n    `cloud.google.com\u002Fneg: '{\"ingress\": true}'`.\n-   **Private Service Connect (PSC)**: Use `ServiceAttachment` CRD to expose\n    services across VPCs without peering.\n",{"name":5,"metadata":24,"description":7},{"category":25},"Networking","main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Programming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgke-networking",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-networking",{"tool":42,"command":43},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill gke-networking",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill gke-networking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FCloud_DevOps_and_Infrastructure\u002FGoogle_Cloud_and_GKE\u002Fgke-networking\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]