email

Email management and automation. Send, read, search, and organize emails across multiple providers.

Quality

41%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/email/SKILL.md

Quality

Content

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a feature listing and marketing blurb rather than an actionable skill document. It provides no executable code, no configuration guidance, no authentication setup, and no workflows for any of the claimed capabilities. Claude would gain almost nothing from this content that it doesn't already know.

Suggestions

Add concrete, executable code examples for at least the core operations (send email, read inbox, search) with a specific provider, including authentication setup and library imports.

Define clear multi-step workflows for operations like sending email (authenticate → compose → validate recipients → send → confirm delivery) with explicit validation checkpoints.

Include provider-specific configuration details (e.g., Gmail API credentials setup, IMAP/SMTP connection strings) since these are the non-obvious details Claude actually needs.

Either add bundle files for provider-specific guides (GMAIL.md, OUTLOOK.md, IMAP.md) with clear references from the main skill, or inline the essential details if the skill is meant to be self-contained.

Dimension	Reasoning	Score
Conciseness	The content is relatively brief and doesn't over-explain concepts, but the feature list and provider list are essentially just labels with no actionable value—they take up tokens without teaching Claude anything it doesn't already know.	2 / 3
Actionability	There is no concrete, executable guidance whatsoever—no code, no API calls, no commands, no configuration steps. The 'Usage Examples' are just natural language prompts, not actionable instructions for how to actually send, read, or search emails.	1 / 3
Workflow Clarity	There are no steps, sequences, or workflows defined. For a skill involving email operations (sending, bulk operations, authentication), there should be clear multi-step processes with validation, but none are provided.	1 / 3
Progressive Disclosure	The content is a shallow overview with no references to supporting files, no bundle files exist, and there is no structured navigation to deeper content. It reads like a feature advertisement rather than a skill document.	1 / 3
	Total	5 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and lists concrete actions well, establishing a clear niche around email management. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding trigger guidance and a few more natural keyword variations would strengthen it significantly.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about sending, reading, replying to, or managing emails.'

Include additional natural trigger terms and provider names users might mention, such as 'inbox', 'Gmail', 'Outlook', 'draft', 'reply', 'attachment', or 'mail'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Send, read, search, and organize emails' and mentions 'multiple providers'. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes natural keywords like 'email', 'send', 'read', 'search', 'organize' which users would say, but misses common variations like 'inbox', 'Gmail', 'Outlook', 'draft', 'reply', 'attachment', or 'mail'.	2 / 3
Distinctiveness Conflict Risk	Email management is a clear, distinct niche. The combination of 'email', 'send', 'read', 'search', 'organize', and 'multiple providers' makes it unlikely to conflict with other skills.	3 / 3
	Total	10 / 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: about 1 month 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.