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.

skills/performing-docker-bench-security-assessment/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: performing-docker-bench-security-assessment
-description: Run Docker Bench for Security, the open-source CIS Docker Benchmark audit
-  script, to check host configuration, Docker daemon settings, container images, and
-  runtime configurations, then interpret pass/fail/warn results and remediate common
-  failures. Use when auditing Docker hosts for CIS Benchmark compliance, scheduling
-  recurring container security assessments, or validating container runtime hardening
-  controls.
+description: >-
+  Runs Docker Bench for Security, the open-source CIS Docker Benchmark audit script, across
+  host configuration, daemon settings, images, and runtime configuration, then interprets
+  pass/fail/warn output and remediates the common failures. Use when auditing Docker hosts for
+  CIS compliance, scheduling recurring container assessments, or validating runtime hardening
+  controls after a change. Keywords: docker-bench-security, CIS Docker Benchmark, audit
+  script, pass fail warn, host configuration, remediation. Do not use for applying the daemon
+  hardening itself - use hardening-docker-daemon-configuration.
 domain: cybersecurity
 subdomain: container-security
 tags: