bitwarden-secrets
Retrieve and manage secrets using Bitwarden Secrets Manager CLI (bws). Trigger terms: bitwarden, secrets, bws, secret, api key, credentials, password.
Datos de origen
- Repositorio
- Th0rgal/sandboxed-library-template
- Última actividad en el origen
- 13 de febrero de 2026 a las 21:56
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 8
- Forks
- 16
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- bitwarden-secrets
- description
- Retrieve and manage secrets using Bitwarden Secrets Manager CLI (bws). Trigger terms: bitwarden, secrets, bws, secret, api key, credentials, password.
## Use when
- Retrieving API keys, passwords, or credentials for a task
- Listing available secrets or projects
- Creating or updating secrets
## Don't use when
- Storing secrets in code or config files (use bws instead)
- Managing Bitwarden vault items (use `bw` CLI, not `bws`)
## Prerequisites
- `bws` CLI installed
- `BWS_ACCESS_TOKEN` environment variable set
## Quick Reference
| Action | Command |
|--------|---------|
| Get secret | `bws secret get <SECRET_ID>` |
| List secrets | `bws secret list` |
| List in project | `bws secret list <PROJECT_ID>` |
| List projects | `bws project list` |
| Create secret | `bws secret create <KEY> <VALUE> <PROJECT_ID>` |
| Edit secret | `bws secret edit <SECRET_ID> --value <VALUE>` |
| Delete secret | `bws secret delete <SECRET_ID>` |
## Outputs
Use `--output` flag: `json`, `yaml`, `table`, `tsv`, `env`
```bash
bws secret get <ID> --output json
bws secret list --output table
```
## Templates or Examples
- Use the `bws secret list --format json` output when a structured list is required.
- Use the `bws secret get --format json` output when the user needs an exact payload.
## Procedure
1. **List projects** to find where secrets are stored
2. **List secrets** in the relevant project
3. **Get secret** by ID to retrieve the value
4. Use the secret value in your task (don't log it)
## Checks & Guardrails
- Never echo or log secret values
- Don't commit secrets to git
- Use `--output json` for parsing in scripts
Ver en GitHub