[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B54RFRFT4DN1J8RFPK04MS":3,"skill-same:01M7B54RFRFT4DN1J8RFPK04MS":79},{"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":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7B54RFRFT4DN1J8RFPK04MS","benchmarking-kubernetes-with-kube-bench",null,"Installs and runs the kube-bench tool against a Kubernetes cluster as a Job, DaemonSet, or standalone binary, selecting the correct benchmark version and targets (control plane, etcd, kubelet, worker nodes) and emitting JSON or JUnit output for pipelines. Use when setting kube-bench up for the first time, choosing which benchmark version and node targets to run, wiring it into CI, or troubleshooting skipped or misdetected checks. Keywords: kube-bench, DaemonSet, --benchmark, --targets, JSON output, JUnit, CI integration. Do not use for interpreting the findings or producing an audit report - 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\u002Fbenchmarking-kubernetes-with-kube-bench\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: benchmarking-kubernetes-with-kube-bench\ndescription: >-\n  Installs and runs the kube-bench tool against a Kubernetes cluster as a Job, DaemonSet, or\n  standalone binary, selecting the correct benchmark version and targets (control plane, etcd,\n  kubelet, worker nodes) and emitting JSON or JUnit output for pipelines. Use when setting\n  kube-bench up for the first time, choosing which benchmark version and node targets to run,\n  wiring it into CI, or troubleshooting skipped or misdetected checks. Keywords: kube-bench,\n  DaemonSet, --benchmark, --targets, JSON output, JUnit, CI integration. Do not use for\n  interpreting the findings or producing an audit report - use\n  performing-kubernetes-cis-benchmark-with-kube-bench.\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- kubernetes\n- kube-bench\n- cis-benchmark\n- container-security\n- hardening\n- compliance\n- cluster-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\nmitre_attack:\n- T1610\n---\n# Benchmarking Kubernetes with kube-bench\n\n## Overview\n\nkube-bench (by Aqua Security) is an open-source tool that checks whether a Kubernetes cluster is deployed securely by running the checks documented in the **CIS Kubernetes Benchmark**. It inspects the control-plane components (API server, controller manager, scheduler, etcd), the kubelet and worker-node configuration, and cluster-wide policy settings, then reports each check as PASS, FAIL, WARN, or INFO with a remediation recommendation drawn directly from the CIS guidance. Tests are configuration-driven YAML files, so kube-bench tracks new Kubernetes versions and benchmark revisions and supports managed distributions (EKS, GKE, AKS, ACK, OpenShift, RKE, k3s).\n\nHardening a cluster against the CIS Benchmark directly reduces the attack surface for **T1610 (Deploy Container)**, where an adversary deploys a container to execute code or evade defenses — for example by abusing privileged containers, host namespaces, anonymous API access, or insecure kubelet settings that an unhardened cluster leaves exposed.\n\nkube-bench can run as a standalone binary on a node, inside a container, or — most commonly — as a Kubernetes Job whose pod has the host filesystem mounted so it can read the relevant config files. Output is available as human-readable text, JSON, JUnit, or AWS Security Finding Format (ASFF) and can be pushed to a PostgreSQL database for trend tracking.\n\n## When to Use\n\n- When establishing a security baseline for a new Kubernetes cluster against the CIS Kubernetes Benchmark.\n- When performing periodic compliance audits of control-plane and node hardening.\n- When validating remediation after applying hardening changes (re-run to confirm checks now PASS).\n- When integrating cluster compliance scanning into CI\u002FCD or a continuous monitoring pipeline.\n- When preparing evidence for SOC 2, PCI DSS, or internal hardening compliance.\n\n## Prerequisites\n\n- Access to the cluster: either SSH access to a control-plane\u002Fworker node (binary mode) or `kubectl` with permission to create Jobs (in-cluster mode).\n- Knowledge of the cluster's Kubernetes version (kube-bench auto-detects, or specify with `--version` \u002F `--benchmark`).\n- Install kube-bench (Aqua Security official methods):\n\n```bash\n# Binary release (Linux)\nKB_VERSION=0.10.7\ncurl -L -o kube-bench.tgz \\\n  \"https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench\u002Freleases\u002Fdownload\u002Fv${KB_VERSION}\u002Fkube-bench_${KB_VERSION}_linux_amd64.tar.gz\"\ntar -xzf kube-bench.tgz\nsudo mv kube-bench \u002Fusr\u002Flocal\u002Fbin\u002F\nsudo cp -R cfg \u002Fetc\u002Fkube-bench\u002Fcfg\n\n# Via Go install\ngo install github.com\u002Faquasecurity\u002Fkube-bench@latest\n\n# Run as a one-off container directly on a node (mounts host config)\ndocker run --rm --pid=host \\\n  -v \u002Fetc:\u002Fetc:ro -v \u002Fvar:\u002Fvar:ro \\\n  -t docker.io\u002Faquasec\u002Fkube-bench:latest run --targets node\n\n# Verify\nkube-bench version\n```\n\n## Objectives\n\n- Run kube-bench against the appropriate benchmark for the cluster's Kubernetes version.\n- Scan control-plane (master), node, etcd, control-plane policies, and managed-service targets.\n- Produce machine-readable JSON\u002FJUnit output for pipelines and dashboards.\n- Triage FAIL and WARN results and apply CIS remediation guidance.\n- Re-run to validate that remediations now PASS.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Name | Tactic | Relevance |\n|--------------|------|--------|-----------|\n| T1610 | Deploy Container | Execution \u002F Defense Evasion | CIS Benchmark hardening enforced by kube-bench restricts privileged\u002Fhost-namespace deployments, anonymous API access, and insecure kubelet settings that adversaries abuse when deploying malicious containers. |\n\n## Workflow\n\n### 1. Run the default scan (auto-detect)\n\nRun all applicable targets, letting kube-bench detect the Kubernetes version and benchmark:\n\n```bash\nsudo kube-bench\n```\n\n### 2. Run as a Kubernetes Job (in-cluster)\n\nApply the provided Job manifest from the kube-bench repo and read the results from the pod logs:\n\n```bash\n# General-purpose job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\n\n# Wait, then retrieve results\nkubectl get pods -l app=kube-bench\nkubectl logs -l app=kube-bench\n\n# Platform-specific jobs are available, e.g. EKS:\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-eks.yaml\n```\n\n### 3. Target specific components\n\nUse `run --targets` to scope the scan to particular component groups:\n\n```bash\n# Control-plane (API server, scheduler, controller manager)\nsudo kube-bench run --targets master\n\n# Worker node (kubelet, proxy)\nsudo kube-bench run --targets node\n\n# etcd datastore\nsudo kube-bench run --targets etcd\n\n# Cluster-wide policies (RBAC, pod security, network policy)\nsudo kube-bench run --targets policies\n\n# Combine multiple targets\nsudo kube-bench run --targets master,node,etcd,policies\n```\n\n### 4. Pin a specific benchmark or Kubernetes version\n\nWhen auto-detection is wrong or you must audit against a specific revision, pin the benchmark explicitly:\n\n```bash\n# Pin to a specific CIS benchmark revision\nsudo kube-bench run --benchmark cis-1.8\n\n# Or map by Kubernetes version\nsudo kube-bench --version 1.27\n\n# Managed\u002Fdistribution-specific benchmarks\nsudo kube-bench run --benchmark eks-1.5.0\nsudo kube-bench run --benchmark gke-1.6.0\nsudo kube-bench run --benchmark rke2-cis-1.7\n```\n\n### 5. Run or skip individual checks\n\nFocus on or exclude specific check IDs during remediation cycles:\n\n```bash\n# Run only specific checks\nsudo kube-bench run --targets master --check 1.2.1,1.2.2\n\n# Skip noisy\u002Fknown-accepted checks\nsudo kube-bench run --targets node --skip 4.2.6\n```\n\n### 6. Produce machine-readable output\n\nEmit JSON or JUnit for ingestion into pipelines, SIEM, or dashboards, and write to a file:\n\n```bash\n# JSON to a file\nsudo kube-bench run --targets master,node --json --outputfile kube-bench-report.json\n\n# JUnit (for CI test reporting)\nsudo kube-bench --junit --outputfile kube-bench-junit.xml\n\n# AWS Security Finding Format (for Security Hub)\nsudo kube-bench run --targets node --asff\n```\n\n### 7. Triage and remediate FAIL\u002FWARN findings\n\nEach failing check prints a remediation. Apply the CIS-recommended fix on the node\u002Fmanifest, for example tightening API server flags in the static pod manifest:\n\n```bash\n# Example remediation for a common control-plane FAIL:\n# CIS 1.2.x — ensure anonymous-auth is disabled on the API server.\n# Edit the static pod manifest and set the flag:\nsudo vi \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\n#   - --anonymous-auth=false\n# The kubelet restarts the static pod automatically.\n\n# Example node remediation — kubelet config file permissions (CIS 4.1.x):\nsudo chmod 600 \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\nsudo chown root:root \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\n```\n\n### 8. Re-validate after remediation\n\nRe-run the relevant target and confirm the previously failing checks now PASS, then track the score over time:\n\n```bash\nsudo kube-bench run --targets master --check 1.2.1 --json --outputfile recheck.json\n\n# Optional: persist results to PostgreSQL for trend tracking\nsudo kube-bench run --targets master,node --pgsql\n```\n\n## Tools and Resources\n\n| Tool \u002F Resource | Purpose | Link |\n|------------------|---------|------|\n| kube-bench | CIS Kubernetes Benchmark checker | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench |\n| kube-bench docs | Running \u002F platforms \u002F flags | https:\u002F\u002Faquasecurity.github.io\u002Fkube-bench\u002F |\n| CIS Kubernetes Benchmark | Source hardening standard | https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes |\n| Trivy Operator | Continuous in-cluster compliance + vuln scanning | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy-operator |\n| kube-hunter | Complementary penetration-testing tool | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-hunter |\n\n## Validation Criteria\n\n- [ ] kube-bench installed (`kube-bench version`) or running as a Job.\n- [ ] Scan run against the correct benchmark for the cluster's Kubernetes version.\n- [ ] master, node, etcd, and policies targets each scanned.\n- [ ] JSON\u002FJUnit output produced for pipeline\u002Fdashboard ingestion.\n- [ ] FAIL and WARN findings triaged and prioritized.\n- [ ] CIS remediation applied to control-plane manifests and node configs.\n- [ ] Re-run confirms previously failing checks now PASS.\n- [ ] Results tracked over time (file archive or PostgreSQL).\n","# Benchmarking Kubernetes with kube-bench\n\n## Overview\n\nkube-bench (by Aqua Security) is an open-source tool that checks whether a Kubernetes cluster is deployed securely by running the checks documented in the **CIS Kubernetes Benchmark**. It inspects the control-plane components (API server, controller manager, scheduler, etcd), the kubelet and worker-node configuration, and cluster-wide policy settings, then reports each check as PASS, FAIL, WARN, or INFO with a remediation recommendation drawn directly from the CIS guidance. Tests are configuration-driven YAML files, so kube-bench tracks new Kubernetes versions and benchmark revisions and supports managed distributions (EKS, GKE, AKS, ACK, OpenShift, RKE, k3s).\n\nHardening a cluster against the CIS Benchmark directly reduces the attack surface for **T1610 (Deploy Container)**, where an adversary deploys a container to execute code or evade defenses — for example by abusing privileged containers, host namespaces, anonymous API access, or insecure kubelet settings that an unhardened cluster leaves exposed.\n\nkube-bench can run as a standalone binary on a node, inside a container, or — most commonly — as a Kubernetes Job whose pod has the host filesystem mounted so it can read the relevant config files. Output is available as human-readable text, JSON, JUnit, or AWS Security Finding Format (ASFF) and can be pushed to a PostgreSQL database for trend tracking.\n\n## When to Use\n\n- When establishing a security baseline for a new Kubernetes cluster against the CIS Kubernetes Benchmark.\n- When performing periodic compliance audits of control-plane and node hardening.\n- When validating remediation after applying hardening changes (re-run to confirm checks now PASS).\n- When integrating cluster compliance scanning into CI\u002FCD or a continuous monitoring pipeline.\n- When preparing evidence for SOC 2, PCI DSS, or internal hardening compliance.\n\n## Prerequisites\n\n- Access to the cluster: either SSH access to a control-plane\u002Fworker node (binary mode) or `kubectl` with permission to create Jobs (in-cluster mode).\n- Knowledge of the cluster's Kubernetes version (kube-bench auto-detects, or specify with `--version` \u002F `--benchmark`).\n- Install kube-bench (Aqua Security official methods):\n\n```bash\n# Binary release (Linux)\nKB_VERSION=0.10.7\ncurl -L -o kube-bench.tgz \\\n  \"https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench\u002Freleases\u002Fdownload\u002Fv${KB_VERSION}\u002Fkube-bench_${KB_VERSION}_linux_amd64.tar.gz\"\ntar -xzf kube-bench.tgz\nsudo mv kube-bench \u002Fusr\u002Flocal\u002Fbin\u002F\nsudo cp -R cfg \u002Fetc\u002Fkube-bench\u002Fcfg\n\n# Via Go install\ngo install github.com\u002Faquasecurity\u002Fkube-bench@latest\n\n# Run as a one-off container directly on a node (mounts host config)\ndocker run --rm --pid=host \\\n  -v \u002Fetc:\u002Fetc:ro -v \u002Fvar:\u002Fvar:ro \\\n  -t docker.io\u002Faquasec\u002Fkube-bench:latest run --targets node\n\n# Verify\nkube-bench version\n```\n\n## Objectives\n\n- Run kube-bench against the appropriate benchmark for the cluster's Kubernetes version.\n- Scan control-plane (master), node, etcd, control-plane policies, and managed-service targets.\n- Produce machine-readable JSON\u002FJUnit output for pipelines and dashboards.\n- Triage FAIL and WARN results and apply CIS remediation guidance.\n- Re-run to validate that remediations now PASS.\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Name | Tactic | Relevance |\n|--------------|------|--------|-----------|\n| T1610 | Deploy Container | Execution \u002F Defense Evasion | CIS Benchmark hardening enforced by kube-bench restricts privileged\u002Fhost-namespace deployments, anonymous API access, and insecure kubelet settings that adversaries abuse when deploying malicious containers. |\n\n## Workflow\n\n### 1. Run the default scan (auto-detect)\n\nRun all applicable targets, letting kube-bench detect the Kubernetes version and benchmark:\n\n```bash\nsudo kube-bench\n```\n\n### 2. Run as a Kubernetes Job (in-cluster)\n\nApply the provided Job manifest from the kube-bench repo and read the results from the pod logs:\n\n```bash\n# General-purpose job\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob.yaml\n\n# Wait, then retrieve results\nkubectl get pods -l app=kube-bench\nkubectl logs -l app=kube-bench\n\n# Platform-specific jobs are available, e.g. EKS:\nkubectl apply -f https:\u002F\u002Fraw.githubusercontent.com\u002Faquasecurity\u002Fkube-bench\u002Fmain\u002Fjob-eks.yaml\n```\n\n### 3. Target specific components\n\nUse `run --targets` to scope the scan to particular component groups:\n\n```bash\n# Control-plane (API server, scheduler, controller manager)\nsudo kube-bench run --targets master\n\n# Worker node (kubelet, proxy)\nsudo kube-bench run --targets node\n\n# etcd datastore\nsudo kube-bench run --targets etcd\n\n# Cluster-wide policies (RBAC, pod security, network policy)\nsudo kube-bench run --targets policies\n\n# Combine multiple targets\nsudo kube-bench run --targets master,node,etcd,policies\n```\n\n### 4. Pin a specific benchmark or Kubernetes version\n\nWhen auto-detection is wrong or you must audit against a specific revision, pin the benchmark explicitly:\n\n```bash\n# Pin to a specific CIS benchmark revision\nsudo kube-bench run --benchmark cis-1.8\n\n# Or map by Kubernetes version\nsudo kube-bench --version 1.27\n\n# Managed\u002Fdistribution-specific benchmarks\nsudo kube-bench run --benchmark eks-1.5.0\nsudo kube-bench run --benchmark gke-1.6.0\nsudo kube-bench run --benchmark rke2-cis-1.7\n```\n\n### 5. Run or skip individual checks\n\nFocus on or exclude specific check IDs during remediation cycles:\n\n```bash\n# Run only specific checks\nsudo kube-bench run --targets master --check 1.2.1,1.2.2\n\n# Skip noisy\u002Fknown-accepted checks\nsudo kube-bench run --targets node --skip 4.2.6\n```\n\n### 6. Produce machine-readable output\n\nEmit JSON or JUnit for ingestion into pipelines, SIEM, or dashboards, and write to a file:\n\n```bash\n# JSON to a file\nsudo kube-bench run --targets master,node --json --outputfile kube-bench-report.json\n\n# JUnit (for CI test reporting)\nsudo kube-bench --junit --outputfile kube-bench-junit.xml\n\n# AWS Security Finding Format (for Security Hub)\nsudo kube-bench run --targets node --asff\n```\n\n### 7. Triage and remediate FAIL\u002FWARN findings\n\nEach failing check prints a remediation. Apply the CIS-recommended fix on the node\u002Fmanifest, for example tightening API server flags in the static pod manifest:\n\n```bash\n# Example remediation for a common control-plane FAIL:\n# CIS 1.2.x — ensure anonymous-auth is disabled on the API server.\n# Edit the static pod manifest and set the flag:\nsudo vi \u002Fetc\u002Fkubernetes\u002Fmanifests\u002Fkube-apiserver.yaml\n#   - --anonymous-auth=false\n# The kubelet restarts the static pod automatically.\n\n# Example node remediation — kubelet config file permissions (CIS 4.1.x):\nsudo chmod 600 \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\nsudo chown root:root \u002Fetc\u002Fkubernetes\u002Fkubelet\u002Fkubelet-config.json\n```\n\n### 8. Re-validate after remediation\n\nRe-run the relevant target and confirm the previously failing checks now PASS, then track the score over time:\n\n```bash\nsudo kube-bench run --targets master --check 1.2.1 --json --outputfile recheck.json\n\n# Optional: persist results to PostgreSQL for trend tracking\nsudo kube-bench run --targets master,node --pgsql\n```\n\n## Tools and Resources\n\n| Tool \u002F Resource | Purpose | Link |\n|------------------|---------|------|\n| kube-bench | CIS Kubernetes Benchmark checker | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-bench |\n| kube-bench docs | Running \u002F platforms \u002F flags | https:\u002F\u002Faquasecurity.github.io\u002Fkube-bench\u002F |\n| CIS Kubernetes Benchmark | Source hardening standard | https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fkubernetes |\n| Trivy Operator | Continuous in-cluster compliance + vuln scanning | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Ftrivy-operator |\n| kube-hunter | Complementary penetration-testing tool | https:\u002F\u002Fgithub.com\u002Faquasecurity\u002Fkube-hunter |\n\n## Validation Criteria\n\n- [ ] kube-bench installed (`kube-bench version`) or running as a Job.\n- [ ] Scan run against the correct benchmark for the cluster's Kubernetes version.\n- [ ] master, node, etcd, and policies targets each scanned.\n- [ ] JSON\u002FJUnit output produced for pipeline\u002Fdashboard ingestion.\n- [ ] FAIL and WARN findings triaged and prioritized.\n- [ ] CIS remediation applied to control-plane manifests and node configs.\n- [ ] Re-run confirms previously failing checks now PASS.\n- [ ] Results tracked over time (file archive or PostgreSQL).\n",{"name":5,"tags":24,"author":32,"domain":33,"license":14,"version":34,"nist_csf":35,"subdomain":28,"description":7,"mitre_attack":37},[25,26,27,28,29,30,31],"kubernetes","kube-bench","cis-benchmark","container-security","hardening","compliance","cluster-security","mahipal","cybersecurity","1.0",[36],"PR.PS-01",[38],"T1610","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill benchmarking-kubernetes-with-kube-bench",{"tool":51,"command":52},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill benchmarking-kubernetes-with-kube-bench",{"tool":54,"command":55},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill benchmarking-kubernetes-with-kube-bench","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002FSKILL.md",true,[59,63,69,73],{"path":60,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fapi-reference.md","REFERENCE","参考文档",2969,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002Freferences\u002Fapi-reference.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fstandards.md",1650,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002Freferences\u002Fstandards.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fagent.py","SCRIPT","脚本",5717,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbenchmarking-kubernetes-with-kube-bench\u002Fscripts\u002Fagent.py",[80,88,95,102,109,116],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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",[],[]]