CtrlK
BlogDocsLog inGet started
Tessl Logo

brevo-automation

Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.

44

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/brevo-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill provides a reasonable overview of Brevo operations via Rube MCP with good structural organization and a useful quick reference table. However, it suffers from lack of concrete executable examples (actual tool call syntax), missing validation/error-handling steps in workflows, and parameter documentation that could be offloaded to reference files. The content also has some redundancy between per-workflow pitfalls and the consolidated 'Known Pitfalls' section.

Suggestions

Add concrete, copy-paste-ready examples of actual MCP tool calls with specific parameter values (e.g., a complete RUBE_SEARCH_TOOLS call followed by a BREVO_LIST_EMAIL_CAMPAIGNS call with sample arguments).

Add validation checkpoints to each workflow, such as checking the response status after campaign updates and providing error recovery guidance for common failure modes (429 rate limits, unverified sender errors).

Move detailed parameter listings to a separate REFERENCE.md file and keep only the most essential parameters inline, reducing the main skill to an actionable overview.

Remove the redundant 'Known Pitfalls' section at the bottom or consolidate it with the per-workflow pitfalls to eliminate duplication, and remove the vacuous 'When to Use' section.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some unnecessary verbosity. The 'Known Pitfalls' section at the bottom repeats information already covered in per-workflow pitfalls sections. The 'When to Use' section at the end is vacuous. Some parameter listings are exhaustive where Claude could discover them via the tool schemas mentioned in prerequisites.

3 / 5

Actionability

The skill provides tool names, parameter lists, and sequences, but lacks executable code examples showing actual MCP tool calls with concrete arguments. The 'Campaign Lifecycle' pattern is pseudocode-level. There are no copy-paste-ready examples of calling RUBE_SEARCH_TOOLS or any Brevo tool with specific parameter values.

3 / 5

Workflow Clarity

Workflows have clear sequences with labeled steps and tool ordering, but lack validation checkpoints. There's no verification that a campaign update succeeded, no error handling guidance for failed API calls, and no feedback loops for retrying on failures. The setup section has a reasonable verification flow, but core workflows lack validation steps.

3 / 5

Progressive Disclosure

The content is structured with clear sections and a quick reference table, which is good. However, the document is quite long (~200 lines) with detailed parameter listings that could be split into separate reference files. No bundle files exist to offload the detailed parameter documentation, and everything is inlined in a single monolithic skill file.

3 / 5

Total

12

/

20

Passed

Description

39%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 identifies the specific platform (Brevo/Sendinblue) and integration path, which provides good distinctiveness, but it fails to list any concrete actions and completely lacks a 'Use when...' clause. The vague phrase 'email marketing operations' gives no indication of what specific tasks the skill can perform.

Suggestions

Add specific concrete actions such as 'create email campaigns, manage contact lists, send transactional emails, view campaign analytics'.

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about Brevo, Sendinblue, email campaigns, subscriber management, or newsletter automation'.

Include natural user terms and synonyms like 'newsletters', 'mailing lists', 'subscribers', 'email templates' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Brevo email marketing) and the integration mechanism (Composio's Brevo toolkit via Rube MCP), but provides no concrete actions—'automate operations' is vague and doesn't specify what operations (e.g., create campaigns, manage contacts, send transactional emails).

2 / 5

Completeness

Has a vague 'what' (automate email marketing operations) but no 'when' clause at all. There is no explicit guidance on when Claude should select this skill, which caps this dimension per the rubric guidelines.

2 / 5

Trigger Term Quality

Includes relevant keywords like 'Brevo', 'Sendinblue', 'email marketing', and 'Composio', which are useful trigger terms. However, it misses natural user phrases like 'send emails', 'email campaigns', 'contact lists', 'newsletters', or 'subscribers'.

3 / 5

Distinctiveness Conflict Risk

The mention of 'Brevo (formerly Sendinblue)' and 'Composio's Brevo toolkit via Rube MCP' makes it fairly distinct and unlikely to conflict with generic email or marketing skills. Minor overlap risk with other email marketing platform skills.

4 / 5

Total

11

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.