bitwarden-secrets

Manage Bitwarden Secrets Manager credentials and sync .env files.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/leto-labs/openclaw-bootstrap-config --skill bitwarden-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bitwarden-secrets
Source: https://github.com/leto-labs/openclaw-bootstrap-config/tree/main/skills/bitwarden-secrets
Command: npx skills add https://github.com/leto-labs/openclaw-bootstrap-config --skill bitwarden-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, awk, sed, bws, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Bitwarden Secrets Manager is essential for securely storing and managing credentials; this skill centralizes creation, updating, listing, and rotation of secrets while keeping values hidden from chat.

Core Features & Use Cases

  • Setup and verify Bitwarden Secrets Manager access (bws, BWS_ACCESS_TOKEN)
  • Create/update/list/delete secrets
  • Sync secrets between Bitwarden projects and .env files in both directions
  • Guidance on runtime usage (bws run vs on-demand fetch)
  • Guardrails and incident response

Quick Start

Install the bws CLI, configure BWS_ACCESS_TOKEN, and run the env-to-bws or bws-to-env workflow to seed and sync secrets.

Frequently Asked Questions about bitwarden-secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync secrets between Bitwarden and .env files?

You can sync secrets between Bitwarden and .env files using the env-to-bws and bws-to-env workflows. This enables bidirectional synchronization to seed and update credentials while keeping secret values hidden from the chat interface.

What do I need to access Bitwarden Secrets Manager for CI/CD pipelines?

To access Bitwarden Secrets Manager in CI/CD pipelines, you need the bws CLI installed, a valid BWS_ACCESS_TOKEN configured, and jq available. These dependencies enable runtime secret access and on-demand credential fetching.

Can I rotate credentials in Bitwarden without exposing secret values?

Yes, you can create, update, and rotate secrets in Bitwarden without exposing values. The skill enforces strict guardrails to keep secret values hidden from chat during credential rotation and environment migration workflows.

What is the best way to migrate environment variables to Bitwarden Secrets Manager?

The best way to migrate environment variables to Bitwarden Secrets Manager is the env-to-bws workflow. It securely transfers credentials from .env files into Bitwarden projects while maintaining strict guardrails against value exposure.

Does the Bitwarden Secrets Manager workflow support runtime secret access in OpenClaw?

Yes, Bitwarden Secrets Manager supports runtime secret access in OpenClaw workflows and CI/CD pipelines. You can use bws run for execution or perform on-demand fetches using the bws CLI with a valid BWS_ACCESS_TOKEN.

Why should I use Bitwarden Secrets Manager instead of storing credentials directly in .env files?

Bitwarden Secrets Manager centralizes credential management with strict guardrails, preventing secret exposure in chat. Unlike plain .env files, it supports secure rotation workflows, project onboarding, and CI/CD pipeline integration while keeping values hidden.