Bitwarden (1)

**Judgment:** High-quality, security-conscious Bitwarden CLI skill with a well-defined tmux-based session model. Suitable for production-like secret retrieval workflows, provided the environment supports tmux and Bitwarden/Vaultwarden. **Strengths:** - Encodes a complete, repeatable bw workflow: install/configure → login → unlock → use → lock. - Uses a dedicated tmux session and BW_SESSION to ensure authenticated commands persist across multiple steps. - Provides practical, concrete CLI examples and a Docker-based Vaultwarden test setup (including mkcert guidance and test scripts). - Explicit guardrails against secret leakage and recommendations to lock the vault when done. **Risks & Limitations:** - Security is still environment-dependent: BW_SESSION in env vars and tmux panes can be sensitive if the host is compromised or panes are logged. - Requires tmux and adherence to the specified socket/session conventions; misuse (running bw outside tmux or capturing full panes) can break workflows or expose data. - Focuses on common operations; more advanced Bitwarden features (e.g., orgs, attachments, complex item manipulation) are not covered. **Recommended Scenarios:** - OpenClaw workflows that need to securely fetch credentials (passwords, usernames, TOTP codes) from Bitwarden without embedding secrets in code. - Teams standardizing on Bitwarden/Vaultwarden and wanting a reproducible, testable CLI-based integration pattern. - CI/dev environments where a controlled tmux + bw session is acceptable and security policies allow short-lived BW_SESSION usage in process environments.