CtrlK
BlogDocsLog inGet started
Tessl Logo

vmcp-review

Reviews vMCP code changes for known anti-patterns that make the codebase harder to understand or more brittle. Use when reviewing PRs, planning features, or refactoring vMCP code.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An exemplar instruction-only skill: token-efficient, immediately actionable, with a clear workflow and a well-structured report template plus an explicit scope-exclusion section that routes non-goals elsewhere. The only minor gap is the absence of explicit validation checkpoints, which matters little for read-only review work.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows; every section (scope rules, severity definitions, report template, exclusions) earns its place. The Purpose section adds new information (target directories, dual use) beyond the description, so it is not padding.

5 / 5

Actionability

Concrete, executable guidance throughout: specific directories ("pkg/vmcp/", "cmd/vmcp/"), a specific rules file path, defined severity criteria, and a copy-paste-ready markdown report template with file:line format. As an instruction-only skill the absence of code is not penalized since the guidance is fully actionable.

5 / 5

Workflow Clarity

A clear three-step sequence (determine scope, detect anti-patterns, present findings) with a defined output format and an explicit empty-case instruction ("If no issues are found, say so explicitly"). Not 5 because there are no explicit validation checkpoints or feedback loops, though the read-only nature of review work makes that a minor gap.

4 / 5

Progressive Disclosure

The skill is under 60 lines with no bundle files (no references/, scripts/, or assets/ exist), and its sections are well organized with clear headers. The one reference to ".claude/rules/vmcp-anti-patterns.md" is an external auto-loaded rules file, clearly signaled and one level deep, not a buried reference.

5 / 5

Total

19

/

20

Passed

Description

82%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.

A strong description: third person, concise, with an explicit 'Use when...' clause containing three concrete triggers and a tightly scoped niche. The only gap is that it names just one capability rather than enumerating several specific actions.

DimensionReasoningScore

Specificity

"Reviews vMCP code changes for known anti-patterns that make the codebase harder to understand or more brittle" names the domain and one concrete action with its effects, but does not list several distinct actions. It fits the 'names domain and 1-2 concrete actions' anchor; not 4 because no broader set of specific capabilities is enumerated.

3 / 5

Completeness

Clearly answers what ("Reviews vMCP code changes for known anti-patterns...") and when ("Use when reviewing PRs, planning features, or refactoring vMCP code") with concrete trigger phrases. Not below 5 because both halves are explicit and specific.

5 / 5

Trigger Term Quality

"Use when reviewing PRs, planning features, or refactoring vMCP code" includes natural phrases users would say. Good coverage but missing common variations like "code review", "audit", or file extensions, so not 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific codebase ("vMCP code") with distinct triggers, giving it a clear niche with minimal conflict risk against generic review skills. It cannot score higher than the top anchor.

5 / 5

Total

17

/

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.

Validation — 16 / 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.