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:
Mahipal
2026-08-23 17:15:30 +02:00
parent a81b233649
commit 6972fe933e
33 changed files with 300 additions and 149 deletions
@@ -1,11 +1,13 @@
---
name: implementing-container-image-minimal-base-with-distroless
description: Reduces container attack surface by building application images on Google
distroless base images that contain only the app runtime with no shell, package
manager, or OS utilities, using multi-stage Docker build patterns and debug/scanning
techniques for distroless containers. Use when hardening container images, cutting
attack surface in a container security architecture, or responding to a security
assessment that flags bloated base images.
description: >-
Reduces container attack surface by building application images on Google distroless base
images that ship only the application runtime - no shell, package manager, or OS utilities -
using multi-stage build patterns plus debugging and scanning techniques adapted to
distroless. Use when hardening container images, cutting attack surface in a container
architecture, or answering an assessment finding about bloated base images. Keywords:
distroless, multi-stage build, no shell, nonroot tag, debug image, scratch, attack surface.
Do not use for scanning an image for known CVEs - use scanning-docker-images-with-trivy.
domain: cybersecurity
subdomain: container-security
tags: