Name: sendinblue
Rating: 53.6 (1 reviews)
Author: membranedev

sendinblue

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

Quality

60%

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/sendinblue/SKILL.md

Quality

Content

63%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 highly actionable with a clear, well-validated workflow, but it carries introductory fluff and inlines reference material that would benefit from being split into separate bundle files. Solid but not optimally lean.

Suggestions

Remove the introductory paragraph describing what Sendinblue is and trim narrative filler like 'so you can focus on the integration logic rather than auth plumbing'; Claude already understands these concepts.

Move the proxy request flag table and full connection state-machine details into a references file (e.g. references/proxy.md) and link to it from SKILL.md to improve progressive disclosure.

Add a brief 'Verify' note after running an action (e.g. check the output field for errors / confirm expected record count) to close the loop on batch and mutating operations.

Dimension	Reasoning	Score
Conciseness	Commands are lean, but the intro paragraph ('Sendinblue is a marketing automation platform...used by businesses of all sizes') and phrases like 'so you can focus on the integration logic rather than auth plumbing' explain concepts Claude does not need, matching anchor 3.	3 / 5
Actionability	It provides concrete, copy-paste commands (membrane login, connection ensure, action list/run) and a proxy flag table, with only minor gaps from placeholders like CONNECTION_ID and QUERY, matching anchor 4.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear and includes an explicit state-machine feedback loop (BUILDING→READY/CLIENT_ACTION_REQUIRED→poll again), with only minor validation gaps, matching anchor 4.	4 / 5
Progressive Disclosure	There are no bundle files and the body is over 50 lines with reference-like content (full proxy flag table, state-machine details) inlined rather than split out, matching anchor 3 despite good sectioning.	3 / 5
	Total	14 / 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 answers both what and when in third person, but its action verbs are generic and it lacks the natural trigger variations users would actually say. It is functional but under-specific.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Sendinblue actions such as 'create email and SMS campaigns, manage contact lists, and build automation workflows'.

Expand the trigger clause with natural phrasings users say, e.g. 'Use when the user wants to send email or SMS campaigns, manage contacts or contact lists, or build Sendinblue/Brevo automations'.

Consider mentioning Brevo (Sendinblue's current name) in the trigger to catch users who use the rebranded term.

Dimension	Reasoning	Score
Specificity	Phrases like 'Manage data, records, and automate workflows' name the Sendinblue domain but use minimal, generic actions rather than concrete operations, matching anchor 2.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Sendinblue data'), but the when could be more specific, matching anchor 4.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Sendinblue data' includes a relevant keyword but misses common natural variations users would say (email campaigns, contacts, SMS, Brevo), matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	The Sendinblue niche and 'interact with Sendinblue data' trigger are mostly distinct with only minor overlap risk against related marketing skills, matching anchor 4.	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/sendinblue/SKILL.md
Commit: f484c82

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