Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
No user-visible changes in this version. - Version bumped to 1.0.69 with no file or documentation changes detected.
What This Skill Does
Manages API keys, passwords, OAuth tokens, and SSH keys for agents without exposing values to the conversation context. The agent creates a secret via the Vincent CLI, the user sets the value through the heyvincent.ai dashboard, and the CLI writes it directly to a .env file. The credential value never appears in stdout or the agent's context window.
Credentials never enter the agent's context or stdout, unlike pasting secrets directly into chat where they become part of the conversation history.
When to use it
- Storing a third-party API key for an app an agent is building
- Writing database username and password to .env without pasting them in chat
- Managing OAuth tokens for a service the agent needs to integrate
- Setting up SSH keys for a deployment pipeline being configured by an agent
- Recovering credential access after an agent loses its stored API key
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Store my Acme service credentials securely so the agent can use them
- 1Check for existing credential keys with `secret list --type CREDENTIALS`
- 2Create a new CREDENTIALS secret with `secret create --type CREDENTIALS --memo 'Acme credentials'`
- 3Share the returned claimUrl with the user so they can set the value via the heyvincent.ai dashboard
- 4Once the user confirms the value is set, run `secret env --key-id <ID> --env-var ACME_USERNAME --field username` and repeat for password
- 5Confirm .env was updated using the returned confirmation JSON
.env file contains ACME_USERNAME and ACME_PASSWORD without the values ever appearing in the agent conversation
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.