CtrlK
BlogDocsLog inGet started
Tessl Logo

brevo-automation

Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/brevo-automation/SKILL.md

The canonical home for this skill is brevo-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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.

The body is well-organized and actionable with concrete tool sequences and parameters, but it carries redundant pitfall repetition, a filler closing section, no post-operation validation loops, and no progressive disclosure into bundle files.

Suggestions

Remove the duplicated 'Known Pitfalls' section (or trim it to only pitfalls not already stated per-workflow) and delete the filler 'When to Use' section.

Add explicit validation feedback loops after batch/significant operations, e.g. re-list the campaign/template after update to confirm the change applied.

Move the detailed parameter reference tables into a separate reference file (e.g. references/params.md) and link to it from each workflow, keeping SKILL.md an overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material, but the 'Known Pitfalls' section re-states date-format and sender-verification pitfalls already covered per-workflow, the intro repeats the frontmatter description, and the closing 'When to Use' section is filler ('applicable to execute the workflow or actions described in the overview').

3 / 5

Actionability

Concrete tool slugs, numbered tool sequences, and parameter tables with types/formats give mostly executable guidance for the MCP context; minor gaps include no example request payloads or response-parsing snippets.

4 / 5

Workflow Clarity

Sequences are present and Setup includes a validation checkpoint (confirm connection ACTIVE), but the campaign/template update workflows lack post-action validation feedback loops, and the rubric caps batch/significant operations without validation at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the entire API reference (parameter lists, pitfalls) is inlined in one ~190-line file; structure is reasonable via headers, but content that could live in a separate reference file is all inline with no one-level-deep references.

3 / 5

Total

13

/

20

Passed

Description

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

The description is well-scoped to a distinct platform niche but lacks concrete action verbs and any explicit 'when to use' trigger guidance. Adding specific capabilities and a Use-when clause would materially improve it.

Suggestions

Replace the generic 'Automate ... operations' with concrete actions, e.g. 'Create and update email campaigns, manage templates, and list verified senders'.

Append an explicit trigger clause, e.g. 'Use when the user wants to manage Brevo/Sendinblue email campaigns, templates, or senders via Rube MCP.'

Add common natural terms users say ('campaigns', 'templates', 'newsletter') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain precisely ('Brevo (formerly Sendinblue) email marketing') but the only action verb is the generic 'Automate ... operations', with no concrete actions listed (e.g. send campaigns, manage templates).

2 / 5

Completeness

It states clearly what the skill does, but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural product terms ('Brevo', 'Sendinblue', 'email marketing') are present, but common user phrasings like 'campaigns', 'templates', or 'newsletter' are missing, and 'Composio'/'Rube MCP'/'toolkit' are technical jargon rather than user-spoken triggers.

3 / 5

Distinctiveness Conflict Risk

The narrow platform scoping ('Brevo/Sendinblue email marketing via Composio's Brevo toolkit via Rube MCP') gives it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.