email-parser

Email Parser - Auto-activating skill for Business Automation. Triggers on: email parser, email parser Part of the Business Automation skill category.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill email-parser

What are skills?

1.05x

Quality

Does it follow best practices?

Impact

98%

1.05x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/email-parser/SKILL.md

SKILL.md

Review

Evals

Discovery

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 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 .eml and .msg formats.'

Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions parsing emails, extracting email content, reading .eml files, or processing inbox messages.'

Remove the redundant duplicate trigger term and expand to include variations users would naturally say like 'email extraction', 'read email file', 'email headers', 'email attachments'.

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-case explanation.	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 emails', '.eml files', or 'inbox'.	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

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 substantive content. It describes meta-information about when the skill activates and what it claims to do, but provides zero actual guidance on how to parse emails. There are no code examples, no library recommendations, no parsing techniques, and no workflows.

Suggestions

Add executable Python code examples showing how to parse emails using libraries like `email`, `mailparser`, or `imapclient`

Include specific parsing patterns for extracting common fields (sender, subject, body, attachments, dates)

Define a clear workflow: connect to mailbox -> fetch emails -> parse content -> extract structured data -> validate output

Remove the meta-description sections ('When to Use', 'Example Triggers') and replace with actual technical content

Dimension	Reasoning	Score
Conciseness	The content is padded with generic filler that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless without specifics.	1 / 3
Actionability	No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly but never shows how to actually parse an email - no libraries, no code examples, no specific techniques.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps for parsing emails, no validation checkpoints, and no process to follow. The content only describes when the skill activates, not what to do.	1 / 3
Progressive Disclosure	The content is organized into clear sections with headers, but there's no actual content to disclose progressively. No references to detailed documentation or examples exist.	2 / 3
	Total	5 / 12 Passed

Validation

81%

Warnings & errors only

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: 2 days ago

Table of Contents

Discovery Implementation Validation

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.