CtrlK
BlogDocsLog inGet started
Tessl Logo

brevo-automation

Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas.

70

1.15x
Quality

58%

Does it follow best practices?

Impact

88%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/brevo-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides solid coverage of Brevo automation workflows with clear tool sequences and useful pitfall documentation. However, it suffers from redundancy (pitfalls repeated in sections and consolidated), lacks executable call examples despite being tool-oriented, and misses validation/error-recovery steps for destructive operations. The content would benefit from being more concise by leveraging the RUBE_SEARCH_TOOLS instruction (which provides schemas dynamically) rather than exhaustively listing parameters inline.

Suggestions

Add concrete, executable MCP tool call examples (e.g., showing an actual RUBE_SEARCH_TOOLS call followed by a BREVO_LIST_EMAIL_CAMPAIGNS call with real arguments) rather than just listing parameter names.

Add explicit validation checkpoints to workflows, e.g., 'Verify campaign exists and is in draft status before updating' or 'Confirm template deletion succeeded by re-listing templates'.

Reduce parameter listing verbosity since the skill already instructs to call RUBE_SEARCH_TOOLS for current schemas—keep only the most critical parameters and non-obvious pitfalls inline.

Consolidate pitfalls into the single 'Known Pitfalls' section rather than repeating them in each workflow section to reduce redundancy.

DimensionReasoningScore

Conciseness

The skill is fairly detailed and well-organized, but includes some redundancy—pitfalls are repeated across sections and again in a consolidated 'Known Pitfalls' section. The exhaustive parameter listings for every tool border on verbose given the instruction to always call RUBE_SEARCH_TOOLS first for current schemas, which would provide these details dynamically.

2 / 3

Actionability

The skill provides specific tool names, parameter names, and clear sequences, but lacks executable code examples showing actual MCP tool calls with concrete arguments. The 'Campaign Lifecycle' and 'Template Personalization' sections use plain text or template syntax rather than executable call examples, making it more descriptive than copy-paste ready.

2 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with labeled steps and tool ordering, but there are no explicit validation checkpoints or error recovery loops. For operations like updating campaigns or deleting templates (potentially destructive), there's no 'verify before proceeding' or 'check result and retry' guidance.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and a quick reference table, but it's monolithic—all parameter details, pitfalls, and patterns are inline in a single long file. The detailed parameter listings for each tool could be split into separate reference files, with the SKILL.md serving as a concise overview. No bundle files exist to offload this content.

2 / 3

Total

8

/

12

Passed

Description

67%

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 does well at specifying concrete capabilities and is highly distinctive due to the named platform and integration. Its main weaknesses are the lack of an explicit 'Use when...' trigger clause and missing some natural user terms like 'newsletter', 'email marketing', or 'transactional email' that would improve discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Brevo, Sendinblue, email campaigns, newsletters, or email marketing automation.'

Include additional natural trigger terms users might say, such as 'newsletter', 'email marketing', 'transactional email', 'email analytics', or 'contact lists'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: manage email campaigns, create/edit templates, track senders, and monitor campaign performance. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause. The instruction to 'always search tools first' is operational guidance, not a trigger condition. Per rubric guidelines, missing 'Use when' caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant keywords like 'Brevo', 'Sendinblue', 'email campaigns', 'templates', 'senders', and 'campaign performance'. However, it misses common user variations like 'marketing emails', 'newsletter', 'email marketing', 'transactional email', or 'email analytics'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive by naming both the platform (Brevo/Sendinblue) and the integration method (Rube MCP/Composio). This is a clear niche that is unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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
davepoon/buildwithclaude
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.