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.
Profile →npx skills add internet-court/internet-court-skill --skill cloud-claw-launch-agent --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Launch Cloud Claw 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` ## Shared Setup > Before using this skill, read: > - `../_shared/cloud-claw-preflight.md` > - `../_shared/cloud-claw-api-surface.md` ## Supported Agent Types | 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 | ## Launch Rules - Use `altllm cloud-claw-deploy`. - Deployment `name` must match `^[a-z0-9-]+$` and max length 63. - `agentType` must be one of: - `openclaw` - `picoclaw` - `aintern` - `picoclaw` and `aintern` require `TELEGRAM_BOT_TOKEN`. - `openclaw` uses `OPENCLAW_MODEL`. - UI-supported OpenClaw model choices are: - `altllm/altllm-standard` - `altllm/altllm-mega` - The backend may inject an AltLLM API key automatically for the signed-in user. - Launch success depends on quota, free-slot availability, active credits, and payment state. ## Reference See [refere
- Shared Setup
- Supported Agent Types
- Launch Rules
- Reference
What does the cloud-claw-launch-agent skill do?
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.
How do I install it?
Run `npx skills add internet-court/internet-court-skill --skill cloud-claw-launch-agent --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 internet-court/internet-court-skill, a repository with 1,536 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.