redpill-vault
Manages environment variables and credentials for AI tools. API keys, tokens, database URLs, and other secrets are stored in an encrypted vault. Use rv-exec to run commands with secrets injected. The agent never sees secret values or the master key.
What this skill does
# redpill-vault
Secure credential manager for AI tools. Secrets are stored in an encrypted vault and injected into commands via `rv-exec`.
## NEVER run these commands
The following commands are **user-only** — the agent must NEVER run them:
- `rv approve` — only the user can approve a project
- `rv revoke` — only the user can revoke approval
- `rv set` — only the user can set secret values
If a secret is missing, tell the user to run `rv set KEY_NAME` themselves.
## Setup
```bash
./skills/redpill-vault/setup.sh
```
```bash
rv init
```
After setup, the **user** must approve the project before secrets can be injected:
```bash
rv approve
```
This is a one-time step per project. The agent cannot run `rv approve` — only the user can.
## Running commands with secrets
Use `rv-exec --all` to inject all secrets from `.rv.json`:
```bash
rv-exec --all -- <command>
```
Examples:
```bash
rv-exec --all -- npm run deploy
rv-exec --all -- docker push myimage:latest
rv-exec --all -- bash -c 'echo $MY_SECRET'
```
The `--all` flag injects all secrets defined in `.rv.json`. Secrets are resolved from the vault at runtime — the agent never sees the values.
### Specific keys
To inject only specific keys:
```bash
rv-exec KEY1 KEY2 -- <command>
```
### Generating a .env file
Some commands require a `.env` file. Use `--dotenv`:
```bash
rv-exec --all --dotenv .env -- phala deploy -e .env
```
This writes secrets to `.env` before running and deletes it after.
## Adding secrets
### Importing from .env
```bash
rv import .env
```
Imports all keys from the file, stores each as a project-scoped secret. Values go directly to the encrypted vault.
To import specific keys: `rv import .env GITHUB_TOKEN DATABASE_URL`
To import as global keys: `rv import .env -g`
### Setting a single secret (user only)
Tell the user to run in their terminal:
```bash
rv set KEY_NAME
```
The agent must NEVER run `rv set` — it reads secret values from stdin.
### Removing secrets
```bash
rv rm KEY_NAME
rv rm KEY_NAME -g # global
```
## .rv.json
```json
{
"project": "myapp",
"secrets": {
"GITHUB_TOKEN": { "description": "GitHub API token" },
"DATABASE_URL": {}
}
}
```
The `"project"` field is optional — directory name is used if omitted.
## Key resolution
For each key, `rv-exec` checks:
1. Project-scoped key (`PROJECT__KEY`) first
2. Falls back to global key (`KEY`)
This lets projects override or inherit global credentials.
`rv list` shows each key's source: `[project]`, `[global]`, or `[missing]`.
## Commands
| Command | Description |
|---------|-------------|
| `rv init` | Initialize project (master key + vault + config) |
| `rv approve` | Approve project for secret injection (user only) |
| `rv revoke` | Revoke project approval (user only) |
| `rv import .env` | Import secrets from .env file |
| `rv list` | Show secrets with source |
| `rv list -g` | Show global keys in vault |
| `rv check` | Verify all keys exist |
| `rv doctor` | Full health check |
| `rv set KEY` | Set a secret (user only, reads from stdin) |
| `rv rm KEY` | Remove a secret |
| `rv-exec --all -- cmd` | Run command with all secrets |
| `rv-exec K1 K2 -- cmd` | Run command with specific secrets |
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.