What makes vmware-pilot notable?

2.4K downloads. Trust evidence available

How should vmware-pilot be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

vmware-pilot

Use this skill whenever the user wants to design, execute, or manage complex multi-step VMware workflows with human approval gates and explicit, best-effort rollback. Pilot is the orchestration brain — it breaks a goal into steps across companion VMware skills (aiops, monitor, nsx, nsx-security, aria, vks, storage, avi), adds approval gates before destructive operations, and records per-step undo actions that run only when rollback is explicitly called, never automatically. Always use vmware-pilot for: "clone and test before applying to production", "VMware incident response with checkpoints", "investigate alert root cause", "VMware rolling restart with health checks", "baseline capture and drift detection", "rolling maintenance with AVI drain", or any VMware workflow needing approval gates or rollback. 15 built-in templates + custom YAML + AI-designed workflows. Do NOT use for single-step work — use vmware-aiops for one VM action, vmware-monitor for read-only queries, vmware-avi for load balancer queries.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.4k

Updated

Oct 9, 2026

Version

1.12.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.4K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.4K downloadsadoption · observed Oct 9, 2026
Latest release: 1.12.0release · observed Sep 19, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:vmware-pilot

Install using `clawhub skill install s171xgnmqse0nqvgqvqnaq5f9183kyre:vmware-pilot` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/zw008/vmware-pilot before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-zw008-vmware-pilot/snapshot"

Documentation

CLAWHUB

152,721 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: vmware-pilot
description: >
Use this skill whenever the user wants to design, execute, or manage complex multi-step VMware workflows with human approval gates and explicit, best-effort rollback.
Pilot is the orchestration brain — it breaks a goal into steps across companion VMware skills (aiops, monitor, nsx, nsx-security, aria, vks, storage, avi), adds approval gates before destructive operations, and records per-step undo actions that run only when rollback is explicitly called, never automatically.
Always use vmware-pilot for: "clone and test before applying to production", "VMware incident response with checkpoints", "investigate alert root cause", "VMware rolling restart with health checks", "baseline capture and drift detection", "rolling maintenance with AVI drain", or any VMware workflow needing approval gates or rollback.
15 built-in templates + custom YAML + AI-designed workflows.
Do NOT use for single-step work — use vmware-aiops for one VM action, vmware-monitor for read-only queries, vmware-avi for load balancer queries.
installer:
kind: uv
package: vmware-pilot
allowed-tools: [Bash]
metadata: {"openclaw":{"requires":{"anyBins":["vmware-pilot","uvx"]},"optional":{"env":["VMWARE_AUDIT_APPROVED_BY"]},"homepage":"https://github.com/vmware-skills/VMware-Pilot","emoji":"🧭","os":["macos","linux"]}}
compatibility: >
vmware-policy auto-installed as Python dependency (provides @vmware_tool decorator and audit logging). All workflow operations audited to ~/.vmware/audit.db.
No direct vCenter/NSX credentials: Pilot is an orchestration layer that delegates to companion skills (aiops, monitor, nsx, etc.) which handle their own auth.
Approval gates: Workflows pause for human review before destructive steps; a custom workflow (YAML, create_workflow, or AI-designed) with a destructive or unclassifiable step not preceded by a gate is rejected, and force=True cannot override that. Rollback is never automatic: a failed step stops the workflow, and undo happens only when rollback is called; it is best-effort, and on the MCP server the calling agent performs each rollback_tool call itself.
Pilot drives companion skills that change production (VM power, guest commands, network, storage, Kubernetes). Guest commands (vm_guest_exec, vm_guest_upload, …) and credential-returning steps (vks get_tkc_kubeconfig, get_supervisor_kubeconfig) are gated like destructive ones.
State persistence: SQLite-backed workflow state (~/.vmware/workflows.db, owner-only 0600 in a 0700 directory) survives restarts; secret-named params are masked before they are written. No webhooks, no outbound network calls.
Transitive dependencies: Only vmware-policy (audit/policy). No post-install scripts or background services.
---

# VMware Pilot

> **Disclaimer**: This is a community-maintained open-source project and is **not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom Inc.** "VMware" is a trademark of Broadcom. Source code is

_meta.json

{
  "ownerId": "kn7b067awq2s97bn3d7p5qfhw5827pxc",
  "slug": "vmware-pilot",
  "version": "1.12.0",
  "publishedAt": 1789790141850
}

references/agent-guardrails.md

# Operating vmware-pilot with a local / small model

