email-marketing
When the user needs to design, write, or optimize email sequences -- including welcome series, nurture campaigns, re-engagement flows, onboarding emails, or newsletter strategy.
79
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/email-marketing/SKILL.mdQuality
Discovery
72%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 effectively identifies its niche in email marketing sequences with good trigger term coverage and low conflict risk. However, it lacks specificity in describing concrete actions/outputs and blends the 'what' and 'when' together rather than clearly articulating both. Adding explicit capability statements would strengthen it.
Suggestions
Add concrete capability statements before the trigger clause, e.g., 'Creates email copy, designs sequence timing and cadence, writes subject lines, defines audience segments, and maps conversion funnels for email campaigns.'
Restructure to separate 'what' from 'when': lead with specific capabilities, then add an explicit 'Use when...' clause for clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (email sequences) and lists several types (welcome series, nurture campaigns, re-engagement flows, onboarding emails, newsletter strategy), but the core actions are somewhat generic ('design, write, or optimize') rather than listing multiple concrete, distinct capabilities. | 2 / 3 |
Completeness | The description starts with 'When the user needs to...' which addresses the 'when' aspect, but the 'what does this do' portion is weak — it only says 'design, write, or optimize' without clearly stating the skill's concrete outputs or capabilities. The 'when' and 'what' are blended rather than explicitly separated, and there's no distinct 'Use when...' clause. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would actually say: 'email sequences', 'welcome series', 'nurture campaigns', 're-engagement flows', 'onboarding emails', 'newsletter strategy'. These cover a good range of common variations a user might mention. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around email sequences and campaigns specifically, with distinct trigger terms like 'welcome series', 'nurture campaigns', 're-engagement flows' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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, highly actionable skill that provides Claude with specific frameworks, timings, copy structures, and benchmarks to produce complete email sequences. Its main weakness is moderate verbosity — some best practices and explanations are things Claude already knows, and the document could benefit from splitting detailed reference material (like sequence arc templates and best practices) into supplementary files. The workflow is clear and well-sequenced for a content creation task.
Suggestions
Trim best practices that Claude already knows (e.g., 'short paragraphs, active voice,' 'mobile-first writing' basics) to reduce token usage while keeping the non-obvious advice like reply-to deliverability impact and list hygiene thresholds.
Consider extracting the detailed sequence arc templates (welcome 5-7 emails, nurture 6-8 emails, etc.) into a separate SEQUENCES.md reference file, keeping only a summary in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some content Claude would already know (e.g., explaining what welcome/nurture/re-engagement sequences are, basic email formatting advice like 'short paragraphs' and 'active voice'). The best practices section contains some commonly known advice that could be trimmed. However, the specific frameworks, sequence arcs, and benchmarks add genuine value. | 2 / 3 |
Actionability | The skill provides highly specific, actionable guidance: exact email counts and timings for each sequence type, concrete copy structure (hook/context/value/CTA), subject line character limits, word count ranges per email type, specific benchmarks (25-35% open rate), and detailed examples showing what good output looks like. Claude can follow this to produce complete email sequences. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced from goal definition through measurement, with each step building logically on the previous one. The sequence arc mappings provide explicit progression patterns for each email type. The output format section serves as a validation checklist ensuring completeness. For a non-destructive content creation task, this level of workflow clarity is excellent. | 3 / 3 |
Progressive Disclosure | The skill is a single long document (~600+ words of body content) with no references to supplementary files. The frameworks/best practices section and the detailed sequence arcs could potentially be split into reference files. However, the Related Skills section does provide clear cross-references to adjacent skills. The content is well-organized with clear headers but is borderline monolithic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- 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.