CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

1.15x
Quality

66%

Does it follow best practices?

Impact

88%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

65%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 content is well-structured and highly actionable with concrete tool and parameter detail, organized into clear workflows. Its weaknesses are redundant recap sections (Quick Reference / Known Pitfalls) and the absence of validation checkpoints on destructive update/delete operations.

Suggestions

Add explicit validation/verification steps to the update and delete workflows (e.g., re-fetch the campaign/template after update and confirm fields, or verify a template is inactive before deleting) to lift the workflow clarity cap.

Remove or consolidate the redundant "Known Pitfalls" and "Quick Reference" sections whose content already appears per-workflow, to improve conciseness.

Optionally include one concrete example tool-call payload (arguments object) for the most common operation to push actionability to 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-structured parameter lists, but the "Known Pitfalls" and "Quick Reference" sections repeat pitfalls and params already stated per workflow, adding avoidable tokens.

3 / 5

Actionability

Concrete tool slugs, exact parameter names, valid value sets, and ISO date formats give mostly executable guidance, with only minor gaps (no literal example call payloads).

4 / 5

Workflow Clarity

Sequences are clear with Required/Optional tags and prerequisites, but update/delete operations (campaign update, template delete) have no validation or verification checkpoints, capping workflow clarity at 3 per the destructive/batch guideline.

3 / 5

Progressive Disclosure

As a single self-contained file with no external references needed, it is well-organized with clear section headers, qualifying for the simple-skill exception at the top of the scale.

5 / 5

Total

15

/

20

Passed

Description

67%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 specific and distinctive, listing four concrete Brevo actions clearly. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps both completeness and trigger term quality.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when the user wants to automate Brevo/Sendinblue email marketing, campaigns, or templates") to raise completeness above 3.

Include natural synonyms and trigger phrases users would say, such as "Sendinblue", "email blasts", or "newsletter sends", to improve trigger term quality.

Keep the concise action list as-is; it already anchors specificity and distinctiveness well.

DimensionReasoningScore

Specificity

"manage email campaigns, create/edit templates, track senders, and monitor campaign performance" lists multiple specific concrete actions with comprehensive coverage of the Brevo domain.

5 / 5

Completeness

The description clearly states what the skill does across four actions, but lacks any explicit "when" / "Use when..." trigger clause, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Terms like "email campaigns", "templates", and "senders" are relevant and somewhat natural, but there are no "Use when..." trigger phrases and no synonyms/extensions, leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

Brevo (Sendinblue) via Rube MCP (Composio) is a clear niche with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

16

/

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
davepoon/buildwithclaude
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.