internet-court/cloud-claw-launch-agent
Use this skill when the user wants to launch a new AltClaw, OpenClaw, PicoClaw, or Ottie deployment through Cloud Claw. Covers the same user-facing fields and constraints exposed in the Cloud Claw UI, using the local altllm cloud-claw-* commands. Do NOT use for post-launch lifecycle tasks like start/stop/delete/logs; use cloud-claw-manage-vm.
npx skills add https://github.com/internet-court/internet-court-skill --skill cloud-claw-launch-agent
Use this skill for the new deployment workflow exposed in the Cloud Claw UI, via the local CLI commands in this repository.
The implementation source of truth is the sibling repository:
../cloud-claw> Before using this skill, read:
> - ../_shared/cloud-claw-preflight.md
> - ../_shared/cloud-claw-api-surface.md
| Agent Type | Internal Value | User-facing Notes |
|---|---|---|
| OpenClaw | openclaw | paid-tier path, Telegram + web dashboard |
| PicoClaw | picoclaw | Telegram-only |
| Ottie | aintern | Telegram-only, self-evolving fork path |
altllm cloud-claw-deploy.name must match ^[a-z0-9-]+$ and max length 63.agentType must be one of:openclawpicoclawainternpicoclaw and aintern require TELEGRAM_BOT_TOKEN.openclaw uses OPENCLAW_MODEL.altllm/altllm-standardaltllm/altllm-megaSee references/cli-reference.md for payload examples and expected responses.
Take internet-court/cloud-claw-launch-agent from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.