CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 邮件个性化/合并标签/条件内容块/兜底默认值

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, actionable instruction skill: numbered steps with a genuine validation checkpoint (the fallback-safety audit), explicit stop/continue gates, and concrete fallback syntax examples. Its main costs are repeated scope-guard/link material that inflates token usage without adding information, and a missing worked example of conditional-block syntax; progressive disclosure is good but rests entirely on references that live outside this bundle and cannot be verified from it.

Suggestions

State the scope guard once (e.g. in the opening section) and refer back to it, removing the near-verbatim repeats after the Skill Contract and Decision Gate; the email-quality-auditor and email-render-builder links appear five-plus times and can be consolidated into Reference Materials and Next Best Skill.

Add one worked conditional-block example showing actual if/elseif/else syntax with its worst-case else render, mirroring the quality of the existing merge-tag fallback example.

Make the audit feedback loop explicit: after the fallback-safety audit, instruct 'if any tag renders empty or any block has no valid default, fix the fallback/conditional and re-run the audit before done'.

DimensionReasoningScore

Conciseness

The body is dense and instruction-first with no padding on concepts Claude already knows, but structural repetition is noticeable rather than minor: the scope guard appears three times (intro, dedicated paragraph, and again after the Decision Gate) and the email-quality-auditor / email-render-builder links repeat across five or more locations. This fits 'mostly efficient but could be tightened' better than the 4 anchor's 'minor instances'.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: a rendered fallback example ("{{first_name | \"there\"}} → 'Hi there,' not 'Hi ,'"), segment→offer mapping patterns (champions → loyalty, at-risk → win-back), and a four-part output contract with a done-when checklist. It falls short of 5 because the conditional-block deliverable is never shown with actual if/elseif/else syntax rendered, leaving the skill's second output as described rather than exemplified.

4 / 5

Workflow Clarity

Nine ordered steps are clearly sequenced with the fallback-safety audit as an explicit, central validation checkpoint ('walk the whole template as if every personalized field were empty'), plus a stop/continue Decision Gate table and a done-when checklist. It misses 5 only because the error-recovery loop (audit finds an empty render → fix the fallback → re-audit) is implied by 'No fallback = fail' rather than stated as an explicit feedback loop.

4 / 5

Progressive Disclosure

Sections are well organized (Quick Start, Skill Contract, Data Sources, Instructions, Decision Gate, Save Results, Reference Materials, Next Best Skill) and every external reference is one level deep with a stated purpose. It does not reach 5 because the bundle contains no referenced files at all — all paths resolve outside the bundle (e.g. ../../../references/skill-contract.md, ../../../CONNECTORS.md) and cannot be verified, and key output formats (handoff summary, save template) are deferred to that absent external file.

4 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong example: it pairs a concrete, comprehensive statement of the four deliverables with explicit quoted user-voice trigger phrases, and closes with named-skill negative boundaries that sharply reduce mis-triggering. The only weakness is modest synonym coverage in the trigger terms (missing casual phrasings like 'custom fields' or 'use the subscriber's name').

DimensionReasoningScore

Specificity

The description lists four concrete deliverables — "a merge-tag map with per-tag fallbacks, conditional-block rules with per-segment variations, a fallback-safety audit, and a PII guard" — which is comprehensive, specific coverage of what the skill produces. It does not fall to 4 because the action list has no identifiable coverage gaps.

5 / 5

Completeness

Both halves are explicit: "Use when the user asks to" followed by concrete trigger phrases, and a concrete what (the four-part output). This matches the anchor-5 pattern of 'clearly and explicitly answers both what AND when with concrete trigger phrases'; score 4 would require the when to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Four quoted natural trigger phrases ("personalize the email", "add merge tags / dynamic content", "set up conditional blocks per segment", "make first-name and product-recommendation fields fall back safely") give strong, user-voice keyword coverage with synonyms. A few natural terms are still missing (e.g. "custom fields", "use the subscriber's name", "personalization tokens"), which keeps it below the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

Explicit negative boundaries name the owning skill for each adjacent task ("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"), giving a clear niche with minimal conflict risk. This exceeds the 4 anchor, which only requires minor overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 30 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/engage/dynamic-content-personalizer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.