Name: vmware
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

vmware

VMware integration. Manage data, records, and automate workflows. Use when the user wants to interact with VMware data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vmware/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete, copy-paste CLI commands and a clear overall sequence, but it spends tokens explaining VMware basics and lacks validation checkpoints around destructive action runs. Structure is clean with no external references needed.

Suggestions

Remove the opening paragraph explaining what VMware is; assume Claude's competence and lead directly with the integration workflow.

Add a validation/verification step before running destructive or batch actions (e.g., confirm target VM and power-state impact, then verify the result), to lift workflow clarity above the destructive-ops cap.

Tighten the "Agent Types" and best-practices prose, which currently reads as filler, into crisp directives.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens by explaining what VMware is ("VMware provides virtualization software and services. It's used by IT professionals..."), which Claude already knows and adds padding without earning its tokens.	3 / 5
Actionability	Guidance is fully executable and copy-paste ready: real commands ("membrane connection ensure", "membrane action run", "membrane request") with concrete flags, JSON input examples, and a flag table covering the common proxy cases.	5 / 5
Workflow Clarity	The connect→discover→run sequence is clear with explicit connection-state feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but running actions on VMware can be destructive (power state, record deletion) and the workflow includes no validation/verification checkpoint before or after such runs, so the destructive-ops cap at 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but the body is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices); it exceeds the 50-line simple-skill exception yet remains well-structured with only minor gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly uses third person and includes both a what and a when clause, but its actions and triggers are generic rather than VMware-specific. It is solid but could be sharpened with concrete capabilities and synonyms.

Suggestions

Replace generic actions ("Manage data, records") with concrete VMware capabilities such as managing virtual machines, power states, and tasks.

Expand the trigger clause with natural synonyms users say, e.g. vSphere, ESXi, virtual machines, or VM power operations.

Tighten the when clause to enumerate concrete trigger phrases ("Use when the user asks to manage VMs, check power states, or query VMware tasks").

Dimension	Reasoning	Score
Specificity	The description names the domain (VMware) and lists a few actions ("Manage data, records, and automate workflows"), but these are generic rather than concrete VMware-specific capabilities like provisioning VMs or managing power states, so it sits at the generic-actions anchor rather than the comprehensive one.	3 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with VMware data") are present, but the when clause is generic rather than enumerating concrete trigger phrases, matching the score-4 example.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with VMware data" surfaces the "VMware" keyword, but misses natural variations and synonyms users would say (vSphere, ESXi, virtual machines), matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	VMware is a clear, specific niche with low conflict risk, but the generic trigger wording ("interact with VMware data") leaves minor overlap risk versus a more tightly scoped trigger, placing it just below the distinct-triggers anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/vmware/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.