Bitwarden

Access and manage Bitwarden/Vaultwarden passwords securely using the rbw CLI.

Security Scan

The skill is internally consistent: it only instructs the agent to run the rbw CLI to access a Bitwarden/Vaultwarden vault and does not request unrelated credentials or install arbitrary code.

Purpose & Capability

Name/description and runtime instructions align: the skill operates exclusively through the rbw CLI and declares rbw as the required binary. There are no unrelated requested binaries, env vars, or install steps.

Instruction Scope

SKILL.md instructs the agent to run rbw commands (login, unlock, list, get, add, sync) and to use tmux/pinentry-curses if interactive prompts are needed. It does not tell the agent to read other system files or unrelated environment variables. One ambiguous phrase—"rbw caches the session key in the agent"—should be clarified: the agent will handle interactive secrets (master password/2FA) and may hold session tokens for the CLI, which is expected but sensitive.

Install Mechanism

Instruction-only skill with no install spec and no external downloads — lowest-risk installation behavior. It relies on a preinstalled rbw binary (expected for this purpose).

Credentials

The skill declares no required env vars. The instructions mention common supporting envs/tools (EDITOR, pinentry provider) which are appropriate for interacting with rbw but are not declared as required. No unrelated credentials or config paths are requested.

Persistence & Privilege

always:false (normal). The skill can be invoked autonomously by the agent (platform default). Because it enables access to a local password vault, autonomous invocation increases risk — consider whether you want the agent to access secrets without explicit user confirmation each time.

Assessment

This skill is coherent: it simply tells the agent to run the rbw CLI to manage your Bitwarden/Vaultwarden vault. Before enabling it, confirm you have a trusted rbw binary installed and understand that the agent will prompt for (and may temporarily hold) your master password, 2FA, and session tokens. If you prefer tighter control, only allow this skill to run when you explicitly invoke it (avoid enabling autonomous invocation for sensitive workflows), and verify the agent's storage/rotation policy for cached session keys. Finally, if you see the skill request additional environment variables or installation steps later, treat that as a red flag and re-evaluate.

Bitwarden Skill

Interact with Bitwarden or Vaultwarden vaults using the rbw CLI.

Usage & Configuration

1. Setup (First Run)

rbw config set email <your_email>
rbw config set baseurl <vault_url> # Optional, defaults to bitwarden.com
rbw login

Note: Login requires the Master Password and potentially 2FA (email/TOTP).

2. Unlock

rbw unlock

Note: rbw caches the session key in the agent. If interactive input is required (pinentry), see if you can setup pinentry-curses (CLI-based pinentry) as the pinentry provider.

3. Management

• List items: rbw list
• Get item: rbw get "Name"
• Get JSON: rbw get --full "Name"
• Search: rbw search "query"
• Add: rbw add ...
• Sync: rbw sync (Refresh vault) Note: Always sync before getting details to ensure accuracy.

Tools

The agent uses exec to run rbw commands.

• For unlocking, use tmux if rbw prompts for a password via pinentry-curses.
• For adding items, rbw add may require EDITOR configuration or tmux.