creator/Anthropic-Cybersecurity-Skills
1
0
Fork 0
mirror of https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git synced 2026-08-31 21:50:50 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs(skills): rewrite container-security descriptions to a uniform standard

Browse Source 
All 33 container-security skills now carry what it does, an explicit
"Use when" trigger, keywords, and a negative trigger naming the nearest
neighbour. Six collision clusters resolved by differentiating scope
rather than merging, so no skill is removed:

- kube-bench: running the tool vs interpreting findings into an audit
- Calico: portable upstream NetworkPolicy vs Calico-as-CNI vs Calico-only
  CRDs (GlobalNetworkPolicy, HostEndpoint, DNS egress)
- Falco: deploying and operating it vs authoring escape rules
- container escape: tool-agnostic runtime signals vs Falco rule syntax vs
  static posture audit vs offensive breakout
- Trivy: all-target platform and operator vs single-image scan
- Docker: images and Dockerfiles vs daemon.json vs the CIS audit script

Also replaces the templated "When to Use" boilerplate in these files,
including bullets that only restated the skill's own name.

Worst pair (Pod Security Standards vs Pod Security Admission) drops from
0.77 cosine to below the 0.45 threshold. Repo-wide: colliding pairs
60 -> 56, skills involved 105 -> 94.
This commit is contained in:
Mahipal
2026-08-23 17:15:30 +02:00
parent a81b233649
commit 6972fe933e
33 changed files with 300 additions and 149 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/performing-kubernetes-penetration-testing/SKILL.md
+8 -5
View File
@@ -1,10 +1,13 @@
---
name: performing-kubernetes-penetration-testing
description: Systematically evaluate Kubernetes 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
to identify misconfigurations leading to cluster compromise. Use for authorized
penetration tests or hands-on validation of Kubernetes security controls.
description: >-
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.
domain: cybersecurity
subdomain: container-security
tags: