Bitwarden Vault CLI

**Quick judgement:** This is a strong, opinionated skill for interacting with Bitwarden via the `bw` CLI, well-suited to agents that need to fetch secrets securely on a machine where Bitwarden CLI and tmux are available. It provides a complete workflow (install check → login/unlock → session export → secret retrieval) and supports email/password, API key, and SSO authentication, including self-hosted servers. **Key risks:** - **Secret exposure risk:** Any agent misuse (e.g., echoing secrets into logs, chat output, or files) can leak sensitive data despite the documented guardrails. - **Environment dependencies:** Requires both Bitwarden CLI and `tmux`; if `tmux` is missing or the environment is unusual (e.g., restricted shells, containerized CI), workflows may break. - **Session handling errors:** Mismanaging `BW_SESSION` (forgetting to export it, using a stale session, or losing the tmux session) can cause confusing authentication/"vault locked" errors. **Recommended scenarios:** - Agent-driven automation that must read secrets from Bitwarden on a developer workstation or well-prepared server. - Secure configuration of local tools and scripts (exporting secrets directly into environment variables without writing to disk). - Workflows that need periodic retrieval of credentials, TOTP codes, or structured secret fields from Bitwarden, including against self-hosted/Vaultwarden instances.