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

Blog Docs Log in Get started

vero

Vero integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vero 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/vero/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 to the Membrane CLI integration pattern with strong executable commands and a clear connection-state feedback loop. Its main weaknesses are mild marketing/concept padding and the absence of an explicit validation checkpoint before destructive Vero actions.

Suggestions

Trim the intro paragraph and marketing phrasing (e.g. 'so you can focus on the integration logic rather than auth plumbing') since Claude already understands auth plumbing.

Add an explicit validation/confirmation step before running outward-facing actions, e.g. 'Before running send/broadcast actions, confirm the target segment and review the message payload with the user.'

If the proxy flag table and auth flow grow, move them into references/ files and link one level deep to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and brief explanations, but includes unnecessary padding such as the opening paragraph explaining what Vero is and marketing phrasing like 'so you can focus on the integration logic rather than auth plumbing' — fitting anchor 3's 'mostly efficient but includes some unnecessary explanation' rather than anchor 4's lean standard.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (login, connection ensure, action list/run with JSON input, request proxy) plus a full flag table, with only minor gaps from placeholders (CONNECTION_ID, <actionId>, QUERY) needing substitution — anchor 4 rather than anchor 5's fully covered common cases.	4 / 5
Workflow Clarity	The connect flow is explicitly sequenced with a real feedback loop (poll --wait, then branch on READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but running actions lacks an explicit validation or confirmation checkpoint before potentially destructive marketing operations (sending emails), so it sits at anchor 4 with a minor validation gap rather than anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices), with content appropriately placed inline; it scores 4 rather than 5 because the document is over 50 lines and the proxy/auth detail could be split into references if it grows.	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 is a solid third-person statement that covers both what the skill does and when to use it, with a distinct named-platform niche. Its main weakness is generic action vocabulary and trigger terms that miss the Vero-specific phrases (campaigns, segments, emails) users would naturally say.

Suggestions

Replace generic actions with concrete Vero operations, e.g. 'Send email campaigns, manage segments and customer records, and trigger behavioral workflows'.

Expand the trigger clause with natural Vero-specific terms, e.g. 'Use when the user wants to send Vero campaigns, manage segments, or automate customer messaging'.

Add file/extension or noun variations users actually say (campaigns, newsletters, events, push messages) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Vero) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Vero-specific operations like campaigns, segments, or events, so it is not comprehensive — matching anchor 3 and below anchor 4's 'several specific actions'.	3 / 5
Completeness	Answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Vero data'), but the trigger clause is generic rather than concrete trigger phrases, fitting anchor 4 and below anchor 5's explicit concrete triggers.	4 / 5
Trigger Term Quality	Includes the core term 'Vero' and 'interact with Vero data', but omits the natural Vero-specific phrases a user would actually say (email, campaign, segment, newsletter, push), leaving only some relevant keywords — matching anchor 3 and below anchor 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	Vero is a named specific platform giving it a clear niche with low conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing introduces minor overlap risk with other data/integration skills — anchor 4 rather than anchor 5's fully distinct triggers.	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/vero/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.