Claude-class models drive this skill without special instruction. Smaller and
locally-hosted models — Llama 3.3 70B, Qwen, Mistral, and similar, served
through Goose, Ollama, or OpenShift AI — need explicit operating rules to call
tools reliably.

This page exists because an operator wrote those rules by hand first. The
guardrails below are adapted, with thanks, from the working configuration
[@juanpf-ha](https://github.com/juanpf-ha) developed while running
vmware-monitor and vmware-aria against a production vSphere estate with Llama
3.3 70B FP8 on an on-prem H100
([VMware-AIops#31](https://github.com/vmware-skills/VMware-AIops/issues/31)). The
cross-skill rules are identical across this family; the parts below marked
vmware-pilot are specific to this skill.

vmware-pilot is the odd one out. It manages no infrastructure of its own — it
designs multi-step workflows, tracks their state, and gates them on human
approval. Two consequences follow, and both matter more on a small model than
on a large one: **authoring a workflow is itself the write operation**, and
**pilot does not execute anything** — the calling agent does.

> **Disclaimer**: This is a community-maintained open-source project and is
> **not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom
> Inc.** "VMware" and "vSphere" are trademarks of Broadcom.

---

## First: the rules you no longer need to write

Several guardrails from the original configuration are now enforced by the
skill itself. Prompt instructions are advisory — a model can ignore them.
These are structural, so it cannot.

| Guardrail you would otherwise prompt for | Now enforced by |
|---|---|
| "Do not execute steps yourself — hand them back for a human to run" | **The dispatch contract.** Pilot never calls a companion skill's MCP tools; it returns a step description and the calling agent invokes the tool. This is architecture, not etiquette. |
| "Check the plan makes sense before running it" | **`review_workflow`** performs a structural sanity check and returns `approved` or `needs_revision`. It is a read tool that inspects a definition without executing it. |
| "Put an approval gate before anything destructive" | **Custom-workflow rejection.** In a custom workflow (YAML, `create_workflow`, or a draft), a destructive or unclassifiable step — or any step passing `confirm: True` — with no `require_approval` before it makes `create_workflow` / `confirm_draft` / `plan_workflow` refuse to save it and `run_workflow` refuse to run it — `force=True` does not override that. The refusal names the step and the gate to insert. |
| "Log every state change you make" | **The `@vmware_tool` decorator.** Every workflow transition is recorded to `~/.vmware/audit.db`, and `get_workflow_status` returns the state plus its audit log. |

The one guardrail this skill does not hand you: pilot's list tools return bare
collections, not the family `{items, returned, limit,

references/capabilities.md

# Capabilities — vmware-pilot

## MCP Tools (13 — 4 read, 9 write)

| # | Tool | Risk | Category | Description |
|---|------|------|----------|-------------|
| 1 | `get_skill_catalog` | low | Discovery | List all available skills and tools for workflow design |
| 2 | `list_workflows` | low | Discovery | List built-in + custom templates and active workflows |
| 3 | `design_workflow` | low | Design | Natural language goal → draft workflow for review |
| 4 | `update_draft` | medium | Design | Edit draft workflow steps, name, or description |
| 5 | `confirm_draft` | medium | Design | Finalize draft → state changes to PENDING |
| 6 | `plan_workflow` | medium | Execute | Create workflow from built-in/custom template |
| 7 | `create_workflow` | medium | Execute | Create custom workflow from step list (refused if a destructive step has no approval gate before it) |
| 8 | `run_workflow` | medium | Execute | Execute workflow, pauses at approval gates |
| 9 | `approve` | high | Control | Human approval to continue past approval gate |
| 10 | `rollback` | high | Control | Explicit, best-effort undo of steps pilot recorded as succeeded, in reverse order — never automatic. Previews (`blast_radius`) unless `confirm=True` |
| 11 | `get_workflow_status` | low | Control | Query workflow state, audit log, diff report |
| 12 | `review_workflow` | low | Discovery | Sanity-check a planned workflow before anyone runs it |
| 13 | `cancel_workflow` | high | Control | Cancel a workflow — moves it to the terminal CANCELLED state. Previews (`blast_radius`) unless `confirm=True` |

---

## Built-in Templates (15)

| # | Template | Steps | Approval | Skills Used | Risk |
|---|----------|-------|----------|-------------|------|
| 1 | `clone_and_test` | 6-7 | Yes | aiops, monitor | Medium |
| 2 | `incident_response` | 4 | Yes | monitor, aiops | Medium |
| 3 | `plan_and_approve` | 3 | Yes | aiops | High |
| 4 | `compliance_scan` | 1-3 | No | monitor, aria | Low |
| 5 | `network_segment_setup` | 3-6 | Yes | nsx, nsx-security | Medium |
| 6 | `vks_cluster_deploy` | 5 | Yes | vks | Medium |
| 7 | `rolling_restart` | 2+3n | Yes | aiops, monitor | Medium |
| 8 | `capacity_expansion` | 5 | Yes | aria, aiops, monitor | Medium |
| 9 | `disaster_recovery` | 5 | Yes | aiops, monitor, nsx | High |
| 10 | `patch_deployment` | 1+3n | Yes | aiops, monitor | Medium |
| 11 | `storage_expansion` | 6 | Yes | storage | Medium |
| 12 | `baseline_capture` | 1-5 | No | monitor, nsx, storage | Low |
| 13 | `baseline_audit` | 1-5 | No | monitor, nsx, storage, aria | Low |
| 14 | `baseline_remediate` | 3+n | Yes | varies | High |
| 15 | `investigate_alert` | 4 (8 with `deep_dive`) | Checkpoint | monitor, aria | Low |

---

## Orchestrated Skills (13)

Pilot does not call VMware APIs directly. It delegates to these skills. Two different
numbers matter here, and they are not the same thing:

- **Skill tools** — everything that skill exposes over MCP, all callable by the agent
  when it dispatches a step.

references/cli-reference.md

# CLI Reference — vmware-pilot

The `vmware-pilot` CLI is a **launcher, not a second interface to workflows**. It starts the
MCP server and reports its version — nothing else. Every workflow operation (design, plan,
run, approve, rollback, cancel) is performed via MCP tool calls through an AI agent or MCP
client.

---

## Commands

| Command | Description |
|---------|-------------|
| `vmware-pilot mcp` | Start the MCP server on stdio transport |
| `vmware-pilot version` | Print the installed version |
| `vmware-pilot --help` | Show usage |

## MCP Server Launch

```bash
# Recommended: installed entry point, never touches the network
uv tool install vmware-pilot==1.12.0
vmware-pilot mcp

# Fallback: uvx re-resolves against PyPI each start and fails behind a
# TLS-inspecting corporate proxy — set UV_NATIVE_TLS=true if you must use it
uvx --from vmware-pilot==1.12.0 vmware-pilot-mcp
```

The server runs on **stdio** transport and exposes 13 MCP tools (4 read, 9 write).

---

## MCP Tool Reference

### Discovery Tools

#### get_skill_catalog

Get available skills and tools for workflow design.

```
get_skill_catalog()
→ {aiops: {tools: {...}}, monitor: {...}, nsx: {...}, ...}
```

#### list_workflows

List built-in and custom templates, plus active workflows.

```
list_workflows()
→ {templates: [...], active_workflows: [...]}
```

### Design Tools

#### design_workflow

Create a draft workflow from natural language description.

```
design_workflow(
    goal="Migrate app01 to new network with firewall",
    constraints="approval before destructive steps"
)
→ {workflow_id: "wf-...", state: "draft", next_step: "..."}
```

#### update_draft

Edit a draft workflow's name, description, or steps.

```
update_draft(
    workflow_id="wf-...",
    name="app_migration",
    steps=[{action: "...", skill: "...", tool: "...", params: {...}}]
)
→ {workflow_id: "wf-...", steps: [...]}
```

#### confirm_draft

Finalize a draft workflow for execution (DRAFT -> PENDING).

```
confirm_draft(
    workflow_id="wf-...",
    save_as_template=True
)
→ {workflow_id: "wf-...", state: "pending"}
```

### Execution Tools

#### plan_workflow

Create a workflow from a built-in or custom template.

```
plan_workflow(
    workflow_type="clone_and_test",
    params={target_vm: "db01", change_spec: {memory_mb: 32768}}
)
→ {workflow_id: "wf-...", steps: [...]}
```

Available types: `clone_and_test`, `incident_response`, `plan_and_approve`, `compliance_scan`,
`network_segment_setup`, `vks_cluster_deploy`, `rolling_restart`, `capacity_expansion`,
`disaster_recovery`, `patch_deployment`, `storage_expansion`, `baseline_capture`,
`baseline_audit`, `baseline_remediate`.

#### create_workflow

Create a custom workflow directly from a step list. Refused — nothing saved —
if any destructive or unclassifiable step has no `require_approval` step before
it; the error names each step and the gate to insert.

```
create_workflow(
    name="quick_restart",
    description="Restart with health check

Github ReposUpdated 6h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.