Brevo deep api operator
Skill tajoio/tajo-agent-skills/skills/brevo-deep-api-operator
Open agent skills for commerce, marketing, CRM, lifecycle messaging, and integration APIs.
npx -y skills add tajoio/tajo-agent-skills --skill brevo-deep-api-operatorAssembled 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 working with Brevo API operations for contacts, lists, custom events, transactional email, transactional SMS, webhooks, bounces, suppression, rate limits, or API-backed lifecycle messaging.
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
2.8 KB, 511 tokens by cl100k_base, as published. Nobody here has run it
Brevo Deep API Operator
Use this skill to plan or execute Brevo-bound API work with production discipline. Prefer official Brevo documentation and OpenAPI evidence over guesses.
Operating Model
- Classify the task: contact sync, list assignment, behavioral event tracking, transactional messaging, CRM object sync, webhook handling, suppression, or reporting.
- Confirm required inputs before selecting an endpoint.
- Use stable identifiers. Contacts need an email, phone number, or deterministic external id. Events need an event name and at least one contact identifier.
- Treat marketing consent as data, not prose. Do not send promotional messages without channel-specific opt-in evidence.
- Use webhooks for delivery, bounce, unsubscribe, complaint, inbound email, and campaign feedback when available.
- Treat hard bounces, complaints, spam reports, and unsubscribe events as send-eligibility changes. Do not suppress solely on a soft bounce.
- Respect Brevo rate limits. On
429, use vendor reset headers or standardRetry-After, then bounded jittered retry. - Keep API keys in environment variables or secret stores. Never print or embed secret values.
Endpoint Selection
- Contact upsert: use Brevo contact create/update semantics with update enabled when appropriate.
- Bulk contacts or list assignment: prefer import/bulk workflows when volume is high.
- List membership: require a known list id and a known or just-created contact.
- Custom event: require
event_nameplus contact identity. Normalize event names to portable identifiers. - Transactional email: require recipient, verified sender, subject, and either template id or approved HTML/text.
- Transactional SMS: require recipient phone number, sender constraints, and message body.
- Webhooks: require signature verification, idempotency, replay handling, and dead-letter behavior.
When To Stop
Stop and ask for evidence when:
- The request lacks a required identifier, list id, sender, template, or consent basis.
- The endpoint appears only in generated or community docs.
- Webhook verification cannot be implemented.
- A write path has no idempotency or replay plan.
- The user asks to bypass consent, suppression, unsubscribe, or complaint handling.
References
references/contacts-lists-identity.mdreferences/events-and-automations.mdreferences/transactional-messaging.mdreferences/webhooks-bounces-suppression.mdreferences/rate-limits-retries.md
What ships with it: 5 files
5.1 KB alongside SKILL.md