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,13 +1,10 @@
---
name: implementing-aws-nitro-enclave-security
description: 'Implements AWS Nitro Enclave-based confidential computing environments
with cryptographic attestation, KMS policy integration using PCR-based condition
keys, and secure vsock communication channels. The practitioner builds enclave images,
configures attestation-aware KMS policies, validates attestation documents against
the AWS Nitro PKI root of trust, and establishes isolated computation pipelines
for processing sensitive data such as PII, cryptographic keys, and healthcare records.
Activates for requests involving Nitro Enclave setup, enclave attestation validation,
confidential computing on AWS, or KMS enclave policy configuration.
description: 'Build AWS Nitro Enclave confidential computing environments using nitro-cli
to create enclave images, configure attestation-aware KMS policies with PCR condition
keys, validate attestation documents against the Nitro PKI root, and set up vsock/kmstool-enclave-cli
pipelines for processing PII, keys, and health records. Use for Nitro Enclave setup,
attestation validation, or scoping KMS to an enclave image hash.
'
domain: cybersecurity