email-template-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill email-template-generatorEmail Template Generator - Auto-activating skill for Business Automation. Triggers on: email template generator, email template generator Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It only states the skill name and category without explaining capabilities, use cases, or providing meaningful trigger terms. Claude would struggle to know when to select this skill over others.
Suggestions
Add specific actions the skill performs, e.g., 'Creates professional email templates for marketing campaigns, newsletters, transactional emails, and customer outreach. Supports customizable sections, merge fields, and responsive formatting.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to create email templates, draft marketing emails, design newsletters, or needs help with email copy, subject lines, or email campaigns.'
Add file types or output formats if applicable, e.g., 'Outputs HTML email templates compatible with major email platforms like Mailchimp, SendGrid, or Outlook.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Email Template Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, formatting, customizing, or any specific email template operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'email template generator' repeated twice, which is the skill name itself. Missing natural variations users would say like 'create email', 'draft template', 'marketing email', 'newsletter', 'email copy', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'email template' is somewhat specific to a domain, the lack of detail about what kind of templates (marketing, transactional, newsletters) or what operations are supported means it could overlap with general writing or document skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no substantive value. It consists entirely of generic meta-descriptions about what the skill supposedly does without providing any actual guidance, code, templates, or actionable instructions for email template generation. The content fails every dimension by describing rather than instructing.
Suggestions
Add concrete, executable code examples showing how to generate email templates (e.g., Python functions with Jinja2 or string formatting)
Include 2-3 actual email template examples with placeholders and expected outputs
Define a clear workflow: 1) Identify template type, 2) Gather variables, 3) Generate template, 4) Validate output format
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 Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | Contains zero concrete guidance, no code examples, no specific commands, and no actual instructions for generating email templates. The entire content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but includes no actual steps. There are no processes, sequences, or validation checkpoints of any kind. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed materials, no examples, and no navigation to additional resources despite claiming capabilities. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.