Craft A/B test variants, optimize open rates, and structure drip campaigns for marketing emails. Trigger when a user explicitly requests a "marketing email," "email sequence," "marketing CTA," or "optimize subject lines." Do not use for standard or internal correspondence.
Install with Tessl CLI
npx tessl i github:davidkogit/public-skills --skill email-marketing94
Quality
92%
Does it follow best practices?
Impact
95%
1.72xAverage score across 3 eval scenarios
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It provides specific capabilities, natural trigger terms, explicit usage guidance with both inclusion and exclusion criteria, and clearly carves out its niche from general email skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Craft A/B test variants, optimize open rates, and structure drip campaigns.' These are distinct, actionable capabilities in the marketing email domain. | 3 / 3 |
Completeness | Clearly answers both what (A/B test variants, optimize open rates, structure drip campaigns) AND when with explicit 'Trigger when' clause listing specific phrases. Also includes helpful exclusion criteria ('Do not use for standard or internal correspondence'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'marketing email,' 'email sequence,' 'marketing CTA,' 'optimize subject lines.' These are terms users naturally use when requesting marketing email help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on marketing emails with explicit boundary ('Do not use for standard or internal correspondence') that distinguishes it from general email writing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides highly actionable guidance for email marketing copywriting. The three-phase workflow with explicit validation checkpoints is excellent, and the concrete examples (subject lines, HTML snippets, output template) make it immediately usable. Minor verbosity in explaining concepts Claude already understands prevents a perfect conciseness score.
Suggestions
Trim explanatory text like 'Opt for a personal name rather than a faceless company name to build trust' - Claude understands email marketing psychology; just state the rule.
Remove the definition of 'bulletproof buttons' and just provide the HTML snippet with a brief label.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what bulletproof buttons are, basic email marketing concepts Claude would know). The HTML snippet is appropriately included as it's specific implementation detail, but some surrounding context could be trimmed. | 2 / 3 |
Actionability | Highly actionable with concrete examples for subject lines, exact HTML code for CTA buttons, specific character counts (20-40 for subjects, 70 for preheaders), and a complete output template structure. Copy-paste ready guidance throughout. | 3 / 3 |
Workflow Clarity | Excellent three-phase workflow with explicit validation checkpoints after Phase 1 and Phase 3. Clear sequencing from context gathering → drafting → output with pause points for user approval before proceeding. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate reference to external file (DRIP_CAMPAIGNS.md) for advanced automation content. The main skill stays focused on core email drafting while pointing to specialized content for sequences. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.