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-auditor. 邮件个性化/合并标签/条件内容块/兜底默认值
aaron-he-zhu · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aaron-he-zhu/aaron-marketing-skills --skill dynamic-content-personalizer技能说明
name: dynamic-content-personalizer slug: aaron-dynamic-content-personalizer displayName: "Dynamic Content Personalizer · 邮件个性化" summary: "邮件个性化/合并标签/条件内容块/兜底默认值" description: '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-auditor. 邮件个性化/合并标签/条件内容块/兜底默认值' version: "20.1.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Use when adding personalization to an already-written email creative: mapping merge/personalization tags to real export columns with a safe fallback for every tag, defining conditional-content blocks that vary by segment, auditing that no empty merge field or broken conditional renders ("Hi ,"), and guarding which PII fields are allowed to appear in the rendered body at all. Covers B2C lifecycle, B2B cold-outbound personalization, and newsletter dynamic modules." argument-hint: "<email creative + segment map or export columns> [mode: promo|cold|newsletter]" metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "email", "phase": "engage", "geo-relevance": "low", "hermes": {"tags": ["marketing", "email", "engage"], "category": "email"}, "openclaw": {"emoji": "✉️", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
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), does not write the subject/body/CTA (email-creative-builder), and does not score, roll up the EQS, or run the S1/S2/N1/D1 vetoes (email-quality-auditor 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: champions get the loyalty offer, at-risk get the win-back offer, everyone else the base offer. Segment map attached.
Audit this template for fallback safety and PII exposure before we send. [paste template with {{merge_tags}}]
Skill Contract
Expected output: a personalization spec in four parts — (1) a merge-tag map listing every tag, the export column it binds to, and its fallback value (with the fallback shown as it will render); (2) conditional-block rules — per-segment if/elseif/else variations, each tied to a named segment from the segment map, with a mandatory catch-all else; (3) a fallback-safety audit confirming no tag can render empty (no "Hi ,", no orphaned punctuation, no dead conditional) and each block has a default branch; and (4) a PII guard naming which fields are allowed to render and which are blocked — informing the SEND E (Engagement/personalization) dimension, plus the standard handoff summary.
- Reads: the email creative to personalize (from email-creative-builder); the segment map and the available export columns + fill-rates (from list-segment-builder); the program mode (promo / cold / newsletter); and, when a personalized line makes a promotional claim, approved wording from
memory/claims/claims-ledger.md(the offer-claims-registry). - Writes: a user-facing personalization spec and a reusable handoff summary to
memory/email/dynamic-content-personalizer/. - Promotes: the merge-tag/fallback contract, the conditional-block map, any low-fill-rate field, and any PII-exposure risk to
memory/hot-cache.mdandmemory/open-loops.md; propose durable personalization decisions as pending-decision items (never writedecisions.mddirectly). - Done when: every merge tag binds to a real export column and carries a rendered fallback; every conditional block references a named segment and has a catch-all
else; the fallback-safety audit shows no empty-field or dead-conditional render; the PII guard states which fields may appear and which are blocked; and the SEND E relevance is noted. - Primary next skill: email-render-builder to assemble the personalized template into a rendered, cross-client email; or email-quality-auditor to score the finished unit and run the vetoes.
Handoff Summary
Emit the standard shape from skill-contract.md §Handoff Summary Format.
Data Sources
Use ~~email platform only as an own-data manual export — the ESP subscriber CSV tells you which personalization columns actually exist and their fill-rate (what fraction of rows have a non-empty value), which is the single fact that decides whe