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

brevo

Brevo integration. Manage Persons, Organizations, Deals, Leads, Pipelines, Users and more. Use when the user wants to interact with Brevo 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/brevo/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 body is a strong, command-rich integration guide with a well-sequenced, state-validated connection workflow and good sectioning, held back only by an expendable introductory paragraph and the lack of validation guidance around its destructive table actions.

Suggestions

Cut the opening 'Brevo is a marketing automation and CRM platform...' paragraph and other explanatory padding to move conciseness toward level 4-5.

Add a brief validation/confirmation step before destructive actions (e.g. 'Confirm the contact exists via get-contact before delete-contact') so the workflow clarity cap from batch/destructive operations is lifted.

Consider moving the full 21-row Popular actions table into a references/actions.md file and keeping only the top few inline, improving progressive disclosure toward level 5.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opener 'Brevo is a marketing automation and CRM platform. It's used by businesses, especially small to medium-sized ones...' and prose like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude already knows, fitting the level-3 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean level-4.	3 / 5
Actionability	Concrete, copy-pasteable commands appear throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://app.brevo.com/" --json', 'membrane action run <actionId> ... --input ...') with a populated actions table, meeting level-4; minor placeholders like <agentType> and <actionId> keep it just short of the fully-substituted level-5.	4 / 5
Workflow Clarity	The connection flow is explicitly sequenced with state-based checkpoints and a feedback loop (ensure -> poll with --wait -> handle CLIENT_ACTION_REQUIRED -> poll again -> READY), matching level-4's 'clear sequence with most checkpoints'; it is not level-5 because the listed destructive actions (delete-contact) appear only in a table without their own validate-before-act guidance.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with the action catalog inlined as scannable tables, fitting level-4 'good structure; most content appropriately placed'; it is not level-5 since no one-level-deep references are signaled and the inline actions table could arguably live in a reference file.	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 cleanly covers both what and when with a clear, product-distinct trigger, but it leans on a single generic verb ('Manage') and omits concrete action verbs and natural keyword variations, capping specificity and trigger quality at mid-range.

Suggestions

Replace the generic 'Manage' with concrete action verbs (e.g. 'Create, update, list, and delete Contacts, Deals, Companies, and Tasks') to lift specificity toward level 4-5.

Expand the trigger clause with natural variations users would say, e.g. 'Use when the user wants to manage Brevo/Sendinblue contacts, deals, companies, email campaigns, or lists'.

Drop the vague 'and more' — it is filler that reduces both specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage Persons, Organizations, Deals, Leads, Pipelines, Users and more' name the domain and several concrete entity targets, but the single generic verb 'Manage' (plus vague 'and more') is not the multiple distinct concrete actions the level-4 anchor requires.	3 / 5
Completeness	It states both what ('Brevo integration. Manage Persons, Organizations, Deals...') and when ('Use when the user wants to interact with Brevo data'), fitting the level-4 anchor where both are present but 'when' could be more explicit; it is not the level-5 concrete multi-trigger phrasing.	4 / 5
Trigger Term Quality	The clause 'Use when the user wants to interact with Brevo data' supplies the natural trigger 'Brevo', but coverage stops there — missing common variations like 'Brevo contacts/deals', 'Sendinblue', or specific tasks users would name, matching the level-3 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The product-specific name 'Brevo' gives a clear niche with minimal conflict risk, but the broad 'Manage ... and more' framing leaves minor overlap risk with generic CRM skills, placing it at level 4 rather than the fully-distinct level 5.	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/brevo/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.