Name: designing-email-templates
Rating: 73.6 (1 reviews)
Author: PostHog

designing-email-templates

Author, save, and edit email templates in the PostHog workflows library — compose email design JSON with Liquid personalization and create and round-trip-edit templates over MCP. Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or campaigns.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

92%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.

An lean, highly actionable skill body that sequences its workflows with real validation checkpoints and teaches only PostHog-specific behavior. Its one real weakness is progressive disclosure: the two referenced files it points to are missing from the bundle, breaking navigation.

Suggestions

Ship the missing references/unlayer-design-json.md and references/design-guidelines.md files in the bundle so the links the body already signals resolve, rather than leaving the design JSON schema and design guidance unreachable.

If those files cannot be bundled, inline the minimal design-JSON schema snippet and the core design-guidance rules directly in SKILL.md so the skill is self-contained.

Confirm the exact reference paths in the body match the bundle filenames (including directory) to prevent the broken-link gap from recurring.

Dimension	Reasoning	Score
Conciseness	The body is dense and PostHog-specific (MCP tool names, click-tracking markers, presigned upload flow) with no padding explaining general concepts Claude already knows; every section teaches a renderer/tool-specific behavior that earns its tokens.	5 / 5
Actionability	Concrete JSON payloads, an executable curl upload command, and specific numbered tool calls cover the common cases (create, image upload, patch, edit); the only abbreviation is the deeply-nested design body, which is unavoidable.	5 / 5
Workflow Clarity	Create, read-modify-write, patch, and draft→test→publish workflows are clearly sequenced with explicit checkpoints (show-preview after save, fetch-fresh before update, malformed-JSON fix-and-resend loop, use_draft test before publish).	5 / 5
Progressive Disclosure	The body is well-sectioned and clearly signals one-level-deep references to references/unlayer-design-json.md and references/design-guidelines.md, but those files are absent from the bundle, so the signaled navigation is broken and the design JSON schema is unreachable.	3 / 5
	Total	18 / 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.

A strong, third-person description that concretely states multiple capabilities and pairs them with an explicit, natural-language "Use when" trigger clause scoped to a distinct PostHog niche. The only minor gap is a lack of additional synonyms beyond the strong core trigger set.

Dimension	Reasoning	Score
Specificity	"Author, save, and edit email templates", "compose email design JSON with Liquid personalization", and "create and round-trip-edit templates over MCP" list multiple concrete, specific actions with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly answers what ("Author, save, and edit email templates... compose email design JSON...") and when ("Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or campaigns") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"design, build, update, or fix an email template for workflows, broadcasts, or campaigns" gives good natural keyword coverage users would actually say, but stops short of the exhaustive synonym list (e.g. alternate phrasings) that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	"PostHog workflows library" and the workflows/broadcasts/campaigns triggers carve out a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	14 / 16 Passed

Repository: PostHog/posthog
Path: products/workflows/skills/designing-email-templates/SKILL.md
Commit: 130f3a1

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.