PranavNagrecha/AwesomeSalesforceSkills / skills/admin/email-studio-administration
email-studio-administration
VerifiedUse when building, configuring, or troubleshooting email sends in Marketing Cloud Email Studio and Content Builder. Triggers: 'dynamic content', 'send classification', 'A/B test email', 'Content Builder template', 'triggered send', 'suppression list', 'Commercial vs Transactional'. NOT for MCAE (Pardot) — use admin/mcae-pardot-setup. NOT for Journey Builder orchestration — use admin/journey-builder-administration.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.8 KB |
| references/examples.md | markdown | 6.6 KB |
| references/gotchas.md | markdown | 6.6 KB |
| references/llm-anti-patterns.md | markdown | 8.0 KB |
| references/well-architected.md | markdown | 6.0 KB |
| scripts/check_email_studio_administration.pyexecutable | script | 11.9 KB |
| templates/email-studio-administration-template.md | markdown | 3.7 KB |
templates/email-studio-administration-template.md
View on GitHub# Email Studio Administration — Work Template
Use this template when working on email creation, send configuration, or pre-send validation tasks in Marketing Cloud Email Studio and Content Builder.
## Scope
**Skill:** `email-studio-administration`
**Request summary:** (fill in what the user asked for)
**Send type:** (Scheduled batch / Triggered / Journey Builder send)
**Legal classification:** (Commercial / Transactional — confirm before proceeding)
## Context Gathered
Record the answers to the Before Starting questions from SKILL.md here.
- **Business unit:** (which BU owns this send)
- **Subscriber data structure:** (List or Data Extension; which fields are available for dynamic content rules)
- **Legal classification confirmed:** (Commercial or Transactional; rationale)
- **Known constraints:** (IP pool, SAP affinity, suppression list requirements)
- **Failure modes to watch for:** (Triggered Send activation status, dynamic content default coverage, A/B test audience size)
## Send Classification Configuration
- **Send Classification name:**
- **Sender Profile:** (From Name / From Address)
- **Delivery Profile:** (IP pool / physical address)
- **Unsubscribe Profile:** (Commercial global unsubscribe / Transactional separate opt-out)
- **CAN-SPAM footer:** (Required — Yes/No based on classification)
## Content Build Approach
- **Build method:** (Drag-and-drop blocks / Raw HTML)
- **Dynamic content blocks:** (List each block, its rule conditions in order, and the default variation)
| Block Name | Rule 1 | Rule 2 | Rule N | Default |
|---|---|---|---|---|
| (e.g., Hero Image) | Condition + variation | Condition + variation | ... | Default variation |
## A/B Test Configuration (if applicable)
- **Test dimension:** (Subject line / From name / Content / Send time)
- **Version A:**
- **Version B:**
- **Test split:** % → A / % → B / % → Holdout
- **Winner criteria:** (Open rate / Click rate / Manual)
- **Evaluation window:** (hours)
- **Auto-send winner:** (Yes / No)
- **Minimum open events per arm to trust the result:** (calculate from historical open rate)
## Suppression Configuration
- [ ] Auto-suppression active (bounces, global unsubscribes, spam complaints)
- [ ] Publication list suppression confirmed for send
- [ ] Global Suppression List reviewed — current address count: ____
- [ ] Emergency suppression process documented if needed during active send
## Pre-Send Validation Checklist
Copy the review checklist from SKILL.md and tick items as you complete them.
- [ ] Send Classification assigned and confirmed (Commercial / Transactional)
- [ ] CAN-SPAM footer present and correct for Commercial sends
- [ ] Every Dynamic Content block has a valid default variation
- [ ] Dynamic content rules tested with representative subscriber data per segment
- [ ] Content Detective run — spam score result: ____
- [ ] Test send delivered to seed list and reviewed by email owner
- [ ] Inbox Preview completed (Litmus) — target clients tested: ____
- [ ] Global Suppression List active and address count reviewed
- [ ] For A/B tests: winner criteria, evaluation window, and holdout % confirmed
- [ ] For Triggered Sends: definition status confirmed as "Active"
- [ ] Approval workflow completed (if required by BU policy)
## Approach
Which pattern from SKILL.md applies? Why?
(e.g., "Dynamic Content for Segmented Personalization — subscriber data has LoyaltyTier attribute with 4 values. Single email with 4-rule dynamic content blocks used instead of separate versions.")
## Notes
Record any deviations from the standard pattern and why.
(e.g., "Email build uses raw HTML because the design requires custom background image CSS not supported by drag-and-drop blocks.")
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |