Menu
Operate the VPS fleet — status, accounts, usage, ssh, exec. Use when asked about servers, teams, Claude logins, or subscription usage.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Dispatch and track goals across the fleet — use when asked to send work to a team, check goal progress, or verify a deploy.
Add one or more VPSes to the fleet and stand up their dev environment — scaffold the team yml, bootstrap tools, optimize the box, wire per-org secrets, hand off login. Use when asked to add a server/box/team, grow the fleet, or set up a dev environment on a VPS.
| name | fleet |
| description | Operate the VPS fleet — status, accounts, usage, ssh, exec. Use when asked about servers, teams, Claude logins, or subscription usage. |
All fleet state lives in fleet/teams/*.yml (schema: fleet/CLAUDE.md). All commands run from repo root.
| want | run |
|---|---|
| inventory | bin/cnc teams |
| health (ssh, claude auth, disk, running goals) | bin/cnc status |
| who's logged in / needs auth | bin/cnc accounts |
| token/cost per subscription | bin/cnc usage --days 7 |
| run a command everywhere | bin/cnc exec --all -- <cmd> |
| shell into a box | bin/cnc ssh <team> |
Rules:
bin/cnc ssh <team> --login in their terminal — never attempt the OAuth flow yourself.unreachable in status → check host/ssh_user in the team yml, then the VPN (wg_ip).fleet/teams/ (copy _example.yml) + bootstrap checklist in fleet/CLAUDE.md.