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

—

Does it follow best practices?

Impact

88%

1.15x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A highly actionable, well-organized Brevo reference whose chief weaknesses are duplicated pitfall content, missing validation checkpoints on destructive operations, and a monolithic structure with no external reference files. Splitting reference material and consolidating pitfalls would improve conciseness and progressive disclosure.

Suggestions

Consolidate the duplicated pitfalls (date formats, htmlContent/htmlUrl exclusivity, sender verification) into the single 'Known Pitfalls' section to remove redundancy.

Add verify-before-act checkpoints to destructive workflows (e.g., confirm a template is inactive before calling BREVO_DELETE_EMAIL_TEMPLATE).

Move the detailed parameter reference and pitfall catalog into a separate reference file, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is largely lean, API-specific reference Claude would not already know, but pitfalls are duplicated across per-workflow 'Pitfalls' sections and the global 'Known Pitfalls' section (date formats, htmlContent/htmlUrl exclusivity, sender verification), so it could be tightened.	2 / 3
Actionability	It provides concrete tool slugs, exact parameter names, enum values, ISO date formats, and a Quick Reference table — copy-paste-ready guidance that is fully actionable for an MCP-tool skill.	3 / 3
Workflow Clarity	Setup includes an explicit validation checkpoint (confirm connection is ACTIVE), but destructive/batch operations like deleting templates and updating campaigns lack verify-before-act checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is a single ~195-line file with no bundle files, and substantial parameter reference and pitfall content that could be split into separate reference files is kept inline, so it is organized but not progressively disclosed.	2 / 3
	Total	9 / 12 Passed

Description

82%

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, distinctive description that concretely enumerates Brevo automation capabilities, but it omits an explicit 'when to use' trigger clause. Adding a Use-when sentence would raise completeness.

Suggestions

Add an explicit trigger clause such as 'Use when managing Brevo/Sendinblue email campaigns, templates, or senders' to satisfy the completeness 'when' requirement.

Consider adding common user variations like 'newsletters' or 'email marketing' to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'manage email campaigns, create/edit templates, track senders, and monitor campaign performance' — matching the highest anchor.	3 / 3
Completeness	It clearly answers 'what' the skill does but lacks any 'Use when…' or equivalent explicit trigger guidance for when Claude should invoke it, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Natural user-facing terms ('email campaigns', 'templates', 'senders', 'campaign performance') are present alongside the distinctive Brevo/Sendinblue product names, giving good coverage of what a user would say.	3 / 3
Distinctiveness Conflict Risk	The Brevo/Sendinblue email-marketing niche with named tooling (Rube MCP/Composio) is clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: 366e45b

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