secret-vault

Encrypt and store credentials in a local AES-256-GCM vault.

5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/JansenAnalytics/claudex --skill secret-vault-jansenanalytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-vault
Source: https://github.com/JansenAnalytics/claudex/tree/main/skills/secret-vault
Command: npx skills add https://github.com/JansenAnalytics/claudex --skill secret-vault-jansenanalytics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Encrypts and stores credentials securely in a local vault.

Core Features & Use Cases

  • Encrypts and stores API tokens, passwords, and other secrets in a single encrypted file
  • Per-secret AES-256-GCM encryption with unique IVs and authentication tags
  • CLI and programmatic access via vault.cjs for set, get, list, delete, export, and check

Quick Start

Store your first secret using vault.cjs set NAME VALUE to begin using encrypted storage.

Frequently Asked Questions about secret-vault

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

FAQPage Schema
How do I securely store API tokens and passwords locally using AES-256-GCM encryption?

You can securely store API tokens and passwords locally by using AES-256-GCM encryption with per-secret IVs and authentication tags. The vault encrypts credentials into a single file at ~/.openclaw/vault.enc, with the key stored separately at ~/.openclaw/vault.key.

Can I manage encrypted credentials in Node.js automation scripts?

Yes, you can manage encrypted credentials in Node.js automation scripts using the included vault.cjs script. It provides programmatic access and CLI commands to set, get, list, delete, export, and check secrets directly from your code.

What is the best way to encrypt and retrieve secrets from a local vault via CLI?

The best way to encrypt and retrieve secrets via CLI is using the vault.cjs script. You can store a secret with the set command and retrieve it with the get command, ensuring credentials are encrypted with AES-256-GCM and authenticated before storage.

Does this local secret vault require any external dependencies to manage credentials?

No external dependencies are required to manage credentials in this local secret vault. It operates independently using built-in Node.js capabilities to handle AES-256-GCM encryption and file storage operations.

How do I export encrypted secrets for use in other automation workflows?

You can export encrypted secrets for other automation workflows using the export command provided by the vault.cjs CLI. This allows you to retrieve and integrate your stored credentials into separate scripts or external systems securely.

What are the limitations of using a local encrypted file for credential management?

A limitation of using a local encrypted file for credential management is that the vault and key are stored locally at ~/.openclaw/, restricting access to the specific workstation where they reside and requiring manual secure transfer for cross-machine automation.