dynamic-content-personalizer

Generates merge-tag maps, conditional content blocks, and fallback-safety audits for email personalization.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/qaz26688442/bo-car --skill dynamic-content-personalizer-qaz26688442
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dynamic-content-personalizer
Source: https://github.com/qaz26688442/bo-car/tree/main/.agents/skills/dynamic-content-personalizer
Command: npx skills add https://github.com/qaz26688442/bo-car --skill dynamic-content-personalizer-qaz26688442

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personalized emails break when merge fields are empty or conditional blocks lack a default branch, producing renders like "Hi ," or dead content for unbucketed subscribers. This Skill wires a safe personalization layer onto an already-written email creative so every tag has a fallback and every conditional has a catch-all. ## Core Features & Use Cases - Merge-Tag Map with Fallbacks: Binds every personalization token to a real export column and defines a rendered fallback value for empty fields. - Conditional-Block Rules: Defines per-segment if/elseif/else content variations keyed to named segments, always ending in a catch-all else branch. - Fallback-Safety Audit and PII Guard: Walks the template as if every field were empty to catch broken renders, and blocks sensitive PII (full names, phone numbers, order IDs) from appearing in body copy. - Use Case: Given a promo email and a segment map with champions, at-risk, and new subscribers, produce a spec where champions see a loyalty offer, at-risk see a win-back offer, everyone else falls to the base offer, and first_name falls back to "there" when empty. ## Quick Start Add merge tags with fallbacks to this email creative using export columns first_name, city, and last_product in promo mode.

Frequently Asked Questions about dynamic-content-personalizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add merge tags with fallbacks to an email?▼

Bind each personalization token to a real export column and assign a fallback that reads naturally when the field is empty, such as {{first_name | "there"}} rendering as "Hi there,". A tag with no fallback is treated as a failure because it produces broken renders like "Hi ,".

How do I set up conditional content blocks per email segment?▼

Write if/elseif/else rules keyed to named segments from your segment map, for example champions get the loyalty offer and at-risk get the win-back offer. Every block must end in a catch-all else so subscribers matching no branch still receive valid content.

What is a fallback-safety audit for email templates?▼

It walks the entire template as if every personalized field were empty and every subscriber fell to the else branch, confirming no orphaned punctuation, empty bullets, or dead conditional blocks render. Each tag and block is listed with its worst-case render.

Which PII fields should not appear in personalized email copy?▼

Full names, email addresses, phone numbers, precise addresses, order IDs, and special-category data should be blocked from body copy and subject lines. First name, city, and product category are typically acceptable, and sensitive fields should be replaced with coarser substitutes.

When should I not use this personalization skill?▼

Do not use it to build segments, write the base subject or body copy, or score email quality; those belong to list-segment-builder, email-creative-builder, and email-quality-auditor respectively. It only wires personalization onto existing copy for existing segments.