Agent skill · AI & Agents

init-onecli

Install and initialize OneCLI Agent Vault. Migrates existing .env credentials to the vault. Use after /update-nanoclaw brings in OneCLI as a breaking change, or for first-time OneCLI setup.

NanoCo30,389★ · +78/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add nanocoai/nanoclaw --skill init-onecli --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Path: .claude/skills/init-onecli/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 30,426 · +37 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Initialize OneCLI Agent Vault This skill installs OneCLI, configures the Agent Vault gateway, and migrates any existing `.env` credentials into it. Run this after `/update-nanoclaw` introduces OneCLI as a breaking change, or any time OneCLI needs to be set up from scratch. **Principle:** When something is broken or missing, fix it. Don't tell the user to go fix it themselves unless it genuinely requires their manual action (e.g. pasting a token). ## Phase 1: Pre-flight ### Check if OneCLI is already working ```bash onecli version 2>/dev/null ``` If the command succeeds, OneCLI is installed, check for an Anthropic secret: ```bash onecli secrets list ``` If an Anthropic secret exists, tell the user OneCLI is already configured and working. Use AskUserQuestion: 1. **Keep current setup** — description: "OneCLI is installed and has credentials configured. Nothing to do." 2. **Reconfigure** — description: "Start fresh — reinstall OneCLI and re-register credentials." If they choose to keep, skip to Phase 5 (Verify). If they choose to reconfigure, continue. ### Check for native credential proxy ```bash grep "credential-proxy" src/index.ts 2>/dev/null ``` If `startCredentialProxy` is impo

What's inside
Steps it walks through
  1. Phase 1: Pre-flight
  2. Check if OneCLI is already working
  3. Check for native credential proxy
  4. Check the codebase expects OneCLI
  5. Phase 2: Install OneCLI
  6. Install the gateway and CLI
  7. Configure the CLI
  8. Set ONECLIURL in .env
  9. Wait for gateway readiness
  10. Phase 3: Migrate existing credentials
  11. Scan .env for credentials to migrate
  12. If credentials found in .env
  13. Offer to migrate other container-facing credentials
  14. If no credentials found in .env
Commands it runs
onecli version 2>/dev/null
onecli secrets list
grep "credential-proxy" src/index.ts 2>/dev/null
grep "@onecli-sh/sdk" package.json
curl -fsSL onecli.sh/install | sh
curl -fsSL onecli.sh/cli/install | sh
export PATH="$HOME/.local/bin:$PATH"
grep -q '.local/bin' ~/.bashrc 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
grep -q '.local/bin' ~/.zshrc 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
onecli config set api-host ${ONECLI_URL}
More from nanoclaw
All skills →
About this skill
What does the init-onecli skill do?

Install and initialize OneCLI Agent Vault. Migrates existing .env credentials to the vault. Use after /update-nanoclaw brings in OneCLI as a breaking change, or for first-time OneCLI setup.

How do I install it?

Run `npx skills add nanocoai/nanoclaw --skill init-onecli --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nanocoai/nanoclaw, a repository with 30,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going