mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-30 05:09:41 +03:00
docs(skills): rewrite container-security descriptions to a uniform standard
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:
@@ -1,11 +1,13 @@
|
||||
---
|
||||
name: securing-helm-chart-deployments
|
||||
description: Secures Helm chart deployments by verifying chart signatures and provenance,
|
||||
rendering and scanning templates for misconfigurations with helm lint, enforcing
|
||||
pod security contexts in values.yaml, managing secrets via external stores instead
|
||||
of Helm values, and scoping RBAC for Helm operations in a CI/CD pipeline. Use when
|
||||
deploying Helm charts to Kubernetes or when a security review of chart provenance,
|
||||
templates, or release RBAC is needed.
|
||||
description: >-
|
||||
Secures Helm chart deployments by verifying chart signatures and provenance, rendering and
|
||||
linting templates for misconfiguration, enforcing pod security contexts through values.yaml,
|
||||
moving secrets into an external store instead of Helm values, and scoping RBAC for Helm
|
||||
operations in CI/CD. Use when deploying charts to Kubernetes or reviewing chart provenance,
|
||||
templates, or release RBAC. Keywords: Helm, provenance file, helm verify, helm lint,
|
||||
values.yaml, Tiller-less, release RBAC, external secrets. Do not use for scanning the
|
||||
rendered manifests themselves - use scanning-kubernetes-manifests-with-kubesec.
|
||||
domain: cybersecurity
|
||||
subdomain: container-security
|
||||
tags:
|
||||
|
||||
Reference in New Issue
Block a user