Corey Haines
30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
269 lines
5.5 KiB
Markdown
269 lines
5.5 KiB
Markdown
# Brevo
|
|
|
|
All-in-one marketing platform (formerly Sendinblue) for email, SMS, and WhatsApp with contacts, campaigns, and transactional messaging.
|
|
|
|
## Capabilities
|
|
|
|
| Integration | Available | Notes |
|
|
|-------------|-----------|-------|
|
|
| API | ✓ | REST API v3 for contacts, campaigns, transactional email/SMS |
|
|
| MCP | - | Not available |
|
|
| CLI | ✓ | [brevo.js](../clis/brevo.js) |
|
|
| SDK | ✓ | Node.js, Python, PHP, Ruby, Java, C#, Go |
|
|
|
|
## Authentication
|
|
|
|
- **Type**: API Key
|
|
- **Header**: `api-key: {api_key}`
|
|
- **Get key**: SMTP & API settings at https://app.brevo.com/settings/keys/api
|
|
- **Note**: API key is only shown once on creation; store securely. Formerly used `api.sendinblue.com` base URL.
|
|
|
|
## Common Agent Operations
|
|
|
|
### Get account info
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/account
|
|
```
|
|
|
|
### List contacts
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/contacts?limit=50&offset=0
|
|
```
|
|
|
|
### Get contact by email
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/contacts/user@example.com
|
|
```
|
|
|
|
### Create contact
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/contacts
|
|
|
|
{
|
|
"email": "user@example.com",
|
|
"attributes": {
|
|
"FIRSTNAME": "Jane",
|
|
"LASTNAME": "Doe"
|
|
},
|
|
"listIds": [1, 2]
|
|
}
|
|
```
|
|
|
|
### Update contact
|
|
|
|
```bash
|
|
PUT https://api.brevo.com/v3/contacts/user@example.com
|
|
|
|
{
|
|
"attributes": {
|
|
"FIRSTNAME": "Updated"
|
|
},
|
|
"listIds": [3]
|
|
}
|
|
```
|
|
|
|
### Delete contact
|
|
|
|
```bash
|
|
DELETE https://api.brevo.com/v3/contacts/user@example.com
|
|
```
|
|
|
|
### Import contacts
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/contacts/import
|
|
|
|
{
|
|
"jsonBody": [
|
|
{ "email": "user1@example.com" },
|
|
{ "email": "user2@example.com" }
|
|
],
|
|
"listIds": [1]
|
|
}
|
|
```
|
|
|
|
### List contact lists
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/contacts/lists?limit=50&offset=0
|
|
```
|
|
|
|
### Create list
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/contacts/lists
|
|
|
|
{
|
|
"name": "Newsletter Subscribers",
|
|
"folderId": 1
|
|
}
|
|
```
|
|
|
|
### Add contacts to list
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/contacts/lists/{listId}/contacts/add
|
|
|
|
{
|
|
"emails": ["user1@example.com", "user2@example.com"]
|
|
}
|
|
```
|
|
|
|
### Remove contacts from list
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/contacts/lists/{listId}/contacts/remove
|
|
|
|
{
|
|
"emails": ["user1@example.com"]
|
|
}
|
|
```
|
|
|
|
### Send transactional email
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/smtp/email
|
|
|
|
{
|
|
"sender": {
|
|
"name": "My App",
|
|
"email": "noreply@example.com"
|
|
},
|
|
"to": [
|
|
{ "email": "user@example.com", "name": "Jane Doe" }
|
|
],
|
|
"subject": "Order Confirmation",
|
|
"htmlContent": "<html><body><p>Your order is confirmed.</p></body></html>"
|
|
}
|
|
```
|
|
|
|
### List email campaigns
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/emailCampaigns?limit=50&offset=0&type=classic&status=sent
|
|
```
|
|
|
|
### Create email campaign
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/emailCampaigns
|
|
|
|
{
|
|
"name": "January Newsletter",
|
|
"subject": "Monthly Update",
|
|
"sender": { "name": "My Brand", "email": "news@example.com" },
|
|
"htmlContent": "<html><body><p>Newsletter content</p></body></html>",
|
|
"recipients": { "listIds": [1, 2] }
|
|
}
|
|
```
|
|
|
|
### Send campaign immediately
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/emailCampaigns/{campaignId}/sendNow
|
|
```
|
|
|
|
### Send test email for campaign
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/emailCampaigns/{campaignId}/sendTest
|
|
|
|
{
|
|
"emailTo": ["test@example.com"]
|
|
}
|
|
```
|
|
|
|
### Send transactional SMS
|
|
|
|
```bash
|
|
POST https://api.brevo.com/v3/transactionalSMS/sms
|
|
|
|
{
|
|
"sender": "MyApp",
|
|
"recipient": "+15551234567",
|
|
"content": "Your verification code is 123456",
|
|
"type": "transactional"
|
|
}
|
|
```
|
|
|
|
### List SMS campaigns
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/smsCampaigns?limit=50&offset=0
|
|
```
|
|
|
|
### List senders
|
|
|
|
```bash
|
|
GET https://api.brevo.com/v3/senders
|
|
```
|
|
|
|
## API Pattern
|
|
|
|
Brevo uses standard REST with offset-based pagination (`limit` and `offset` parameters). Contact attributes use uppercase field names (FIRSTNAME, LASTNAME). Lists are nested under the contacts resource path. Transactional email uses the `/smtp/email` endpoint despite being REST-based.
|
|
|
|
## Key Metrics
|
|
|
|
### Contact Fields
|
|
- `email` - Email address
|
|
- `attributes` - Custom attributes (FIRSTNAME, LASTNAME, SMS, etc.)
|
|
- `listIds` - Associated list IDs
|
|
- `emailBlacklisted` - Email opt-out status
|
|
- `smsBlacklisted` - SMS opt-out status
|
|
- `statistics` - Engagement stats (with expand)
|
|
|
|
### Campaign Metrics
|
|
- `sent` - Total sends
|
|
- `delivered` - Successful deliveries
|
|
- `openRate` - Open percentage
|
|
- `clickRate` - Click percentage
|
|
- `unsubscribed` - Unsubscribe count
|
|
- `hardBounces`, `softBounces` - Bounce counts
|
|
|
|
### Transactional Email Response
|
|
- `messageId` - Unique message identifier for tracking
|
|
|
|
## Parameters
|
|
|
|
### Contact Parameters
|
|
- `email` - Contact email address
|
|
- `attributes` - Key-value object of custom attributes
|
|
- `listIds` - Array of list IDs to subscribe to
|
|
- `unlinkListIds` - Array of list IDs to unsubscribe from
|
|
|
|
### Campaign Parameters
|
|
- `name` - Campaign name
|
|
- `subject` - Email subject line
|
|
- `sender` - Object with `name` and `email`
|
|
- `htmlContent` / `textContent` - Email body
|
|
- `recipients` - Object with `listIds` array
|
|
- `type` - classic or trigger
|
|
|
|
## When to Use
|
|
|
|
- Multi-channel marketing (email + SMS + WhatsApp)
|
|
- Transactional email sending with tracking
|
|
- Managing contacts and segmented lists
|
|
- Creating and scheduling email campaigns
|
|
- SMS notifications and marketing
|
|
- Affordable all-in-one marketing automation
|
|
|
|
## Rate Limits
|
|
|
|
- API rate limits depend on plan (free tier: limited sends/day)
|
|
- Transactional email: varies by plan
|
|
- Contact imports: batch processing with async status
|
|
- Rate limit headers returned with responses
|
|
|
|
## Relevant Skills
|
|
|
|
- emails
|
|
- sms-marketing
|
|
- transactional-email
|
|
- lifecycle-marketing
|
|
- contact-management
|