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,9 +1,11 @@
---
name: securing-aws-lambda-execution-roles
description: 'Securing AWS Lambda execution roles by implementing least-privilege
IAM policies, applying permission boundaries, restricting resource-based policies,
using IAM Access Analyzer to validate permissions, and enforcing role scoping through
SCPs.
description: 'Hardens AWS Lambda execution roles by writing least-privilege IAM policies,
applying permission boundaries, restricting resource-based policies, validating
permissions with IAM Access Analyzer, and enforcing role scoping through SCPs. Use
when deploying new Lambda functions, remediating overly permissive Lambda roles found
in an audit, or building reusable least-privilege IAM role templates for serverless
teams.
'
domain: cybersecurity