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,11 @@
---
name: implementing-aws-iam-permission-boundaries
description: Configure IAM permission boundaries in AWS to delegate role creation
to developers while enforcing maximum privilege limits set by the security team.
description: Configures AWS IAM permission boundaries that cap the maximum permissions
an identity-based policy can grant to a user or role, so effective permissions
are the intersection of the identity policy and the boundary even if the policy
grants AdministratorAccess. Use when letting security teams delegate IAM role and
policy creation to developers for self-service while enforcing least-privilege
ceilings and preventing privilege escalation.
domain: cybersecurity
subdomain: identity-access-management
tags: