email

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

Quality

48%

Does it follow best practices?

Impact

Pending

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

Discovery

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.

This description effectively communicates specific email capabilities with clear action verbs and establishes a distinct domain. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural keyword variations that users might say when requesting email help.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks to send mail, check inbox, search messages, or manage email accounts'

Include common email-related terms users might say: 'inbox', 'compose', 'reply', 'Gmail', 'Outlook', 'mail', 'messages'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Send, read, search, and organize emails' - these are clear, actionable verbs describing what the skill does.	3 / 3
Completeness	Clearly answers 'what' (send, read, search, organize emails) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes 'emails' and 'email management' which are natural terms, but missing common variations like 'inbox', 'mail', 'Gmail', 'Outlook', 'compose', or 'reply'.	2 / 3
Distinctiveness Conflict Risk	Email management is a clear, distinct domain with specific triggers like 'emails' and 'multiple providers' - unlikely to conflict with other skills like document processing or messaging.	3 / 3
	Total	10 / 12 Passed

Implementation

29%

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 list or marketing overview rather than actionable documentation. While concise, it provides no concrete guidance on how to actually send, read, or search emails - no API calls, no authentication setup, no code examples, and no workflows. Claude would not know how to perform any of these tasks from this content alone.

Suggestions

Add executable code examples for core operations (send email, read inbox, search) with actual library/API calls for at least one provider

Include authentication/setup workflow with explicit steps for connecting to email providers

Add provider-specific reference files (e.g., GMAIL.md, OUTLOOK.md) and link to them from the main skill

Define error handling and validation steps for operations like sending emails (e.g., verify recipient, check send status)

Dimension	Reasoning	Score
Conciseness	The content is extremely lean with no unnecessary explanations. It assumes Claude knows what email, IMAP/SMTP, and labels are without explaining basic concepts.	3 / 3
Actionability	The skill provides zero executable code, commands, or concrete implementation details. It only lists features and natural language usage examples without any actual instructions on how to perform email operations.	1 / 3
Workflow Clarity	No workflows are defined. There are no steps for sending emails, no authentication guidance, no error handling, and no validation checkpoints for any of the listed operations.	1 / 3
Progressive Disclosure	The content is a flat list of features with no references to detailed documentation, no links to provider-specific guides, and no structured navigation to learn more about any capability.	1 / 3
	Total	6 / 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: 45f9fac

Reviewed: 27 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.