Skillv1.0.0

ClawScan security

Securely interact with Bitwarden/Vaultwarden vaults using rbw CLI. Use when retrieving credentials, managing vault items, or integrating secrets into scripts/systemd services. Handles authentication, field access, and non-interactive operation patterns. · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousFeb 25, 2026, 1:50 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The instructions match the stated purpose (non-interactive rbw usage) but they require storing a Bitwarden master password in plaintext and reference an undeclared environment variable and system paths—these mismatches and the sensitive-system changes warrant caution.
Guidance: This skill's instructions are coherent with its goal (non-interactive rbw usage) but they ask you to store your Bitwarden master password in plaintext and rely on an undeclared RBW_MASTER_PASSWORD environment variable and an /etc systemd file. Before using/installing: (1) verify the rbw binary and other tools (pinentry, jq, curl) are from trusted sources; (2) prefer safer non-interactive patterns if possible (systemd LoadCredential=, OS keyring, hardware token, or ephemeral service accounts) instead of plaintext files; (3) if you must use the provided pattern, restrict the credential file to root:root 600 and minimize who can read/modify systemd unit files; (4) confirm you trust the skill source (homepage unknown) and test in an isolated environment first; (5) consider editing the SKILL.md or your deployment to declare RBW_MASTER_PASSWORD explicitly and to document audit/trust controls. If you need, ask for a version that uses a recommended secure alternative (systemd LoadCredential or an external secret provider) instead of plaintext credentials.

Review Dimensions

Purpose & Capability: okThe skill's name/description (non-interactive rbw usage) aligns with the SKILL.md content: commands, get/list/add, and systemd/script integration are all relevant to the stated purpose.
Instruction Scope: concernThe runtime instructions tell the operator/agent to create a pinentry wrapper that reads RBW_MASTER_PASSWORD and to store the master password in /etc/systemd/rbw-credentials.conf (plaintext), and to configure systemd EnvironmentFile. The SKILL.md therefore instructs reading/writing system-level files and using an environment variable not declared in the skill metadata. These actions go beyond simply invoking rbw and involve system-wide sensitive state.
Install Mechanism: okThis is instruction-only (no install spec, no binaries shipped). That minimizes install-time risk because nothing is downloaded or written by an installer, but it assumes rbw/pinentry/jq/curl are available on the host.
Credentials: concernThe SKILL.md relies on the RBW_MASTER_PASSWORD environment variable and on an EnvironmentFile under /etc/systemd, but the skill metadata declares no required env vars or credentials. Requiring a master password (and storing it as plaintext) is functionally consistent with non-interactive unlocking but the metadata mismatch and the need for a sensitive secret stored at root-level are disproportionate without explicit declaration and justification.
Persistence & Privilege: noteThe skill does not request always:true and does not self-install, but its recommended pattern requires creating system files under /etc and adjusting systemd service EnvironmentFile entries (requires root). That means installation/run will need elevated privileges and will persist a sensitive secret on disk unless the user chooses alternative approaches.