email-template-generator
Email Template Generator - Auto-activating skill for Business Automation. Triggers on: email template generator, email template generator Part of the Business Automation skill category.
35
3%
Does it follow best practices?
Impact
93%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/email-template-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that restates the skill name without providing any meaningful detail about capabilities, actions, or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from any other email-related skill in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates professional email templates for marketing campaigns, follow-ups, onboarding sequences, and transactional notifications. Supports customizable subject lines, body content, and call-to-action sections.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create an email template, draft a marketing email, build a newsletter layout, or generate automated email content.'
Remove the duplicated trigger term and expand with natural variations users would actually say, such as 'email draft', 'email copy', 'newsletter template', 'outreach email', 'email automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Email Template Generator') but provides no concrete actions. It does not describe what the skill actually does—no mention of creating, formatting, customizing, or any specific operations on email templates. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'email template generator' repeated twice. It misses natural variations users would say like 'create email template', 'email draft', 'marketing email', 'newsletter template', 'email layout', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'email template generator' is somewhat specific to a niche (email templates), which provides some distinctiveness. However, the lack of detail about what specifically it does versus other email-related or template-related skills creates potential overlap. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It describes what it would do in abstract terms but provides no actual email templates, code examples, workflows, or concrete guidance. It fails on every dimension because it contains only meta-description and self-referential trigger phrases rather than teaching Claude how to generate email templates.
Suggestions
Add concrete, executable email template examples (e.g., HTML templates for common business scenarios like welcome emails, invoices, password resets) with copy-paste ready code.
Define a clear workflow for generating email templates: gather requirements → select template type → customize content → validate HTML → output final template.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual instructional content—template structures, variable substitution patterns, and best practices for email HTML compatibility.
Add references to supplementary files for advanced topics (e.g., 'See TEMPLATES.md for full template library' or 'See STYLING.md for email CSS compatibility guide').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or actionable content. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no templates, no examples of actual email templates. The 'capabilities' section lists abstract promises ('provides step-by-step guidance') without delivering any of them. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no steps whatsoever. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. There is nothing to progressively disclose because there is no substantive content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.