extending-capabilities

星标16

分支0

更新时间2026年4月1日 09:12

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

TimBeyer

TimBeyer/clawctl

打开 GitHub 仓库查看创作者相关仓库

下载

Extending Capabilities

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.

Key concepts

CapabilityDef — a declarative constant with name, version, hooks (keyed by lifecycle phase), optional dependsOn, and optional migrations.
Lifecycle phases — provision-system, provision-tools, provision-openclaw, provision-workspace, bootstrap. Each phase supports pre:, main, and post: timing slots.
CapabilityContext SDK — sandboxed interface (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.
Steps return ProvisionResult (installed / unchanged / failed) and must be idempotent.
Doctor checks are declared via doctorChecks on hooks, using availableAfter for lifecycle-aware warnings.
State tracking — capability-state.json records installed versions; version changes trigger migrations or re-provision.

Adding a new capability

Create a module in packages/capabilities/src/capabilities/
Export a CapabilityDef constant
Export it from packages/capabilities/src/index.ts
Register it in packages/vm-cli/src/capabilities/registry.ts

Full reference

See references/capabilities.md for the complete documentation including hook timing, runner mechanics, state tracking, migrations, core vs optional capabilities, and AGENTS.md managed sections.

同仓库更多 Skills

同仓库

adding-cli-commands

TimBeyer/clawctl

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.

2026-04-0116

developing-vm-cli

TimBeyer/clawctl

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.

2026-04-0116

managing-provisioning

TimBeyer/clawctl

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.

2026-04-0116

understanding-architecture

TimBeyer/clawctl

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.

2026-04-0116

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.

Extending Capabilities

Key concepts

CapabilityDef — a declarative constant with name, version, hooks (keyed by lifecycle phase), optional dependsOn, and optional migrations.
Lifecycle phases — provision-system, provision-tools, provision-openclaw, provision-workspace, bootstrap. Each phase supports pre:, main, and post: timing slots.
CapabilityContext SDK — sandboxed interface (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.
Steps return ProvisionResult (installed / unchanged / failed) and must be idempotent.
Doctor checks are declared via doctorChecks on hooks, using availableAfter for lifecycle-aware warnings.
State tracking — capability-state.json records installed versions; version changes trigger migrations or re-provision.

Adding a new capability

Create a module in packages/capabilities/src/capabilities/
Export a CapabilityDef constant
Export it from packages/capabilities/src/index.ts
Register it in packages/vm-cli/src/capabilities/registry.ts

Full reference

See references/capabilities.md for the complete documentation including hook timing, runner mechanics, state tracking, migrations, core vs optional capabilities, and AGENTS.md managed sections.