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-image-provenance-verification-with-cosign
description: Signs and verifies container image provenance using Sigstore Cosign,
covering key-based and keyless OIDC-based signing (Fulcio, Rekor transparency log),
SLSA attestations, and enforcing signature verification via Kubernetes admission
control. Use when signing container images for supply chain security, setting
up keyless OIDC signing, attaching attestations, or enforcing verified-image-only
policies at admission in a Kubernetes cluster.
description: >-
Signs and verifies container image provenance with Sigstore Cosign, covering key-based and
keyless OIDC signing (Fulcio, Rekor transparency log), SLSA attestations, and enforcing
signature verification through Kubernetes admission control. Use when signing images for
supply chain security, setting up keyless OIDC signing, attaching attestations, or enforcing
a verified-images-only policy at admission. Keywords: Cosign, Sigstore, Fulcio, Rekor,
keyless, attestation, cosign verify, admission policy. Do not use for in-toto layout-based
pipeline attestation - use implementing-supply-chain-security-with-in-toto.
domain: cybersecurity
subdomain: container-security
tags: