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,7 +1,10 @@
---
name: building-patch-tuesday-response-process
description: Establish a structured operational process to triage, test, and deploy
Microsoft Patch Tuesday security updates within risk-based remediation SLAs.
description: Establish a repeatable operational process for triaging, testing, and
deploying Microsoft Patch Tuesday security updates (Windows, Office, Exchange, SQL
Server, Azure) via WSUS/SCCM within risk-based remediation SLAs, from advisory review
through validation. Use when building or improving a monthly patch management workflow
or prioritizing which CVEs to remediate first.
domain: cybersecurity
subdomain: vulnerability-management
tags: