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

Blog Docs Log in Get started

mav

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

Quality

Content

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

This is a well-structured, command-driven integration skill with a strong connection state machine and concrete CLI examples throughout. Its main weaknesses are a minor invocation inconsistency, a lack of validation guidance on the destructive/proxy side, and a low-value entity list that adds tokens without explanation.

Suggestions

Standardize the CLI invocation (pick either 'membrane' or 'npx @membranehq/cli@latest' and use it consistently, noting the alias once).

Add a validation/verification checkpoint before destructive proxy calls (e.g. 'For -X DELETE, confirm the target id and dry-run or list the resource first').

Either annotate the Mav Overview entity list with one-line descriptions or move it to a reference file so the bullets earn their tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and a focused flags table, though the unexplained entity bullet list and the product-intro paragraph add minor tokens that could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It gives copy-paste-ready commands for install, login, connection ensure/get, action list/run, and request with flag tables, but the invocation form is inconsistent ('membrane' vs 'npx @membranehq/cli@latest action list'), a minor gap keeping it just below fully executable.	4 / 5
Workflow Clarity	The connection flow is a clear state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling and a re-auth feedback loop, but the action-running and proxy (DELETE) side lacks explicit validation checkpoints, leaving minor validation gaps.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well organized into clear sections (Overview, Working with Mav, Install, Auth, Connecting, Searching, Proxy, Best practices) and content is appropriately inline, with only minor organization gaps like the unexplained entity list.	4 / 5
	Total	16 / 20 Passed

Description

57%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 correctly pairs a what-statement with an explicit Use-when trigger in third person, but its capability verbs are generic and the trigger vocabulary is thin beyond the product name. It is distinct because Mav is a named product, yet it reads more as a category label than a precise capability list.

Suggestions

Replace generic verbs with concrete Mav capabilities (e.g. 'Send email/SMS campaigns, manage contacts and conversations, schedule posts') to lift specificity.

Add natural trigger synonyms users would say (e.g. 'Mav, Mav campaigns, Mav contacts, marketing automation') beyond the single 'Mav data' phrase.

Tighten the 'Use when' clause to name the situations that map to this skill (e.g. 'Use when the user wants to send or schedule Mav campaigns, manage contacts, or automate marketing workflows').

Dimension	Reasoning	Score
Specificity	It names the Mav domain and lists actions ('Manage data, records, and automate workflows'), but every verb is generic and abstract rather than a concrete capability, matching the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	It supplies both a 'what' ('Mav integration. Manage data, records, and automate workflows') and an explicit 'Use when...' trigger ('Use when the user wants to interact with Mav data'), though the 'when' could be more specific, matching the both-present anchor.	4 / 5
Trigger Term Quality	It surfaces the relevant product keyword 'Mav' / 'Mav data' and a natural-ish trigger ('interact with Mav data'), but offers no synonyms, variations, or extensions, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Mav integration' ties the skill to a specific named product with a distinct trigger, giving it a clear niche and low conflict risk, but the generic 'manage data, records' phrasing leaves minor overlap with general data skills.	4 / 5
	Total	13 / 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/mav/SKILL.md
Commit: f484c82

Reviewed: 6 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.