Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Bitwarden & Vaultwarden password manager integration. Use when storing, retrieving, generating, or managing passwords and credentials. Wraps the Bitwarden CL...
Bitwarden & Vaultwarden password manager integration. Use when storing, retrieving, generating, or managing passwords and credentials. Wraps the Bitwarden CL...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Bitwarden/Vaultwarden CLI (bw) wrapper with automatic login, session caching, and convenient commands. Works seamlessly with both official Bitwarden (vault.bitwarden.com) and self-hosted Vaultwarden instances.
Bitwarden CLI (bw) installed: npm install -g @bitwarden/cli A Bitwarden or Vaultwarden server instance Credentials configured (see Configuration below)
Set credentials via environment variables or a credentials file: # Environment variables (preferred) export BW_SERVER="https://vault.bitwarden.com" # Official Bitwarden # OR export BW_SERVER="https://your-vaultwarden-instance.example.com" # Vaultwarden export BW_EMAIL="your-email@example.com" export BW_MASTER_PASSWORD="your-master-password" # Or use a credentials file (default: secrets/bitwarden.env) export CREDS_FILE="/path/to/your/bitwarden.env" The credentials file should contain: BW_SERVER=https://vault.bitwarden.com BW_EMAIL=your-email@example.com BW_MASTER_PASSWORD=your-master-password
bash skills/bitwarden/bw.sh <command> [args...]
CommandDescriptionExampleregister [email] [pass] [name]Register new accountbw.sh register user@example.com pass123 "My Name"loginLogin & unlock vaultbw.sh loginstatusShow vault statusbw.sh statuslist [search]List/search itemsbw.sh list githubget <name|id>Get full item JSONbw.sh get "GitHub"get-password <name|id>Get password onlybw.sh get-password "GitHub"get-username <name|id>Get username onlybw.sh get-username "GitHub"create <name> <user> <pass> [uri] [notes]Create loginbw.sh create "GitHub" user pass https://github.comgenerate [length]Generate passwordbw.sh generate 32delete <id>Delete itembw.sh delete <uuid>lockLock vaultbw.sh lock
First call per session: bw.sh login (auto-authenticates from configured credentials) Session token cached at /tmp/.bw_session All subsequent commands auto-use the cached session After reboot/restart: run login again
# Generate + store PASS=$(bash skills/bitwarden/bw.sh generate 32) bash skills/bitwarden/bw.sh create "New Service" "user@email.com" "$PASS" "https://service.com"
Register a new account on your Bitwarden/Vaultwarden server directly from the CLI: # Register using configured credentials (from env/credentials file) bash skills/bitwarden/bw.sh register # Register with explicit credentials bash skills/bitwarden/bw.sh register "user@example.com" "SecurePass123!" "Display Name" How it works: Derives a master key using PBKDF2-SHA256 (600,000 iterations) with the email as salt Creates a master password hash for server authentication Generates a 64-byte symmetric key, encrypted with AES-256-CBC + HMAC-SHA256 Submits registration to the server's /api/accounts/register endpoint Requirements: OpenSSL 3.x+ (for PBKDF2 and HKDF support), curl, xxd. Note: The master password must be at least 12 characters. Works with both official Bitwarden and Vaultwarden servers.
Never paste secrets into logs, chat, or code. Keep bitwarden.env out of version control. Use chmod 600 on credential files. Session tokens are stored in /tmp and cleared on lock/logout.
EndpointPurposeData SentUser-configured BW_SERVERBitwarden/Vaultwarden APIEncrypted vault data, authentication credentials Note: The skill communicates with the Bitwarden server you configure via BW_SERVER. For official Bitwarden, this is https://vault.bitwarden.com. For Vaultwarden, this is your self-hosted instance URL.
What leaves your machine: Authentication requests (email, master password) to your configured Bitwarden server Encrypted vault data (create/read/update/delete operations) All communication uses HTTPS/TLS What stays local: Session tokens (cached in /tmp/.bw_session) Credential files (if using bitwarden.env) Decrypted passwords (only in memory, never written to disk) Trust statement: By using this skill, you are sending authentication credentials and vault data to the Bitwarden server you configure. Only install this skill if you trust your Bitwarden/Vaultwarden instance.
This skill can be invoked autonomously by your OpenClaw agent when it needs to: Store credentials securely Retrieve passwords for automation tasks Generate secure passwords If you prefer manual approval before password operations, configure your OpenClaw agent's tool policy accordingly.
Credentials file: Use chmod 600 on secrets/bitwarden.env Environment isolation: Don't share credential files across systems Session tokens: Automatically expire; run bw.sh lock when done Git: The .gitignore excludes all secrets (secrets/, *.env, .bw_session) Master password: Never hardcode or log your master password
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.