VMware Debug
Disclaimer: Community-maintained open-source project, not affiliated with, endorsed by, or sponsored by VMware, Inc. or Broadcom Inc. "VMware" and "vSphere" are trademarks of Broadcom. Source is publicly auditable under the MIT license.
The diagnostic brain of the VMware skill family. You bring the symptom (an error,
a log dump, a slow VM); this skill runs a systematic investigation, correlates
events from the other skills into one timeline, ranks root-cause hypotheses, and
tells you what to check next. It never touches vSphere — it connects to
nothing and never executes fixes; its only writes are to a local case ledger
under $OPS_HOME. Remediation is routed to vmware-aiops (single op) or
vmware-pilot (multi-step, gated), mirroring the vmware-harden → vmware-pilot
advisor/executor split.
See skills/vmware-debug/SKILL.md for the full
methodology, the event-envelope contract, and symptom routing.
MCP tools (14 — 7 read, 7 write)
The seven writes go to the local case ledger only; none reaches a VMware system.
Correlation — stateless, for a single look:
| Tool | What |
|---|---|
incident_timeline |
[READ] Correlate pre-fetched events → timeline + spikes + ranked hypotheses + next-check ideas |
list_symptom_categories |
[READ] List recognised symptom categories + what to check for each |
Investigation ledger — for an incident you will reason about over time:
| Tool | What |
|---|---|
case_open |
[WRITE] Define the event; returns a case id and the grade this environment can reach |
case_readiness |
[READ] What grade this environment can reach, per symptom category, before you start |
case_knowledge |
[READ] Which knowledge formats are accepted, what is mounted, and which entries apply to a case |
case_plan |
[READ] What to fetch next — skill, tool and purpose per step; recomputed from the case's current state |
case_list |
[READ] Cases, newest first |
case_get |
[READ] One case: scope, ledger sizes, grade history |
case_hypotheses |
[WRITE] Register a candidate explanation, or read the ledger of what supports and refutes each |
case_submit_evidence |
[WRITE] Record one retrieved fact, with its source, query and time basis |
case_record_gap |
[WRITE] Record what could not be retrieved, and how to close it |
case_timeline |
[WRITE] Correlate everything the case has collected into one timeline |
case_grade |
[WRITE] Recompute the conclusion grade from the ledger and record it |
case_close |
[WRITE] Record the final grade, archive, and name what was left open |
Offline / Air-Gapped Install (from source)
This project uses the modern PEP 517 build system (hatchling), so there is no
setup.py by design — that is expected, not a missing file. If you cloned the
source and hit ERROR: File "setup.py" or "setup.cfg" not found ... editable mode currently requires a setuptools-based build, your pip is older than 21.3 and
cannot do an editable (-e) install with a non-setuptools backend. Editable
mode is a developer convenience, not needed to run the tool — do one of:
# From the source tree — a normal (non-editable) install builds a wheel:
pip install . # NOT pip install -e .
# ...or upgrade pip first, and editable works too:
pip install --upgrade pip && pip install -e .
For a truly air-gapped host, build the wheels on a connected machine and copy them over — the target then needs no network:
# On a connected machine, collect this package + its dependencies as wheels:
pip wheel . -w dist # → dist/*.whl (or: uv build, for just this package)
# Copy dist/ to the air-gapped host, then install offline:
pip install --no-index --find-links dist vmware-debug
License
MIT.
1 maintainer
Metadata
1 maintainer
Release files for vmware-debug 1.13.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vmware_debug-1.13.2.tar.gz | 328.9 kB | Without provenance | Details for vmware_debug-1.13.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vmware_debug-1.13.2-py3-none-any.whl | Python 3 | none | any | Details for vmware_debug-1.13.2-py3-none-any.whl |
Total release size: 425.5 kB
Release files / vmware_debug-1.13.2.tar.gz
| Download URL | vmware_debug-1.13.2.tar.gz |
|---|---|
| Size | 328.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3ebc077f9c6db3e862cd8bb5c7ee4a8df330f72f07f9de49b3a603e6d397993
|
|
BLAKE2b-256 checksum How to use checksums |
70be46ecc80d9506bbd39e7268dad3027f809943597ea1a6109611fa6639d2af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Release files / vmware_debug-1.13.2-py3-none-any.whl
| Download URL | vmware_debug-1.13.2-py3-none-any.whl |
|---|---|
| Size | 96.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be4021ee239230aa1c0e35c5cacd06de4d92e4efbdee29919b2c17b462cc71c7
|
|
BLAKE2b-256 checksum How to use checksums |
43509b2c2dcc1407404f0d3e1e1513183f040a1a24fd6b77321fc7dadab93979
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.12
|
Security for vmware-debug 1.13.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
