email-parser
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill email-parserEmail Parser - Auto-activating skill for Business Automation. Triggers on: email parser, email parser Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially providing only a skill name and category without any substantive information about capabilities or usage triggers. It fails to help Claude distinguish when to select this skill, as it lacks concrete actions, natural trigger terms, and explicit guidance on when to activate.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Extracts sender, recipient, subject, body, and attachments from email files. Parses email headers and metadata.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions parsing emails, extracting email content, .eml files, email headers, or needs to process email data.'
Remove the duplicate 'email parser' trigger and expand with variations users would naturally say: 'parse email', 'read email file', 'extract from email', 'email metadata'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Email Parser') without describing any concrete actions. There are no specific capabilities listed like 'extract sender information', 'parse attachments', or 'identify email headers'. | 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' line is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'email parser' repeated twice, which is redundant and misses natural variations users would say like 'parse email', 'extract email data', 'read email', '.eml files', or 'email content'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Email Parser' is somewhat specific to email domain, the lack of detail about what parsing means could cause overlap with other email-related skills or general text processing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual instructional content. It describes what an email parser skill would theoretically do but provides zero concrete guidance on parsing emails - no code examples, no library recommendations, no parsing patterns, no handling of different email formats (MIME, headers, attachments). The entire content could be replaced with actual executable Python code using libraries like email or mailparser.
Suggestions
Add concrete, executable code examples for parsing emails (e.g., using Python's email module to extract headers, body, and attachments)
Include specific patterns for common email parsing tasks: extracting sender/recipient, parsing MIME multipart messages, handling attachments, extracting structured data from email bodies
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actual technical content
Add validation steps for parsed email data and error handling for malformed emails
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague platitudes that waste tokens without teaching Claude anything specific. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual email parsing. The content describes what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, no structure beyond generic headings, and nothing to progressively disclose. | 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.