Bitwarden / Vaultwarden
Bitwarden & Vaultwarden password manager integration. Use when storing, retrieving, generating, or managing passwords and credentials. Wraps the Bitwarden CLI (bw) with automatic session management. Works with both official Bitwarden and self-hosted Vaultwarden servers.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- Bitwarden / Vaultwarden
- homepage
- https://github.com/TWhidden/openclaw-skill-bitwarden
- metadata
- { "clawdbot": { "emoji": "🔐", "requires": { "env": [ "BW_SERVER", "BW_EMAIL", "BW_MASTER_PASSWORD" ], "bins": [ "bw", "openssl", "curl" ], "files": [ "bw.sh" ], "primaryEnv": "BW_SERVER" } } }
- description
- Bitwarden & Vaultwarden password manager integration. Use when storing, retrieving, generating, or managing passwords and credentials. Wraps the Bitwarden CLI (bw) with automatic session management. Works with both official Bitwarden and self-hosted Vaultwarden servers.
03 SKILL.md 正文
Bitwarden & Vaultwarden
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.
Requirements
- Bitwarden CLI (
bw) installed:npm install -g @bitwarden/cli - A Bitwarden or Vaultwarden server instance
- Credentials configured (see Configuration below)
Configuration
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
Invocation
bash skills/bitwarden/bw.sh <command> [args...]
Commands
| Command | Description | Example |
|---|---|---|
register [email] [pass] [name] |
Register new account | bw.sh register user@example.com pass123 "My Name" |
login |
Login & unlock vault | bw.sh login |
status |
Show vault status | bw.sh status |
list [search] |
List/search items | bw.sh list github |
get <name|id> |
Get full item JSON | bw.sh get "GitHub" |
get-password <name|id> |
Get password only | bw.sh get-password "GitHub" |
get-username <name|id> |
Get username only | bw.sh get-username "GitHub" |
create <name> <user> <pass> [uri] [notes] |
Create login | bw.sh create "GitHub" user pass https://github.com |
generate [length] |
Generate password | bw.sh generate 32 |
delete <id> |
Delete item | bw.sh delete <uuid> |
lock |
Lock vault | bw.sh lock |
Workflow
- 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
loginagain
Storing New Credentials
# 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"
Account Registration
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/registerendpoint
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.
Guardrails
- Never paste secrets into logs, chat, or code.
- Keep
bitwarden.envout of version control. - Use
chmod 600on credential files. - Session tokens are stored in
/tmpand cleared on lock/logout.
External Endpoints
| Endpoint | Purpose | Data Sent |
|---|---|---|
| User-configured BW_SERVER | Bitwarden/Vaultwarden API | Encrypted 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.
Security & Privacy
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.
Model Invocation
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.
Security Best Practices
- Credentials file: Use
chmod 600onsecrets/bitwarden.env - Environment isolation: Don't share credential files across systems
- Session tokens: Automatically expire; run
bw.sh lockwhen done - Git: The
.gitignoreexcludes all secrets (secrets/,*.env,.bw_session) - Master password: Never hardcode or log your master password
04 同仓库更多 Skills
crowd-prompting
A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.
ceaser
Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
ceaser-send
Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir/UltraHonk zero-knowledge proofs.
dilemm-ai
Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
arxiv-paper-reviews
Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.