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.

1.15x

Quality

63%

Does it follow best practices?

Impact

88%

1.15x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/brevo-automation/SKILL.md

Quality

Content

57%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.

A well-structured, parameter-rich guide with genuine gotcha knowledge (mutual exclusivity, date formats, sender verification), weakened by duplication between workflow pitfalls and the 'Known Pitfalls' section, absent validation steps around destructive operations, and no example invocations. Everything lives in one inline file with no progressive disclosure.

Suggestions

Deduplicate: keep date-format, sender-verification, and exclusivity rules in one place (either the per-workflow Pitfalls or the Known Pitfalls section, not both).

Add validation before destructive/batch operations, e.g. a step in the delete-template workflow to check templateStatus is inactive before calling BREVO_DELETE_EMAIL_TEMPLATE.

Move per-endpoint parameter detail into a references/ file (e.g. references/parameters.md) and add one example Rube MCP tool invocation showing the actual call shape.

Dimension	Reasoning	Score
Conciseness	The parameter tables and pitfall lists are dense and mostly earn their tokens, but the 'Known Pitfalls' section restates per-workflow material verbatim ('startDate and endDate must be used together', sender verification, htmlContent/htmlUrl exclusivity appears three times), and the 'Powered by Composio' footer is padding. Matches anchor 3: mostly efficient but could be tightened.	3 / 5
Actionability	Concrete tool slugs, typed parameters with formats (e.g. 'YYYY-MM-DDTHH:mm:ss.SSSZ', 'splitRule: 1-99'), mutual-exclusivity rules, and a Quick Reference table give mostly executable guidance. Not 5 because no example tool invocation or payload appears anywhere, leaving the exact call shape to inference.	4 / 5
Workflow Clarity	Sequences are clear and setup has a real checkpoint ('Confirm connection status shows ACTIVE before running any workflows'), but destructive operations lack validation — 'BREVO_DELETE_EMAIL_TEMPLATE' has no pre-check that the template is inactive (only a pitfall note), and the campaign lifecycle ends with 'Send or schedule via Brevo UI' with no verification step. The destructive/batch validation cap applies.	3 / 5
Progressive Disclosure	The single file is well-sectioned with headers and a quick-reference table, but ~200 lines of per-endpoint parameter and API detail are all inlined with no bundle files and no one-level-deep references — content that would fit a reference file sits in SKILL.md.	3 / 5
	Total	13 / 20 Passed

Description

70%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.

A specific, well-scoped description that names the vendor stack and four concrete capability areas with good natural keywords including the Sendinblue synonym. Its main weakness is the absence of any 'use when' trigger guidance, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Brevo, Sendinblue, email campaigns, newsletters, or email templates.'

Include natural user phrasings like 'email marketing' and 'newsletter' alongside the existing vendor terms.

Mention related capability areas (contacts/lists) or drop the generic 'monitor campaign performance' in favor of a concrete action like 'view campaign statistics'.

Dimension	Reasoning	Score
Specificity	Quotes 'manage email campaigns, create/edit templates, track senders, and monitor campaign performance' — several concrete, specific actions in a named domain. Not 5 because 'monitor campaign performance' and 'track senders' are mildly generic and coverage has gaps (e.g., no mention of contacts/lists).	4 / 5
Completeness	The 'what' is clear (Brevo campaign/template/sender automation via Rube MCP), but there is no 'use when' trigger; 'Always search tools first for current schemas' is an operating instruction, not a usage condition. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes 'Brevo (Sendinblue)', 'email campaigns', 'templates', 'senders' — the vendor synonym pair is strong and users would naturally say these. Not 5 because common variations like 'email marketing', 'newsletter', or 'mailing list' are missing.	4 / 5
Distinctiveness Conflict Risk	Explicitly names 'Brevo (Sendinblue)' and 'Rube MCP (Composio)', a clear niche with distinct vendor-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/brevo-automation/SKILL.md
Commit: c9856ea

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