Deploy and manage Alibaba Cloud Serverless applications using the licell CLI. Covers deploy, release, functions, env vars, domains, DNS, logs, OSS, database, cache, Supabase, and ECS queries and lifecycle operations.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Use the first command for discovery, the second for contract lookup, and the third for execution.
Schema Contracts
Raw CLI JSON output is emitted line-by-line with the @@LICELL_JSON@@ prefix. Each record currently conforms to licell-cli-record@1.0, then branches by type=event|result|error.
For licell <command> --help --output json, read help.kind and help.schemaVersion; the current contract is licell-help@1.0.
For licell catalog --output json, read kind and schemaVersion; the current catalog contract is licell-agent-command-catalog@1.0.
licell catalog --output json also declares the help schema and CLI record schema explicitly: licell-help@1.0 / licell-cli-record@1.0.
Agents should prefer nextActions[] as the stable next-step surface; recommendedFlow, decisionGuide, and remediation[] are supporting guidance layers.
For command-specific business payloads, keep reading the command help/catalog result descriptor; the three sections below only describe the shared CLI record envelope.
CLI Event Record · licell-cli-record@1.0
Streaming CLI event record for progress tracking, log bridging, and stage-aware automation.
kind: Fixed to licell-cli-record.
schemaVersion: CLI record schema version; currently 1.0.
type: Fixed to event.
ts: Event timestamp in ISO 8601 format.
command: Current command key, such as deploy or oss upload.
stage: Stable stage identifier, such as deploy, deploy.api, or auth.restore.
action: Stable action identifier, such as run, execute, or stdout.
status: start / ok / failed / skipped / info.
source: command / console / stream.
terminal: Whether this event marks the terminal state of the current action.
ok (optional): Present only on terminal success/failure events; true means success and false means failure.
commandKey (optional): Stable command key when the command can be matched from the CLI registry.
phase: Action phase, such as inspect, verify, or mutate.
priority: primary / secondary.
source: Action source, such as error-remediation.
When parsing strictly, match kind first and then verify schemaVersion; if a higher unknown version appears, fall back to a compatibility path instead of assuming the old shape.
