[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EF7BB9SC1SC9PP3CT4JRWV":3,"skill-same:01M7EF7BB9SC1SC9PP3CT4JRWV":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M7EF7BB9SC1SC9PP3CT4JRWV","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\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":15,"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","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fbenchmarking-kubernetes-with-kube-bench",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill benchmarking-kubernetes-with-kube-bench",{"tool":53,"command":54},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill benchmarking-kubernetes-with-kube-bench",{"tool":56,"command":57},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill benchmarking-kubernetes-with-kube-bench","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbenchmarking-kubernetes-with-kube-bench\u002FSKILL.md",true,[61,67],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fapi-reference.md","REFERENCE","参考文档",2969,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbenchmarking-kubernetes-with-kube-bench\u002Freferences\u002Fapi-reference.md",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fstandards.md",1650,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbenchmarking-kubernetes-with-kube-bench\u002Freferences\u002Fstandards.md",[72,81,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":82,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":80},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":80},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":80},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":80},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":80},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]