Rewrite 548 skill descriptions to the activation rubric

Each rewritten description now states both what the skill does (concrete
capability, named tools/artifacts) and an explicit when-to-use trigger,
improving agent discovery/activation. Grounded in each skill's own body;
changes confined to the `description` field only (bodies and all other
frontmatter untouched). Produced by a gated audit->rewrite->recheck loop
(548 -> 0 flagged) with a sampled anti-invention check (0 ungrounded).

Schema: 817/817 pass. Framework-ID gate: 0 defects.
This commit is contained in:
Mahipal
2026-08-02 09:32:13 -07:00
parent 04a207702e
commit 2fb6a9faff
548 changed files with 2189 additions and 1915 deletions
@@ -1,8 +1,10 @@
---
name: performing-kubernetes-penetration-testing
description: Kubernetes penetration testing systematically evaluates cluster security
by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC,
network policies, and secrets. Using tools
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.
domain: cybersecurity
subdomain: container-security
tags: