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: executing-red-team-engagement-planning
description: Red team engagement planning is the foundational phase that defines scope,
objectives, rules of engagement (ROE), threat model selection, and operational timelines
before any offensive testing begins.
description: Build the foundational red team engagement plan - scope definition, Rules
of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization),
MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an
engagement brief for stakeholder approval. Use before any offensive testing begins, when
scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.
domain: cybersecurity
subdomain: red-teaming
tags: