elbab — Claude Code skill: secret handling and installation
A Claude Code skill that uses credentials from elbab’s encrypted local store without exposing their values. It activates when a task needs a saved API key, password, token, or other secret.
MIT ★ 252 updated 2026-11-12
npx skills add dreamers-laboratory/good-door --skill elbab -a claude-codeWhat elbab does
elbab lets an agent run a command with stored credentials while keeping their values out of the output. The skill uses elbab run ENTRY -- CMD; .env values can be passed this way, and a file can be added with elbab import-env ENTRY FILE.
It also sets handling rules for SSH keys, cloud CLIs, and newly stored secrets. After a store change, run elbab verify. If elbab has not been initialized, the user runs elbab init in their own terminal. show and csv query can expose secrets in a shared terminal.
What it helps with
- run a command with an API key without printing it
- use
.envvalues in a process - load an SSH key with
elbab ssh-load KEY - protect a new secret in the store
Example prompts for the agent
- Run the tests with the API key from the
openaientry through elbab. - Start
npm testusing the.envvalues without displaying them. - Protect the
deploySSH key with elbab.
How to install elbab
1Skills CLI (Vercel)
npx skills add dreamers-laboratory/good-door --skill elbab -a claude-code2Manually: put the files in place
~/.claude/skills/skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/skill/
1Skills CLI (Vercel)
npx skills add dreamers-laboratory/good-door --skill elbab -a codex2Manually: put the files in place
.agents/skills/skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dreamers-laboratory/good-door --skill elbab -a cursor2Manually: put the files in place
.cursor/skills/skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dreamers-laboratory/good-door skill2Manually: put the files in place
.github/skills/skill/SKILL.md1Skills CLI (Vercel)
npx skills add dreamers-laboratory/good-door --skill elbab -a gemini-cli2Platform CLI
gemini skills install https://github.com/dreamers-laboratory/good-door --path skillManually: put the files in place
.devin/skills/skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about elbab
How do I install elbab in Claude Code?
Run npx skills add dreamers-laboratory/good-door --skill elbab -a claude-code. The skill path is ~/.claude/skills/skill/SKILL.md.
What does elbab do?
It guides the agent in using credentials from an encrypted local store without printing their values. Its rules cover API keys, .env values, SSH, and cloud CLIs.
What if elbab has not been set up?
The user runs elbab init in their own terminal. After any store change, the skill runs elbab verify.
Source text
SKILL.md · MIT
--- name: elbab description: Use credentials kept in elbab, the age-encrypted local store, without exposing them. Use when a task needs an API key, password, token, SSH key, cloud CLI login or .env value, or when a credential should be stored or protected. --- # elbab You use credentials. You never see them. ## Rules - Find names with `elbab list`. Use a value with `elbab run ENTRY -- CMD`. - Never print, echo, log or write a value, or pass one as an argument. `elbab get` and `elbab print` only when piped straight into the command that needs it. - Never read `*.age` files, the machine identity or private key files. Never use `--reveal`, `--show` or `--dump`, and never run elbab in a terminal the user shares with you: `show` and `csv query` print secrets there. In your own shell they print masked; if they don't, stop and tell the user. - To store a new secret, ask the user to run `elbab set-key ENTRY VAR` or `elbab NAME` in their own terminal. Don't type it yourself. - Run `elbab verify` after any change to the store. ## Credentials | Need | Do | |---|---| | API key, token | `elbab run ENTRY -- CMD` | | `.env` values | `elbab run ENTRY -- CMD`; store a file with `elbab import-env ENTRY FILE` | | SSH, git, scp | work as usual. Load keys with `elbab ssh-load KEY`, never `ssh-add KEY` | | new SSH key | `elbab ssh-protect KEY` | | public key | `elbab pubkeys NAME` | | AWS | `--profile` or `AWS_SHARED_CREDENTIALS_FILE` as usual; after `aws configure` writes keys, `elbab aws-protect FILE` | | gcloud, az, guarded CLIs | run as usual (shims); after a login outside the shim, `elbab guard-seal TOOL` | | encrypted file or folder (starts with `age-encryption.org/v1`) | `elbab run PATH -- CMD`. `elbab decrypt PATH` only with the user's OK, then `elbab encrypt PATH` when done | | loose secret files | `elbab scan PATH` lists them. Report them; `elbab encrypt PATH` only with the user's OK | ## Errors - `not set up`: the user runs `elbab init`. - `cannot decrypt`: this machine is not a recipient; the user adds it (`elbab recipients add`, `elbab rekey`). - `unknown or expired entry`: check `elbab list`; ask the user.
© dreamers-laboratory · MIT · dreamers-laboratory/good-door