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
58%
Does it follow best practices?
Impact
88%
1.15xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/brevo-automation/SKILL.mdQuality
Discovery
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 listing specific capabilities and is clearly tied to a distinct platform (Brevo/Sendinblue), making it easy to distinguish from other skills. Its main weakness is the lack of an explicit 'Use when...' clause with trigger conditions, and it could benefit from broader natural language trigger terms like 'email marketing' or 'newsletter'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Brevo, Sendinblue, email marketing campaigns, or newsletter management.'
Include additional natural trigger terms users might say, such as 'email marketing', 'newsletter', 'mailing list', 'transactional email', or 'email analytics'.
| Dimension | Reasoning | Score |
|---|---|---|
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 'email marketing', 'newsletter', 'transactional email', 'email analytics', or 'mailing list'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform names (Brevo/Sendinblue) and the specific integration method (Rube MCP/Composio). Unlikely to conflict with other skills unless there are multiple Brevo-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 operations with clear tool sequences and useful pitfall documentation. Its main weaknesses are the lack of executable examples (actual MCP call syntax), missing validation/verification steps in workflows, and verbose inline parameter documentation that could be offloaded to reference files. The quick reference table at the end is a strong organizational element.
Suggestions
Add concrete, executable MCP call examples showing exact invocation syntax for at least the most common operations (e.g., listing campaigns, creating a template).
Add explicit validation checkpoints to workflows, such as verifying a campaign exists before updating it, or confirming sender verification before creating a campaign.
Move detailed parameter listings to a separate REFERENCE.md file and keep only the most essential parameters inline, since the skill already instructs users to call RUBE_SEARCH_TOOLS for current schemas.
Add a brief error handling/recovery pattern showing what to do when common failures occur (e.g., unverified sender, rate limit hit).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-organized, but includes some verbose parameter listings that could be more concise. The exhaustive enumeration of every parameter for each tool adds bulk; Claude could discover these via RUBE_SEARCH_TOOLS as the skill itself instructs. Some sections like 'Manage Senders' are padded for a very simple operation. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear sequences, which is good. However, there are no executable code examples or concrete MCP call examples showing exact invocation syntax. The 'Campaign Lifecycle' and 'Template Personalization' sections use plain text/pseudocode rather than actual executable calls. The guidance is specific but not copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Prerequisite. However, there are no validation checkpoints or error recovery feedback loops. For operations like updating campaigns or deleting templates (potentially destructive), there's no 'verify before proceeding' step. The setup section has a good verification flow, but core workflows lack validation steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's quite long and monolithic. The detailed parameter listings for each tool could be split into separate reference files. The single external link to Composio docs is helpful, but the skill would benefit from splitting the detailed parameter documentation into a separate REFERENCE.md file. | 2 / 3 |
Total | 8 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- 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.