agentsclimarketplace

Brevo engagement designer

Skill tajoio/tajo-agent-skills/skills/brevo-engagement-designer

Open agent skills for commerce, marketing, CRM, lifecycle messaging, and integration APIs.

Install
npx -y skills add tajoio/tajo-agent-skills --skill brevo-engagement-designer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when drafting, reviewing, scheduling, or safely dispatching Brevo email, SMS, WhatsApp, or lifecycle campaigns with consent, approval, deliverability, budget, and performance guardrails.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 313 tokens by cl100k_base, as published. Nobody here has run it

Brevo Engagement Designer

Use this skill for engagement planning and dispatch workflows. The goal is to help an agent design useful sends without bypassing consent, approval, or deliverability constraints.

Dispatch Checklist

Before any send:

  1. Resolve the audience and channel.
  2. Confirm channel-specific consent and suppression filters.
  3. Confirm sender identity and reply-to behavior.
  4. Draft subject, preview text, and body.
  5. Check personalization variables and fallback values.
  6. Check budget, rate limits, and expected volume.
  7. Require human approval for promotional sends, large sends, or sensitive content.
  8. Schedule or send only after the above evidence is present.
  9. Summarize sent, skipped, failed, and cost-relevant outcomes.

Defaults

  • Keep email subject lines under 60 characters unless there is a clear reason.
  • Keep HTML email bodies compact and compatible with major clients.
  • Use staged rollout for large audiences.
  • Include unsubscribe or preference-management instructions for marketing.
  • Tag sends with a campaign or dispatch id for webhook correlation.

Refuse Or Escalate

Refuse or escalate when:

  • recipients do not have explicit opt-in for the channel
  • the user asks to disable consent filters
  • suppression, unsubscribe, complaint, or hard-bounce state is being ignored
  • the audience is too large for an unreviewed blast
  • sender identity is unverified
  • the message makes unsupported claims or creates legal/compliance risk

References

  • references/campaign-review-checklist.md

What ships with it: 1 file

1009 B alongside SKILL.md

references/

Gives 0 of the 12 instructions most design frontend skills give in 313 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • resolve the audience and channel
  • confirm channel-specific consent and suppression filters
  • confirm sender identity and reply-to behavior
  • draft subject preview text and body
  • check personalization variables and fallback values
  • check budget rate limits and expected volume

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.