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 thin and template-generated, providing almost no useful information beyond the skill name. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. It would be nearly impossible for Claude to make an informed decision about when to select this skill over others.
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 files (.eml, .msg), extract email fields, process inbox data, or analyze email headers.'
Remove the duplicate trigger term 'email parser' and expand with natural variations users would say, such as 'parse emails', 'extract email data', 'read email content', 'email fields', '.eml files'.
| 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' guidance is limited to a redundant trigger phrase. There is no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'email parser' repeated twice. It misses natural variations users would say like 'parse email', 'extract email data', 'read email headers', 'email content', '.eml files', or 'inbox processing'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'email parser' is somewhat specific to a niche domain, which reduces conflict risk with unrelated skills. However, the lack of detail about what kind of email parsing it does could cause 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 an empty shell—a boilerplate template that describes what an email parser skill would do without providing any actual email parsing instructions, code, or workflows. It contains no actionable content whatsoever: no parsing libraries, no code examples, no input/output formats, and no validation steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for parsing emails (e.g., using Python's `email` module or `mailparser` library) with sample input and expected output.
Define a clear workflow: e.g., 1) Read raw email → 2) Parse headers/body/attachments → 3) Extract structured data → 4) Validate extracted fields, with explicit validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual instructions and patterns for email parsing.
Add references to supplementary files for advanced topics (e.g., MIME handling, attachment extraction, calendar invite parsing) to provide progressive disclosure.
| 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 ways to ask for help rather than showing how to parse emails. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely claims it 'provides step-by-step guidance' without actually containing any. | 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 overview from detailed content. 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
4dee593
- 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.