Name: vext
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

vext

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

61%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 body is well-structured and actionably executable via Membrane CLI commands, but it opens with a non-instructional 'I don't have enough information' placeholder and lacks explicit validation/feedback loops for destructive or batch operations.

Suggestions

Remove the placeholder line 'I don't have enough information to describe Vext...' and replace it with a concise description of Vext and its entities.

Add an explicit validation/verification step after 'action run' and proxy requests (e.g., check the output/error fields and retry or report on failure) to support destructive and batch operations.

Trim redundant restatements of Membrane's automatic auth handling to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but it opens with the unhelpful admission 'I don't have enough information to describe Vext' and includes some over-explanation (e.g., restating Membrane auth behavior), so it is 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides concrete, copy-pasteable commands for install, login, connection ensure, action list/run, and proxy requests with a flag table, leaving only minor gaps (e.g., placeholder CONNECTION_ID), matching 'mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection setup sequence with READY/BUILDING/CLIENT_ACTION_REQUIRED states is reasonably sequenced, but there are no explicit validation checkpoints or feedback loops for batch/destructive actions like 'action run' or proxy mutations, capping it at 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) at one level with no nested bundle references; it is a self-contained overview with minor organization gaps, matching 'good structure; most content is appropriately placed'.	4 / 5
	Total	14 / 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 provides both a clear 'what' and a 'when' trigger and is anchored to the Vext domain, but its capability verbs are generic ('manage', 'automate') and its trigger phrasing lacks synonyms a user would naturally say.

Suggestions

Replace generic verbs ('manage', 'automate') with concrete Vext operations (e.g., 'create and query records, manage documents, trigger workflows').

Broaden the trigger with natural phrasings and synonyms, e.g. 'Use when the user wants to query, create, or update Vext records or run Vext workflows'.

Reference Vext entities (Documents, Pages, Accounts, Workspaces, Members) in the description to sharpen distinctiveness from generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('data, records', 'workflows') and the concrete actions 'manage' and 'automate', but the actions are minimal and generic with no enumerated operations, matching 'names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Vext data'), satisfying both; the 'when' could be more specific, matching 'has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	It includes the somewhat natural phrase 'interact with Vext data' but otherwise relies on the proper noun 'Vext' and generic terms ('data', 'records', 'workflows'); it is missing the common variations and synonyms users would naturally say, matching 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The Vext proper noun gives it a niche, but the surrounding trigger ('interact with data') is broad and could overlap with other data/automation skills, matching 'somewhat specific but could still overlap with similar skills'.	3 / 5
	Total	12 / 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/vext/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.