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: implementing-vulnerability-remediation-sla
description: Vulnerability remediation SLAs define mandatory timeframes for patching
or mitigating identified vulnerabilities based on severity, asset criticality, and
exploit availability. Effective SLA programs
description: Design a vulnerability remediation SLA program covering asset tiering,
a severity-based SLA matrix, exception processes, escalation chains, ticketing-system
integration, and remediation KPIs/trending metrics. Use when defining mandatory
patching timeframes by severity and asset criticality, building an SLA policy document,
or setting up escalation and KPI tracking for vulnerability remediation.
domain: cybersecurity
subdomain: vulnerability-management
tags: