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 extremely thin and auto-generated, consisting only of a skill name, a duplicated trigger phrase, and a category label. It provides no concrete actions, no natural trigger terms beyond the skill name, and no explicit guidance on when Claude should use it. It would be nearly indistinguishable from other email or template skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates professional email templates for marketing campaigns, follow-ups, onboarding sequences, and transactional notifications.'
Include a 'Use when...' clause with natural trigger terms like 'create email template', 'draft email', 'email layout', 'newsletter', 'email copy', 'outreach email'.
Remove the duplicated trigger term and replace with diverse, natural keyword variations users would actually say when needing this skill.
| 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 capabilities. | 1 / 3 |
Completeness | The 'what' is essentially absent beyond the skill name, and the 'when' is only a redundant trigger phrase with no explicit guidance on when Claude should select this skill. There is no 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'email template generator' repeated twice. It misses natural variations users would say like 'email template', 'create email', 'draft email', 'email layout', 'newsletter template', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'email template generator' is somewhat specific to a niche, which reduces conflict with unrelated skills. However, the lack of detail means it could overlap with other email-related or template-related skills without clear differentiation. | 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 an empty shell with no actual content. It consists entirely of self-referential meta-descriptions that describe what the skill would do without providing any actionable instructions, code examples, email templates, or concrete guidance. It fails on every dimension of the rubric.
Suggestions
Add actual email template examples with concrete code (e.g., HTML email templates, Python code for generating templates with Jinja2, or similar executable examples).
Define a clear workflow for creating email templates: e.g., 1) Choose template type, 2) Define variables/placeholders, 3) Generate HTML, 4) Validate output.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content like template patterns, variable substitution examples, and best practices for email HTML compatibility.
Include at least one complete, copy-paste-ready example showing input (template requirements) and output (generated email template).
| 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. | 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. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured content hierarchy, and no meaningful organization. The sections are just repetitive meta-descriptions with no substantive content to organize. | 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
3e83543
- 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.