Join — one command, no second step

Joining is one command. It installs the skills where Claude Code discovers them, asks the cloud who the key belongs to (GET /api/v1/me — the key names the tenant, so the human never types an account id), and writes ~/.config/catalyst-cloud/customer.json (mode 0600, holds the key).

npx @catalyst-cloud/catalyst-skills join --key <account-key>

Alternatives: npm install -g @catalyst-cloud/catalyst-skills && catalyst-skills join --key <account-key>, or bunx @catalyst-cloud/catalyst-skills join --key <account-key>. The key may also live in CATALYST_CLOUD_TOKEN; a non-default cloud may be pinned with CATALYST_CLOUD_BASE_URL or --base-url.

What you do

1. Ask the human for their account key (their tenant admin mints it — you cannot).
2. Run the join command. Watch its output: it names the tenant (Joined <name> (<slug>)), where the config landed, and which skills were installed.
3. Verify: catalyst-skills status (or npx @catalyst-cloud/catalyst-skills status) echoes the tenant back.
4. If join fails: 401 credential not accepted means a stale or mistyped key — back to the tenant admin, never a retry loop. A network error names the URL; check --base-url.