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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill email-template-generator35
Quality
3%
Does it follow best practices?
Impact
93%
0.97xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/email-template-generator/SKILL.mdDiscovery
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 provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and boilerplate category information add no value for Claude's skill selection process.
Suggestions
Add specific capabilities: describe what the skill actually does (e.g., 'Creates professional email templates for sales outreach, follow-ups, meeting requests, and customer service responses')
Add a proper 'Use when...' clause with natural trigger scenarios (e.g., 'Use when the user needs to draft business emails, create email templates, write professional correspondence, or asks for help with email formatting')
Include natural keyword variations users would say: 'email', 'draft', 'compose', 'business email', 'professional email', 'email format', 'correspondence'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Email Template Generator') without describing any concrete actions. There are no specific capabilities listed like 'create templates', 'customize formatting', or 'generate subject lines'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is not a proper 'Use when...' clause and only repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('email template generator' listed twice) and overly specific. Missing natural variations users would say like 'email templates', 'write an email', 'draft email', 'business email', or 'email format'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'email template' is somewhat specific, the lack of detail about what kind of templates or use cases could cause overlap with general email writing skills or other template generators. | 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 a placeholder template with no actual content. It describes capabilities abstractly without providing any concrete email templates, code examples, or actionable instructions. The entire content could be replaced with a single executable example and would be more useful.
Suggestions
Add 2-3 concrete email template examples with actual template code (e.g., HTML email templates, plain text templates with variable placeholders)
Include executable code showing how to generate/populate templates (e.g., Python string formatting, Jinja2 templates, or similar)
Define a clear workflow: 1) Choose template type, 2) Customize variables, 3) Generate output, 4) Validate formatting
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need and add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, templates, or specific examples are provided. The skill describes what it does abstractly ('generates production-ready code') but never actually shows how to generate an email template or provides any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There's no sequence, no validation, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples file, no template library, and no structured navigation to deeper 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 | |
- 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.