Agent skill · Security

dynamic-content-personalizer

Use when the user asks to "personalize the email", "add merge tags / dynamic content", "set up conditional blocks per segment", or "make first-name and product-recommendation fields fall back safely"; produces a merge-tag map with per-tag fallbacks, conditional-block rules with per-segment variations, a fallback-safety audit, and a PII guard on what may render, informing the SEND E (Engagement/personalization) dimension. Not for building the segments — use list-segment-builder; not for writing the base copy — use email-creative-builder; not for scoring EQS or running vetoes — use email-quality

aaron-he-zhugithub.com/aaron-he-zhuGitHub ↗
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill dynamic-content-personalizer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: email/engage/dynamic-content-personalizer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Dynamic Content Personalizer Takes an already-written email creative plus the segment map (or the raw export columns) and specifies the **personalization layer**: a merge-tag map where every tag has a stated fallback, conditional-content blocks with per-segment variations, a fallback-safety audit that no empty field or dead conditional can render, and a PII guard on which fields are even allowed into the body. This is the SEND **E (Engagement/personalization)** lever. It does not build segments, write the base copy, or score the program. **Scope guard**: this skill wires personalization onto existing copy for existing segments only. It does **not** define WHO the segments are ([list-segment-builder](../../setup/list-segment-builder/SKILL.md)), does **not** write the subject/body/CTA ([email-creative-builder](../email-creative-builder/SKILL.md)), and does **not** score, roll up the EQS, or run the S1/S2/N1/D1 vetoes ([email-quality-auditor](../../deliver/email-quality-auditor/SKILL.md) owns those). ## Quick Start ``` Add merge tags with fallbacks to this email [paste creative]; export columns are first_name, city, last_product. Promo mode. ``` ``` Set up conditional blocks: champi

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Decision Gate
  7. Save Results
  8. Reference Materials
  9. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the dynamic-content-personalizer skill do?

Use when the user asks to "personalize the email", "add merge tags / dynamic content", "set up conditional blocks per segment", or "make first-name and product-recommendation fields fall back safely"; produces a merge-tag map with per-tag fallbacks, conditional-block rules with per-segment variations, a fallback-safety audit, and a PII guard on what may render, informing the SEND E (Engagement/personalization) dimension. Not for building the segments — use list-segment-builder; not for writing the base copy — use email-creative-builder; not for scoring EQS or running vetoes — use email-quality

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill dynamic-content-personalizer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going