init-onecli

Automate OneCLI Agent Vault installation, configuration, and .env credential migration.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wrightchin/nanoclaw-playground --skill init-onecli-wrightchin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-onecli
Source: https://github.com/wrightchin/nanoclaw-playground/tree/main/.claude/skills/init-onecli
Command: npx skills add https://github.com/wrightchin/nanoclaw-playground --skill init-onecli-wrightchin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the installation and configuration of the OneCLI Agent Vault, migrating existing .env credentials into a secure vault so agents never see raw keys.

Core Features & Use Cases

  • Automates gateway setup and credential migration for OneCLI.
  • Migrates Anthropic and container-facing credentials from .env into OneCLI Secrets.
  • Enables per-agent policies and centralized secret management without exposing raw keys.

Quick Start

Run this after /update-nanoclaw to install and configure OneCLI Agent Vault and migrate credentials from .env.

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 credentials to a central vault for NanoClaw agents?

You can migrate .env credentials to a central vault by automating the installation and configuration of OneCLI Agent Vault, which moves raw keys into secure secrets and establishes gateway-level policies for per-agent isolation.

How does OneCLI Agent Vault secure environment credentials for AI agents?

OneCLI Agent Vault secures environment credentials by migrating raw keys from .env files into centralized secrets, enabling agents to access required keys without ever directly viewing or handling the underlying credential values.

Can I set up per-agent isolation policies after migrating environment variables to a vault?

Yes, you can establish per-agent isolation by setting up gateway-level policies during the OneCLI Agent Vault configuration, ensuring centralized secret management restricts raw key exposure across individual NanoClaw deployments.

What is the best way to configure gateway integration after installing OneCLI Agent Vault?

The best way to configure gateway integration is to run an automated workflow that verifies the OneCLI installation, migrates credentials into the vault, creates secrets, and validates the gateway integration for NanoClaw deployments.

Do I need to update NanoClaw before migrating credentials to OneCLI Secrets?

Yes, you need to run /update-nanoclaw first to prepare the deployment, then proceed with installing and configuring OneCLI Agent Vault to migrate Anthropic and container-facing credentials from .env into OneCLI Secrets.

Why should I migrate container-facing credentials from .env files into OneCLI Secrets?

You should migrate container-facing credentials from .env files to prevent agents from seeing raw keys, replacing direct environment variable exposure with centralized secret management and gateway-level policies for secure access.