CtrlK
BlogDocsLog inGet started
Tessl Logo

deploying-vmcp-locally

Deploys a VirtualMCPServer configuration locally for manual testing and verification

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/deploying-vmcp-locally/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a tight, actionable deployment runbook with a well-sequenced workflow, explicit verification, and useful troubleshooting feedback loops. It earns strong scores across all dimensions, with only minor gaps around placeholder substitution, in-step validation checkpoints, and absence of split reference files.

DimensionReasoningScore

Conciseness

The body is command-focused and assumes Claude's familiarity with kubectl/Kind/Helm without explaining them, with only minor instances (e.g. some troubleshooting prose) that could be trimmed, fitting the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

Commands are concrete and largely copy-paste-ready including full curl/JSON MCP payloads, but placeholders like <path-to-vmcp-yaml>, <name>, and <port> require substitution, leaving minor gaps that fit the 'mostly executable' anchor.

4 / 5

Workflow Clarity

A clearly numbered 1-7 sequence pairs an explicit verification step with troubleshooting feedback loops for error recovery, but in-step validation checkpoints (e.g. confirm the pod is Ready before testing the endpoint) are only implicit, landing at the 'clear sequence with most checkpoints' anchor rather than 5.

4 / 5

Progressive Disclosure

Sections are well organized and the example-YAML table provides a clear one-level-deep reference, but the skill is over 50 lines with troubleshooting and examples kept inline rather than split into bundle files, fitting 'good structure; minor organization gaps'.

4 / 5

Total

16

/

20

Passed

Description

53%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 clearly states what the skill does for a specific niche product but omits any explicit 'Use when...' trigger guidance, which caps its completeness and limits trigger-term quality. Adding a trigger clause naming natural user phrases would raise the score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you need to deploy or test a VirtualMCPServer configuration locally before applying it to a real cluster.'

Include natural trigger phrases and synonyms users would actually say (e.g. 'test vMCP locally', 'verify a VirtualMCPServer deployment', 'try out vMCP in Kind') to improve trigger-term coverage.

Name a couple more concrete actions beyond 'Deploys' (e.g. 'apply, verify, and exercise') to move specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('VirtualMCPServer configuration') and one concrete action ('Deploys'), while 'manual testing and verification' describes purpose rather than distinct actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The description gives a clear 'what' but no explicit 'Use when...' trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3 even though 'for manual testing' weakly implies when.

3 / 5

Trigger Term Quality

Relevant terms like 'deploy locally', 'test', and 'verify' are present, but 'VirtualMCPServer configuration' is niche-product jargon and common synonyms or variations are missing, fitting the 'some relevant keywords' anchor.

3 / 5

Distinctiveness Conflict Risk

The unique product name 'VirtualMCPServer' carves a clear niche with minimal conflict risk, but limited trigger phrases keep it just below the comprehensive distinctiveness anchor.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stacklok/toolhive
Reviewed

Table of Contents

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.