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,9 +1,10 @@
---
name: performing-bandwidth-throttling-attack-simulation
description: 'Simulates bandwidth throttling and network degradation attacks using
tc, iperf3, and Scapy in authorized environments to test quality-of-service controls,
application resilience, and network monitoring detection of traffic manipulation
attacks.
description: 'Simulate bandwidth throttling and network degradation attacks using tc,
iperf3, and Scapy in authorized lab environments to test QoS controls, application
resilience, and monitoring detection of traffic manipulation. Use when validating
how VoIP, video, or other real-time applications and network monitoring tools respond
to degraded bandwidth or slowloris-style throttling attacks.
'
domain: cybersecurity