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.
69
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
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
namemust match^[a-z0-9-]+$and max length 63. agentTypemust be one of:openclawpicoclawaintern
picoclawandainternrequireTELEGRAM_BOT_TOKEN.openclawusesOPENCLAW_MODEL.- UI-supported OpenClaw model choices are:
altllm/altllm-standardaltllm/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 references/cli-reference.md for payload examples and expected responses.
- Repository
- internet-court/internet-court-skill
- Commit
fa89195
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.