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,14 +1,11 @@
---
name: implementing-api-gateway-security-controls
description: 'Implements security controls at the API gateway layer including authentication
enforcement, rate limiting, request validation, IP allowlisting, TLS termination,
and threat protection. The engineer configures API gateways (Kong, AWS API Gateway,
Azure APIM, Apigee) to act as a centralized security enforcement point that validates,
throttles, and monitors all API traffic before it reaches backend services. Activates
for requests involving API gateway security, API management security, gateway authentication,
or centralized API protection.
'
description: 'Configures API gateways such as Kong, AWS API Gateway, Azure APIM,
or Apigee as a centralized security enforcement point, covering authentication
enforcement, rate limiting and throttling, request validation, IP allowlisting,
TLS termination, and threat protection. Use when securing API traffic at the gateway
layer, setting up gateway-level authentication and quota management, or centralizing
API protection before requests reach backend services.'
domain: cybersecurity
subdomain: api-security
tags: