Name: vtex
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

vtex

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

Quality

66%

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/vtex/SKILL.md

Quality

Content

67%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 well-structured, actionable guide with concrete Membrane CLI commands and a clear connection workflow with polling checkpoints. Its main weaknesses are an explanatory intro that pads the token budget and inlined detail that could live in reference files.

Suggestions

Trim the introductory 'what is VTEX' paragraph; Claude does not need the platform explained and the section adds tokens without actionable value.

Remove the duplicated action-list command in 'Popular actions' or consolidate it with the earlier 'Searching for actions' example.

Consider moving the proxy flag table and clientAction state reference into a separate reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the intro paragraph explains what VTEX is ('composable and complete commerce platform... Think of it as an all-in-one e-commerce solution') and the 'Popular actions' section repeats the search command already shown, adding padding Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a flag table, with only minor gaps like unfilled <actionId>/<id> placeholders, fitting the 'mostly executable with minor gaps' anchor.	4 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with a polling checkpoint (--wait) and documented state transitions (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) that form a feedback loop, meeting the 'clear sequence with most checkpoints' anchor though error-recovery steps are only lightly sketched.	4 / 5
Progressive Disclosure	The single file is well-organized into clearly labeled sections (Overview, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) with no bundle files present, giving good structure; it inlines a fair amount (full proxy flag table, client-action states) that could be split out, keeping it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

66%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 establishes a clear, distinct VTEX niche with an explicit use-when trigger, but its capability list is generic ('manage data, records, automate workflows') rather than naming concrete commerce actions. Stronger specificity and richer trigger synonyms would raise it further.

Suggestions

Replace generic verbs with concrete VTEX capabilities, e.g. 'Manage catalog products and SKUs, query and update orders, and look up customer records.'

Expand the trigger with natural synonyms users say, e.g. 'Use when the user wants to work with VTEX orders, catalog, SKUs, customers, or marketplace data.'

Dimension	Reasoning	Score
Specificity	It names the domain (VTEX) and lists 'Manage data, records, and automate workflows', but these actions are generic rather than concrete commerce operations like orders, catalog, or SKUs, fitting the 'domain + 1-2 actions but not comprehensive' anchor and falling short of the multi-specific-action level above.	3 / 5
Completeness	Both a 'what' ('VTEX integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with VTEX data') are present, but the 'what' is somewhat generic and the trigger could be more specific, landing at the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with VTEX data' supplies the core 'VTEX' keyword and a natural trigger, but lacks common variations or synonyms (e.g. orders, catalog, marketplace), matching the 'some relevant keywords but missing variations' anchor rather than broad coverage.	3 / 5
Distinctiveness Conflict Risk	VTEX is a named, specific commerce platform and the trigger ('interact with VTEX data') is narrowly scoped, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/vtex/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.