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.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/cloud-claw-launch-agent && cp -r /tmp/cloud-claw-launch-agent/vendored/altlayer/cloud-claw-launch-agent ~/.claude/skills/cloud-claw-launch-agentSKILL.md
# 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 [references/cli-reference.md](references/cli-reference.md) for payload examples and expected responses.
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.