email-daily-summary
Automatically logs into email accounts (Gmail, Outlook, QQ Mail, etc.) and generates daily email summaries. Use when the user wants to get a summary of their emails, check important messages, or create daily email digests.
74
63%
Does it follow best practices?
Impact
91%
1.89xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/10e9928a/email-daily-summary/SKILL.mdQuality
Discovery
100%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 is a well-crafted skill description that clearly communicates its capabilities, includes natural trigger terms across multiple email platforms, and provides explicit 'Use when' guidance. It follows the third-person voice convention and is concise without being vague. The description closely matches the rubric's examples of good descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'logs into email accounts', 'generates daily email summaries', and names specific platforms (Gmail, Outlook, QQ Mail). These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (logs into email accounts and generates daily summaries) and 'when' (explicit 'Use when' clause covering summary requests, checking important messages, and creating daily digests). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'email', 'Gmail', 'Outlook', 'summary', 'important messages', 'daily email digests'. These cover common variations of how users would phrase email summary requests. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of email login automation, specific email providers, and daily summary generation creates a clear niche. Unlikely to conflict with general email composition or other document summary skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is overly verbose and monolithic, mixing quick-start instructions with scheduling configuration, security advice, and aspirational output examples all in one file. While it provides some concrete commands, many are fragile or pseudocode-like, and the workflow lacks validation checkpoints critical for browser automation. The content would benefit significantly from aggressive trimming and splitting into focused sub-documents.
Suggestions
Cut the content by at least 50%: remove the feature bullet list, the email URL reference table (Claude knows these), the launchd plist XML, and the aspirational output example. Keep only the core workflow.
Add explicit validation steps after each browser-use command (e.g., check page title contains 'Inbox', verify email extraction returned non-empty results) to handle the inherent fragility of browser automation.
Split into multiple files: keep SKILL.md as a concise overview with the recommended workflow, and move scheduling setup, troubleshooting, and alternative login methods to separate referenced documents.
Replace placeholder selectors like '<email_input_index>' with a concrete example showing how to read the state output and identify the correct index, making the guidance truly copy-paste actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It includes extensive boilerplate (emoji decorations, feature lists, output examples that are aspirational rather than functional, full launchd plist XML, a reference table of email URLs Claude already knows). Much of this could be cut by 60%+ without losing actionable content. | 1 / 3 |
Actionability | There are concrete bash commands and some JavaScript/Python snippets, but many are pseudocode-like or require significant adaptation (e.g., 'adjust based on actual DOM structure', placeholder index values like '<email_input_index>'). The Python browser-use examples use an API that may not exist as shown, and the JS selectors are fragile Gmail-specific selectors presented without caveats about frequent DOM changes. | 2 / 3 |
Workflow Clarity | The complete bash script provides a numbered sequence, but there are no validation checkpoints — no checks for whether login succeeded, whether the page loaded correctly, or whether email extraction returned valid data. For a workflow involving browser automation (inherently fragile), missing error handling and validation feedback loops is a significant gap. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to external files. The launchd plist, crontab setup, output examples, security tips, and troubleshooting could all be separate documents. The content is a wall of text that mixes quick-start, advanced configuration, scheduling, and troubleshooting without clear navigation. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
45f9fac
- 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.