init-onecli

Installs OneCLI Agent Vault and migrates .env credentials into gateway-managed secrets.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/RADHA0-max/selfhealbackend --skill init-onecli-radha0-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-onecli
Source: https://github.com/RADHA0-max/selfhealbackend/tree/main/nanoclaw/.claude/skills/init-onecli
Command: npx skills add https://github.com/RADHA0-max/selfhealbackend --skill init-onecli-radha0-max

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about init-onecli

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

FAQPage Schema
How do I migrate .env API keys to OneCLI Agent Vault?

Run the init-onecli skill, which scans your .env for credentials like ANTHROPIC_API_KEY and CLAUDE_CODE_OAUTH_TOKEN, registers them with onecli secrets create using the correct host pattern, and removes the raw values from .env while keeping channel tokens intact.

How do I set up OneCLI after a NanoClaw update?

After /update-nanoclaw brings in the @onecli-sh/sdk integration, run /init-onecli. It installs the gateway and CLI via onecli.sh install scripts, sets ONECLI_URL in .env, waits for gateway health, then rebuilds and restarts the service.

Which credentials should stay in .env instead of the vault?

Channel tokens such as TELEGRAM_BOT_TOKEN, SLACK_BOT_TOKEN, SLACK_APP_TOKEN, and DISCORD_BOT_TOKEN must stay in .env because the NanoClaw host process uses them directly. Only credentials used by containers for outbound HTTPS calls should be migrated.

Why is the OneCLI gateway not reachable after installation?

The gateway is a Docker Compose stack, so the most common cause is Docker not running. Start Docker and the containers restart automatically, or bring them up manually with docker compose -f ~/.onecli/docker-compose.yml up -d, then verify with curl on the health endpoint.

Why does git fail with OneCLI credential injection?

OneCLI sets SSL_CERT_FILE for Node and Python but not GIT_SSL_CAINFO, so git rejects the MITM certificate. Add GIT_SSL_CAINFO pointing to the OneCLI CA bundle in the agent's settings.json, and note that github.com git operations require Basic auth rather than Bearer.