Name: verve
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

verve

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

Quality

61%

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/verve/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 content is well-structured and highly actionable with concrete CLI commands and a clear connection state-machine, but a leaked nonsensical opening line and a dangling 'Step 2' reference undermine conciseness and workflow clarity. Fixing those two defects and adding an explicit validation/checkpoint for batch or destructive action runs would meaningfully raise the score.

Suggestions

Delete the leaked model line 'I don't have enough information to do that...' at the top of the body — it is nonsensical padding that harms clarity.

Resolve the dangling 'skip to Step 2' reference: either label the next section 'Step 2: Searching for actions' or rephrase to 'skip to Searching for actions below'.

Add an explicit verify/confirm checkpoint before running batch or mutating actions (e.g. 'Confirm the connectionId and input payload before membrane action run on destructive operations') to satisfy the workflow validation requirement.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but it opens with a nonsensical leaked line ('I don't have enough information to do that...') and includes a few prose asides ('so you can focus on the integration logic rather than auth plumbing') that could be trimmed — matching the score-3 anchor of mostly efficient with some unnecessary content.	3 / 5
Actionability	It provides concrete executable commands throughout (login, connection ensure/get, action list/run, request) with a full proxy-options table, matching the score-4 anchor of mostly executable guidance with only minor gaps like the CONNECTION_ID placeholder.	4 / 5
Workflow Clarity	The connection flow has a real sequence with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop, but it references 'skip to Step 2' when no Step 2 is labeled and the section ordering does not map to that step, matching the score-3 anchor of steps present with checkpoints that are implicit or broken.	3 / 5
Progressive Disclosure	The body is organized into clear headed sections (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with content appropriately kept inline for a CLI integration skill and no nested references, matching the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	14 / 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 answers both 'what' and 'when' and targets a clearly distinct platform, but its action verbs are generic and its trigger vocabulary is limited to the single phrase 'Verve Group data'. Tightening the verbs and adding concrete trigger terms would raise it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions tied to Verve Group, e.g. 'list campaigns, pull reports, and run ad-group workflows'.

Expand the trigger with natural variations users might say, e.g. 'Use when the user wants to query Verve Group campaigns, ad groups, ads, or reports'.

Tie the 'when' clause to the overview entities already documented (Campaigns/Ad Groups/Ads/Reports) so the trigger is specific rather than 'interact with data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Verve Group integration') plus a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete — closer to the score-3 anchor than the multi-action score-4 anchor.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Verve Group data'), matching the score-4 anchor where both are present though the 'when' could be more specific.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Verve Group data' is natural, but the only real keyword is 'Verve Group' with no synonyms or variations, matching the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	'Verve Group integration' is a clearly named platform niche with a distinct trigger, giving mostly-distinct low-conflict behavior; not a perfect score-5 because the action phrasing remains somewhat generic.	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/verve/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.