The body is lean and assumes Claude's competence, with no padding about what email/Liquid/MCP are; every section earns its place with minimal, purposeful prose and code.

Provides a copy-paste-ready create payload, exact tool names, precise attributes (clicktracking="off", data-ph-no-track), and concrete Liquid snippets — fully executable guidance.

The create and read-modify-write-edit flows are explicitly numbered with validation checkpoints (show-template preview, fetch fresh as source of truth) and a recovery loop for rejected/malformed tool calls.

Two clearly-signaled one-level-deep references (unlayer-design-json.md, design-guidelines.md) — both real files in references/ — with their purpose stated, keeping the inline body an overview.

Lists multiple concrete actions — 'Author, save, and edit email templates', 'compose email design JSON with Liquid personalization', and 'round-trip-edit templates over MCP' — matching the comprehensive multi-action anchor.

Explicitly answers both what (author/save/edit/compose design JSON) and when via a clear 'Use when...' trigger, satisfying the both-answered anchor.

The 'Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or campaigns' clause gives good coverage of natural phrases a user would actually say.

Scoped to 'PostHog workflows library' email templates 'over MCP' for broadcasts/campaigns — a distinct niche unlikely to trigger for unrelated skills.