aaron-marketing-skills is a collection of 120 AI-agent skills covering marketing work such as brand narrative, search optimization, social media, email, advertising, influencer campaigns, and launches. Marketers and agent users can install it as a plugin, use its portable skills, or run its described bot team. The catalogue entries are components of this marketing workflow.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skillsnpx agentmods add skills/aaron-he-zhu/aaron-marketing-skills/email-creative-builderWrote 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/aaron-he-zhu/aaron-marketing-skills/email-creative-builder)<a href="https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/email-creative-builder"><img src="https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/email-creative-builder/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/aaron-he-zhu/aaron-marketing-skills/email-creative-builder"><img src="https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/email-creative-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00149 | $0.02849 |
| Opus 5.5 | $0.00060 | $0.01140 |
| Sonnet 5.5 | $0.00030 | $0.00570 |
| Haiku 4.5 | $0.00015 | $0.00285 |
Grade A, and why
email-creative-builder 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Creative Builder
Writes and iterates a single email creative — subject-line variants + preheader, body copy, one clear CTA, and a plain-text alternate — each message-matched to the destination landing page and traced to approved claim wording. This is the build skill that produces the SEND E/D unit (the email analog of paid's ad-creative-builder). It does not score the email, run the D1 veto, or compute the EQS — that is email-quality-auditor — and it does not design the multi-step flow (email-sequence-designer) or the test (send-experiment-designer).
Scope guard: this skill builds the creative unit + message-match + claim flags only. It drafts subject-line variants for the creative but does not pre-score or rank them (spam-trigger flags, length/truncation, emoji-count, inbox-preview render) — that is subject-line-lab. It scores no SEND dimension, runs no veto, and does not compute the profile-weighted EQS — email-quality-auditor owns all four vetoes (S1/S2/N1/D1) and the EQS rollup.
Quick Start
Write 5 subject lines + preheader + body + CTA for [offer], destination [URL], promo mode
Draft a cold-outbound email to [persona] for [offer]; personalize on [signal]; destination [URL]
Iterate these losing subject lines: [paste]. Keep the winners, replace the rest, hold message-match to [URL].
Skill Contract
Expected output: one content-complete email creative — 3-5 subject-line variants, a preheader, structured body copy, a single primary CTA, and a plain-text alternate — with a creative_ref / version / hash, a per-claim message-match note to the destination URL and any [needs source] flags, plus the standard handoff summary for memory/email/email-creative-builder/. Content-complete is not authorization to create or send through an ESP.
- Reads: the offer/topic, destination, email mode, audience/lifecycle stage, existing copy,
memory/projections/narrative.json,memory/projections/claims.json, and the live consent/suppression state required by the selected flow. - Writes: a user-facing email creative and, with permission, a WARM artifact; unresolved claims become authorized proposal events, never direct ledger edits.
- Done when: subject/preheader fit declared render limits, the body has one primary CTA, plain text exists, claims/disclosures are accepted and context-valid or visibly blocked, destination message-match holds, the Narrative/claims dependency tuple is present, and the exact subject/preheader/body/CTA/plain-text set is frozen under a versioned creative hash.
- Primary next skill: send-experiment-designer — design the A/B / send-time test across the subject variants; or email-quality-auditor to score the unit and run the D1 claim veto.
What ships with it
2 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.
- 1mo ago Changed · +2 lines b011527e8b09
- 1mo ago First seen · 100 lines · 149 tokens per session scan A e4299be61801
email-creative-builder is a skill published in the GitHub repository aaron-he-zhu/aaron-marketing-skills (3,024 stars, last pushed today), licensed Apache-2.0. It adds 149 tokens to every session and 2,849 once invoked, about $0.0006 per session on Opus 5.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-08-30.
Other skills, from other repositories
geo-visibility-check
One-shot GEO audit: does your brand appear in Claude, ChatGPT, and Gemini answers for the buyer questions that matter? Runs a prompt panel through the engines with citation tracing and reports per-prompt verdicts, who wins instead, and which sources the answers come from.
geo-optimizer
Audit and fix a website for AI search visibility (Generative Engine Optimization). Use when asked to check whether a site or page can be found and cited by ChatGPT Search, Perplexity, Claude or Google AI Overviews, to score it 0-100 with geo audit, or to fix robots.txt AI crawler rules, llms.txt, JSON-LD schema, meta…
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
schema-generator
Generate JSON-LD schema markup for pages and content types with an implementation checklist. Use when users ask for schema, structured data, rich snippets, or markup.