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,11 +1,11 @@
---
name: implementing-patch-management-for-ot-systems
description: 'This skill covers implementing a structured patch management program
for OT/ICS environments where traditional IT patching approaches can cause process
disruption or safety hazards. It addresses vendor compatibility testing, risk-based
patch prioritization, staged deployment through test environments, maintenance window
coordination, rollback procedures, and compensating controls when patches cannot
be applied due to operational constraints or vendor restrictions.
description: 'Implements a structured patch management program for OT/ICS environments
where IT-style patching can cause process disruption or safety hazards, covering
vendor compatibility testing, risk-based prioritization, staged test deployment,
maintenance window coordination, rollback procedures, and compensating controls.
Use when planning or auditing patching for SCADA, PLCs, or other industrial control
systems.
'
domain: cybersecurity