What problem does it solve? Setting up OneCLI's Agent Vault and moving hardcoded API keys out of .env files is a multi-step, error-prone process involving CLI installation, gateway health checks, credential migration, and service restarts. This Skill automates the entire initialization so agents never see raw API keys. ## Core Features & Use Cases - Automated OneCLI Installation: Installs the OneCLI gateway and CLI, configures the API host, waits for gateway health, and persists ONECLI_URL in .env. - Credential Migration: Scans .env for Anthropic keys, OAuth tokens, and container-facing credentials (OpenAI, Parallel), registers them as OneCLI secrets, and removes the raw values from .env while preserving channel tokens. - Verification & Recovery: Rebuilds the project, restarts the NanoClaw service (launchd/systemd/manual), verifies gateway integration in logs, and includes troubleshooting for Docker, port conflicts, and git-over-HTTPS injection issues. - Use Case: After /update-nanoclaw introduces OneCLI as a breaking change, run this Skill to install the vault, migrate your ANTHROPIC_API_KEY from .env, and confirm containers receive injected credentials. ## Quick Start Run the init-onecli skill to install OneCLI and migrate my .env credentials into the Agent Vault.