Bitwarden Credential

Permission Setup Review

python scripts/_prepare_workspace.py is an optional setup helper for the Bitwarden Credential Skill skill. It may apply broad filesystem permissions for compatibility. Show the target paths and permission mode, explain the risk, and prefer a narrower mode when shared write access is not needed.

Bitwarden Credential Skill

Store credentials (passwords, API keys, OAuth tokens, etc.) in Bitwarden via the CLI.

Workflow

Step 1: Ensure Vault is Unlocked

The user must unlock their Bitwarden vault once per session in their terminal:

bw unlock

After unlocking, the user gets a session key. There are two ways to provide it:

Option A — Export the session (user does in their terminal):

export BW_SESSION="<session-key-from-unlock>"

Then just tell me "unlocked" and I can run commands directly.

Option B — Pass session directly to script:

BW_SESSION="<session-key>" ./bitwarden-credential.sh <name> <username> <password> [notes]

Step 2: Store a Credential

Once vault is unlocked, provide me with:

• Name — identifier for this credential (e.g., "GitHub API Key", "MiniMax API")
• Username — often the client_id or key name
• Password/Secret — the actual secret value
• Notes (optional) — extra context (scope, grant_type, etc.)

Example user message:

"Save to Bitwarden: name=Grafana, username=admin, password=xyz123, notes=prod server"

Step 3: Execute

Use the bundled script or run directly:

# With BW_SESSION set
./scripts/bitwarden-credential.sh "<name>" "<username>" "<password>" "[notes]"

# Or via bw CLI directly
echo -n '{"name":"...","login":{"username":"...","password":"..."},"type":1}' | bw create item

Notes

• Bitwarden CLI must be installed: brew install bitwarden-cli
• API key auth: Use bw login --apikey with client_id + client_secret, but vault still requires master password to unlock
• I cannot unlock the vault for you — the master password never leaves your terminal
• Session token (BW_SESSION) is session-scoped; it expires when the vault locks again