Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill email-studio-administrationgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/email-studio-administration)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/email-studio-administration"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/email-studio-administration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/email-studio-administration"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/email-studio-administration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00087 | $0.03516 |
| Opus 5 | $0.00044 | $0.01758 |
| Sonnet 5 | $0.00017 | $0.00703 |
| Haiku 4.5 | $0.00009 | $0.00352 |
Grade A, and why
email-studio-administration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Studio Administration
This skill activates when a practitioner is creating, configuring, or troubleshooting email builds and sends in Salesforce Marketing Cloud Email Studio and Content Builder. It covers email creation methods, dynamic content, send classifications, A/B testing, suppression lists, triggered vs scheduled sends, and pre-send validation. It does NOT cover MCAE (Pardot) email, SMS or push channel configuration, or the Journey Builder entry-source and decision-split design.
Before Starting
Gather this context before working on anything in this domain:
- Business unit setup: Which Marketing Cloud Business Unit owns this send? Send classifications, suppression lists, and SAP IP addresses are scoped to a business unit.
- Data Extension or List structure: Dynamic content rules and subscriber segmentation depend on which subscriber attributes or DE fields are populated and typed correctly.
- Legal classification of the email: Determine early whether the email is Commercial (marketing offer, newsletter) or Transactional (order confirmation, password reset). This drives which Send Classification to use and whether CAN-SPAM footer + global unsubscribe handling is required.
- Most common wrong assumption: Teams assume that building multiple email versions is required to support different subscriber segments — dynamic content blocks eliminate this need entirely.
- Platform constraints: Content Builder has no hard limit on the number of dynamic content blocks per email, but extremely complex rule trees (20+ conditions) slow template rendering in the preview pane and should be tested.
Core Concepts
Content Builder vs Classic Email Studio
Marketing Cloud offers two email creation environments. Classic Email Studio is the legacy tool. Content Builder is the current authoring environment and is used for all new email development.
Content Builder supports two build methods:
- Drag-and-drop blocks: Assembles emails from pre-built content blocks (text, image, button, HTML). Each block is independently editable. Block-level permissions can restrict who changes certain areas.
- Raw HTML: A single HTML code block allows full control over markup. Required for pixel-perfect rendering or legacy template migration.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 239 lines · 87 tokens per session scan A 4f939f5d1719
email-studio-administration is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 3,516 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
consent-management-marketing
Email consent management in Marketing Cloud: configuring Subscription Centers, building Preference Centers on CloudPages, enforcing CAN-SPAM and GDPR requirements, and handling opt-out propagation. Trigger keywords: unsubscribe handling, CAN-SPAM compliance, GDPR consent tracking, publication lists, subscription…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
v3-use-utils
Documentation for reusable utility functions in a project, including validation, date formatting, CSS variables, permissions, local storage, and tokens.
ab-test-generator
Generate A/B test variants for affiliate content. Triggers on: "create A/B test", "test my headline", "optimize my CTA", "generate variants", "split test ideas", "improve click-through rate", "test my landing page copy", "headline alternatives", "CTA variations", "which version is better", "optimize conversions"…