What problem does it solve? Managing secrets across environments and providers is error-prone and risky. This Skill guides you through creating swamp vaults, storing and reading secrets safely, and referencing them in models and workflows without hardcoding sensitive values. ## Core Features & Use Cases - Vault Lifecycle Management: Create vaults with auto-assigned IDs using built-in types (aws-sm, azure-kv, 1password, local_encryption) or user-defined @collective/name types, then search, edit, and migrate them. - Secret Operations: Store secrets inline, via piped stdin, or through hidden interactive prompts; read values with confirmation guards and list keys without exposing values. - Vault Expressions in Workflows: Reference secrets with ${{ vault.get(vault-name, key) }} expressions that resolve lazily per-step at runtime, supporting rotation and token-refresh patterns. - Use Case: Set up separate dev and production vaults, store API keys via piped input to keep them out of shell history, and reference them in model globalArguments so workflows always fetch fresh credentials. ## Quick Start Ask the assistant to create a local_encryption vault named dev-secrets and store an API key in it using the swamp vault CLI.