How do I install the Botauth skill?

Run npx skillmds@latest add dvcrn/botauth in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Botauth safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Botauth?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Botauth free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Botauth?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Botauth by dvcrn — Agent Skill

Name: Botauth
Rating: 4.666666666666667 (3 reviews)
Author: dvcrn

Botauth

Use the botauth CLI to list, search, and retrieve secrets from the user's unlocked botauth vault with per-request approval in the desktop app. Use when a task needs API keys, tokens, or passwords from an existing botauth vault.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

botauth

Use botauth to securely retrieve API keys, tokens, and credentials from the user's botauth vault. The desktop app must be running, the vault must be unlocked, and every list, search, and get request can trigger an approval prompt.

When to use

You need an API key, token, or password to complete a task
The user asks you to use credentials that already exist in botauth
You need to fill a .env file or config from the user's vault

Do not save new secrets unless the user explicitly asks. botauth add opens a desktop flow for the user to fill in the credential.

Prerequisites

botauth must be installed and available on PATH
The botauth desktop app must be running
The vault must be unlocked
Run botauth status first

Core commands

Check connection

botauth status

Search or list secrets

botauth search "openai"
botauth search "github" --provider github
botauth list
botauth list --provider github
botauth list --tags dev,production

Retrieve a secret in two steps

First get metadata:

botauth get "OpenAI API Key"
botauth get --id <secret-id>

Then fetch the sensitive fields:

botauth get --id <secret-id> --fields api_key
botauth get --id <secret-id> --fields api_key,client_secret --access-key <key>

Reuse --access-key inside the same workflow when possible to avoid redundant approval prompts.

Ask the user to create a secret

botauth add
botauth add --app openai --secret-name "Production Key"

Typical workflow

botauth status
botauth search "openai"
botauth get "OpenAI API Key"
botauth get --id <id> --fields api_key --access-key <access-key>
export OPENAI_API_KEY="<value>"

JSON output

Use --json for machine-readable output:

botauth search "github" --json
botauth get --id <id> --fields token --json

Important notes

list, search, get, and add may show approval prompts in the desktop app
Sensitive values only come back from get --fields
Access keys are short-lived; reuse them during a single task, then discard them
If botauth status fails, ask the user to launch or unlock the desktop app

---name: botauthdescription: Use the botauth CLI to list, search, and retrieve secrets from the user's unlocked botauth vault with per-request approval in the desktop app. Use when a task needs API keys, tokens, or passwords from an existing botauth vault.---# botauthUse `botauth` to securely retrieve API keys, tokens, and credentials from theuser's botauth vault. The desktop app must be running, the vault must beunlocked, and every `list`, `search`, and `get` request can trigger an approvalprompt.## When to use- You need an API key, token, or password to complete a task- The user asks you to use credentials that already exist in botauth- You need to fill a `.env` file or config from the user's vaultDo not save new secrets unless the user explicitly asks. `botauth add` opens adesktop flow for the user to fill in the credential.## Prerequisites- `botauth` must be installed and available on `PATH`- The botauth desktop app must be running- The vault must be unlocked- Run `botauth status` first## Core commands### Check connection```bashbotauth status```### Search or list secrets```bashbotauth search "openai"botauth search "github" --provider githubbotauth listbotauth list --provider githubbotauth list --tags dev,production```### Retrieve a secret in two stepsFirst get metadata:```bashbotauth get "OpenAI API Key"botauth get --id <secret-id>```Then fetch the sensitive fields:```bashbotauth get --id <secret-id> --fields api_keybotauth get --id <secret-id> --fields api_key,client_secret --access-key <key>```Reuse `--access-key` inside the same workflow when possible to avoid redundantapproval prompts.### Ask the user to create a secret```bashbotauth addbotauth add --app openai --secret-name "Production Key"```## Typical workflow```bashbotauth statusbotauth search "openai"botauth get "OpenAI API Key"botauth get --id <id> --fields api_key --access-key <access-key>export OPENAI_API_KEY="<value>"```## JSON outputUse `--json` for machine-readable output:```bashbotauth search "github" --jsonbotauth get --id <id> --fields token --json```## Important notes- `list`, `search`, `get`, and `add` may show approval prompts in the desktop app- Sensitive values only come back from `get --fields`- Access keys are short-lived; reuse them during a single task, then discard them- If `botauth status` fails, ask the user to launch or unlock the desktop app

Frequently asked questions