LeoYeAI/agent-master-skills / skills/api-key-ui-tab
apikeys-ui
VerifiedVault-backed API Keys management for OpenClaw. Secure file-based secret storage with one-click migration from plaintext config, dynamic key discovery, vault key selector for skills, manual secret creation, and plugin-registered settings tab.
| File | Kind | Size |
|---|---|---|
| INSTALL_INSTRUCTIONS.md | markdown | 928 B |
| SKILL.md | skill md | 16.3 KB |
| _meta.json | config | 479 B |
| reference/apikeys-controller.ts | script | 19.1 KB |
| reference/apikeys-views.ts | script | 16.1 KB |
| reference/secrets-rpc.ts | script | 16.0 KB |
| reference/skills-controller.ts | script | 5.7 KB |
| reference/skills-rpc.ts | script | 6.7 KB |
| reference/skills-status.ts | script | 8.9 KB |
| reference/skills-views.ts | script | 9.5 KB |
INSTALL_INSTRUCTIONS.md
View on GitHub# Installation
As of v2.0.0, the API Keys UI is built into OpenClaw as a core feature. No manual installation needed.
The tab is registered automatically via the Plugin UI architecture and appears under **Settings → API Keys** in the dashboard.
## What Changed
Previously, this skill required manually copying view/controller files and editing navigation. Now:
- Backend RPCs are in `src/gateway/server-methods/secrets.ts`
- UI files are at `ui/src/ui/controllers/apikeys.ts` and `ui/src/ui/views/apikeys.ts`
- Tab registration is in `src/gateway/server-methods/plugins-ui.ts` (builtin view)
## First-Time Vault Setup
No setup required. On first key save, the system automatically:
1. Creates `~/.openclaw/secrets.json` (mode 0600)
2. Configures the file secret provider in `openclaw.json`
3. Stores the key and creates a SecretRef
To migrate existing plaintext keys, click "🔒 Migrate to Vault" on the API Keys tab.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |