email-render-builder

Use when the user asks to "build the email HTML", "make this email responsive", "fix dark-mode rendering", or "QA the email across clients"; produces the coded HTML build — a responsive table layout, dark-mode + accessibility pass, a client-render matrix, image-block fallbacks, and a plain-text parity check. Not for writing the copy — use email-creative-builder; not for scoring the email or computing EQS — use email-quality-auditor. 邮件HTML/响应式邮件/暗色模式渲染

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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-structured, actionable build-and-QA workflow with explicit checkpoints, decision gates, and one-level-deep references. The main weakness is mild boundary-statement redundancy across several sections.

Suggestions

Consolidate the 'not for copy / not for scoring / not for EQS' boundary into the Scope guard line and drop its repetition in the intro, Done-when, and Next Best Skill sections.

Pull one concrete bulletproof-button snippet or dark-mode color-pair example inline so the build step is actionable without opening a reference file.

The trailing '邮件HTML/响应式邮件/暗色模式渲染' in the description duplicates the trigger phrasing already given in English; consider removing to tighten the frontmatter.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and task-oriented, but the 'not for copy / not for scoring' boundary is restated in the intro, the Scope guard, Done-when, and Next Best Skill sections — minor redundancy that could be trimmed; not a 5 due to this repetition.	4 / 5
Actionability	Provides a concrete resend render-test command, specific quality-bar checklist, and pointers to reference files with their contents; mostly executable, but the bulk of code/markup lives in referenced files rather than inline.	4 / 5
Workflow Clarity	An 11-step sequenced process with explicit validation checkpoints ('Quality bar before handoff', 'Done when'), Decision Gates distinguishing stop-and-ask vs continue-silently, and feedback loops that route defects back to email-creative-builder.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview; details are split into one-level-deep, well-signaled reference files (email-render-specs.md, client-render-matrix.md) that exist in the bundle and are described in 'Reference Materials'.	5 / 5
	Total	18 / 20 Passed

Description

100%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 exemplary: concrete build actions, natural trigger phrases, explicit what/when guidance, and clear boundary statements against sibling skills. Minimal padding beyond a trailing localized summary.

Dimension	Reasoning	Score
Specificity	Quotes 'a responsive table layout, dark-mode + accessibility pass, a client-render matrix, image-block fallbacks, and a plain-text parity check' — multiple concrete build actions with comprehensive coverage of the render scope.	5 / 5
Completeness	Explicitly answers both what ('produces the coded HTML build …') and when ('Use when the user asks to …') with concrete trigger phrases; it is not a 4 because both halves are explicit and specific.	5 / 5
Trigger Term Quality	Uses natural trigger phrases users would say — '"build the email HTML", "make this email responsive", "fix dark-mode rendering", or "QA the email across clients"' — with several synonym variations.	5 / 5
Distinctiveness Conflict Risk	Clear email-render niche with explicit boundaries — 'Not for writing the copy — use email-creative-builder; not for scoring the email or computing EQS — use email-quality-auditor' — minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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: 21 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: email/engage/email-render-builder/SKILL.md
Commit: 888dd38

Reviewed: 3 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.