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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill brevo-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively communicates specific capabilities for Brevo/Sendinblue automation with good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords. The operational instruction about searching tools first doesn't help Claude decide when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'when user mentions Brevo, Sendinblue, email marketing campaigns, or newsletter management'
Include additional natural keywords users might say: 'marketing emails', 'newsletter', 'email lists', 'subscribers', 'transactional emails'
| 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' with specific capabilities, but lacks an explicit 'Use when...' clause. The instruction 'Always search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Brevo', 'Sendinblue', 'email campaigns', 'templates', but missing common user variations like 'marketing emails', 'newsletter', 'email automation', or 'transactional emails'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct with specific platform names (Brevo/Sendinblue) and MCP tool reference (Rube MCP/Composio). Unlikely to conflict with other skills due to the specific email marketing platform focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of Brevo operations with clear workflow sequences and good pitfall documentation. However, it's verbose for a skill file, with parameter documentation that could live in a separate reference, and lacks concrete executable examples showing actual tool invocations with sample payloads.
Suggestions
Add 1-2 concrete executable examples showing actual RUBE tool calls with complete JSON payloads (e.g., a full BREVO_UPDATE_EMAIL_CAMPAIGN call)
Move detailed parameter lists to a separate BREVO_REFERENCE.md file, keeping only essential parameters inline
Consolidate the 'Pitfalls' subsections into the single 'Known Pitfalls' section to reduce repetition
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections, and some parameter descriptions could be tighter. The quick reference table at the end duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides good parameter documentation and tool sequences, but lacks executable code examples showing actual MCP tool calls with concrete payloads. The 'Campaign Lifecycle' and 'Template Personalization' sections use pseudocode/templates rather than copy-paste ready examples. | 2 / 3 |
Workflow Clarity | Clear multi-step sequences with explicit tool ordering marked as [Required]/[Optional]/[Prerequisite]. Setup section has numbered validation steps, and each workflow clearly sequences operations with appropriate checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (200+ lines) with detailed parameter lists that could be split into a separate reference file. The external toolkit docs link is good, but inline content could benefit from more aggressive splitting. | 2 / 3 |
Total | 9 / 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 | |
Table of Contents
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.