CtrlK
BlogDocsLog inGet started
Tessl Logo

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

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A well-structured, highly actionable personalization spec skill: concrete syntax, a validated 9-step workflow with a safety audit and decision gate, and clean one-level reference navigation. Its main weakness is redundancy — the scope guard and next-skill routing are each restated multiple times — which keeps conciseness at 2.

Suggestions

State the Scope guard once (keep it in the intro) and remove the duplicate after the Decision Gate; the exclusions are already reinforced by the Reference Materials and Next Best Skill links.

Collapse the three overlapping next-skill mentions (Skill Contract "Primary next skill", Reference Materials, Next Best Skill) into a single routing block — the Next Best Skill section largely restates routing already covered.

Trim the trailing bilingual summary string in the description ("邮件个性化/合并标签/条件内容块/兜底默认值") since it duplicates the trigger terms already named in English.

DimensionReasoningScore

Conciseness

The body is domain-dense with no basic-concept padding (it never explains what a merge tag is), but it could be tightened: the Scope guard is stated twice (intro and after the Decision Gate) and next-skill routing is repeated across Skill Contract's "Primary next skill", Reference Materials, and the Next Best Skill section. That redundancy fits the score-2 "mostly efficient but could be tightened" anchor rather than the lean score-3 bar.

2 / 3

Actionability

Guidance is concrete and copy-paste-ready: exact merge-tag syntax (`{{first_name | "there"}}` → "Hi there,"), an explicit if/elseif/else conditional structure keyed to named segments (champions → loyalty offer), specific failure modes to catch ("Hi ,"), and exact save paths — fully actionable instruction-only guidance, not vague description.

3 / 3

Workflow Clarity

A clear 9-step numbered sequence is backed by an explicit fallback-safety audit as a validation checkpoint (step 6), a Decision Gate table for stop-and-ask vs continue-silently feedback, and a "Done when" checklist — matching the score-3 anchor of explicit validation steps, feedback loops, and checklists.

3 / 3

Progressive Disclosure

The body is an overview with a dedicated Reference Materials section pointing one-level-deep to clearly signaled external files (skill-contract.md for handoff/save/termination formats, send-benchmark.md for the SEND framework, CONNECTORS.md, SECURITY.md); no nested 2+ level reference chains are present. No bundle files exist under the skill's own references/scripts/assets, so scoring reflects the signaled outward references.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, trigger-rich description that concretely names its four outputs, opens with natural "Use when…" phrasings, and sharply separates itself from three neighboring skills via explicit exclusions. It is somewhat verbose and carries a redundant trailing bilingual summary, but no dimension is weakened enough to drop below 3.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "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" — matching the score-3 anchor of several specific actions rather than a single named action (score 2).

3 / 3

Completeness

Explicitly answers both halves: an explicit "Use when…" trigger clause for when, and a concrete "produces…" statement of outputs for what, satisfying the score-3 anchor for both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Quotes natural user phrasings a person would actually say — "personalize the email", "add merge tags / dynamic content", "set up conditional blocks per segment", "make first-name and product-recommendation fields fall back safely" — giving good coverage of likely trigger terms, not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Three explicit "Not for…" exclusions name list-segment-builder, email-creative-builder, and email-quality-auditor, carving a clear niche unlikely to fire for the wrong skill — the score-3 distinct-trigger case rather than a generic overlap (score 2).

3 / 3

Total

12

/

12

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.

Validation13 / 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
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.