email-parser
Email Parser - Auto-activating skill for Business Automation. Triggers on: email parser, email parser Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
98%
1.05xAverage 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-parser/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 weak, essentially serving as a label rather than a functional description. It provides no concrete actions, no meaningful trigger terms beyond the skill name repeated, and no guidance on when Claude should select this skill. The 'Business Automation' category mention adds minimal value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Extracts sender, recipient, subject, body, and attachments from raw email content. Parses email headers, MIME types, and embedded metadata.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to parse email messages, extract email fields, process .eml files, analyze email headers, or work with raw email content.'
Include natural keyword variations users might say, such as 'parse email', 'email extraction', 'email headers', 'MIME', '.eml', 'mail content', 'inbox data' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Email Parser' but never describes what concrete actions it performs. There are no specific capabilities listed like 'extract sender addresses', 'parse attachments', or 'categorize emails'. It's essentially just a label. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant restatement of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause with real scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'email parser' repeated twice. It misses natural variations users would say like 'parse email', 'extract email data', 'read email headers', 'email content', '.eml files', 'inbox', 'mail', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'email parser' is somewhat specific to a niche (parsing emails), which provides some distinctiveness. However, the lack of detail about what kind of parsing or what outputs it produces means it could overlap with other email-related skills. | 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 hollow placeholder that contains no actual instructional content. It describes what it would do in abstract terms but provides zero actionable guidance on email parsing—no code, no libraries, no formats, no workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for email parsing (e.g., using Python's `email` module or `mailparser` library to extract sender, subject, body, and attachments).
Define a clear workflow with steps: receive/read email → parse headers → extract body/attachments → validate output, including validation checkpoints.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace with actual instructional content showing input email formats and expected parsed output.
If advanced topics exist (e.g., MIME handling, attachment processing, calendar invites), reference them via separate files with clear navigation links.
| 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 examples of email parsing, no library recommendations, no data formats. The 'Example Triggers' section just lists phrases to activate the skill, not actual usage examples. | 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 vague descriptions with no references to detailed files, no structured navigation, and no separation of concerns. 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
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.