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.

skills/implementing-ot-incident-response-playbook/SKILL.md

@@ -1,9 +1,11 @@
 ---
 name: implementing-ot-incident-response-playbook
-description: 'Develop and implement OT-specific incident response playbooks aligned
-  with SANS PICERL framework, IEC 62443, and NIST SP 800-82 that address unique ICS
-  challenges including safety-critical systems, limited downtime tolerance, and coordination
-  between IT SOC, OT engineering, and plant operations teams.
+description: 'Develops OT-specific incident response playbooks using a SANS PICERL-based Python
+  engine that classifies incident severity (safety, process, access, recon) and
+  coordinates IT SOC, OT engineering, and plant operations, aligned with IEC 62443
+  and NIST SP 800-82. Use when building ICS/SCADA incident response procedures for
+  the first time, preparing for OT ransomware scenarios, or aligning IR with IEC
+  62443/NERC CIP reporting requirements.
 
   '
 domain: cybersecurity