init-onecli

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

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill init-onecli-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-onecli
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/init-onecli
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill init-onecli-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up OneCLI's Agent Vault and moving Anthropic API keys or OAuth tokens out of a plaintext .env file is a multi-step, error-prone process involving CLI installation, gateway health checks, credential migration, and service restarts. This Skill automates that entire flow so containerized agents receive credentials through gateway injection instead of raw keys. ## Core Features & Use Cases - OneCLI installation and gateway setup: Installs the OneCLI gateway and CLI, configures the API host, persists ONECLI_URL in .env, and polls the Docker Compose gateway stack until healthy. - Credential migration: Scans .env for Anthropic keys, OAuth tokens, and container-facing credentials like OPENAI_API_KEY, registers them as OneCLI secrets with correct host patterns, and removes the raw values from .env while preserving channel tokens. - Verification and troubleshooting: Rebuilds the project, restarts the NanoClaw service via launchd or systemd, checks logs for gateway integration, and documents git-over-HTTPS injection settings and safe secret-merge patterns. - Use Case: After /update-nanoclaw introduces OneCLI as a breaking change, run this Skill to install the vault, migrate existing Anthropic credentials, and verify agents receive injected secrets without ever seeing raw keys. ## Quick Start Run the init-onecli skill to install OneCLI, migrate my .env credentials into the Agent Vault, and verify the gateway is working.

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 this Skill to scan .env for ANTHROPIC_API_KEY, CLAUDE_CODE_OAUTH_TOKEN, and similar variables, register each as a OneCLI secret with the correct host pattern, then remove the raw values from .env. Channel tokens like TELEGRAM_BOT_TOKEN stay in .env because the host process uses them.

How do I set up OneCLI after a NanoClaw update?

Run /init-onecli after /update-nanoclaw introduces OneCLI as a breaking change. The Skill installs the gateway and CLI, configures ONECLI_URL, waits for gateway health, migrates credentials, rebuilds with pnpm, and restarts the service.

Why is the OneCLI gateway not reachable?

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

Does OneCLI credential injection work with git over HTTPS?

Yes, but git needs GIT_SSL_CAINFO pointing to the OneCLI CA bundle since OneCLI does not set it automatically. GitHub git operations also require Basic auth rather than Bearer, so git and API access must be configured as separate secrets.

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

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