Menu
Write and extend VM provisioning capabilities for clawctl. Use when adding new tools to the VM, modifying the provisioning pipeline, writing CapabilityDef modules, or working with lifecycle hooks and CapabilityContext SDK.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add new CLI commands to clawctl. Use when creating a new command, subcommand group, or modifying the CLI surface. Ensures all touchpoints are updated: handler, exports, commander wiring, README, shell completions, and tests.
Develop the guest CLI (claw) that runs inside the VM. Use when working on vm-cli commands, the JSON output protocol, doctor checks, CapabilityContext implementation, or the capability registry.
Understand and modify the VM provisioning workflow. Use when working on the host-side provisioning sequence, understanding what each phase installs, debugging provisioning failures, or modifying the idempotency/verification flow.
Understand clawctl's architecture and design decisions. Use when exploring the codebase structure, understanding package responsibilities, learning about the VM backend, mount system, onboarding flow, or making cross-cutting changes.
| name | extending-capabilities |
| description | Write and extend VM provisioning capabilities for clawctl. Use when adding new tools to the VM, modifying the provisioning pipeline, writing CapabilityDef modules, or working with lifecycle hooks and CapabilityContext SDK. |
Capabilities are the extension mechanism for VM provisioning. Each
capability is a CapabilityDef module that declares what it installs,
when it runs (lifecycle phase + hook timing), and what health checks it
provides.
name, version,
hooks (keyed by lifecycle phase), optional dependsOn, and optional
migrations.provision-system, provision-tools,
provision-openclaw, provision-workspace, bootstrap. Each phase
supports pre:, main, and post: timing slots.ctx.exec(),
ctx.fs, ctx.apt, ctx.systemd, ctx.net, ctx.profile,
ctx.agentsMd) that capabilities use for system access. Never import
vm-cli internals directly.ProvisionResult (installed / unchanged /
failed) and must be idempotent.doctorChecks on hooks, using
availableAfter for lifecycle-aware warnings.capability-state.json records installed
versions; version changes trigger migrations or re-provision.packages/capabilities/src/capabilities/CapabilityDef constantpackages/capabilities/src/index.tspackages/vm-cli/src/capabilities/registry.tsSee references/capabilities.md for the complete documentation including hook timing, runner mechanics, state tracking, migrations, core vs optional capabilities, and AGENTS.md managed sections.