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.
83
Quality
77%
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
89%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-constructed skill description with explicit 'Use when' guidance and good trigger term coverage including specific email providers. The main weakness is moderate specificity - it could better detail what the summaries include or what 'important messages' means. Overall, it provides sufficient information for Claude to select this skill appropriately.
Suggestions
Add more specific capabilities like 'categorizes by sender priority', 'extracts action items', or 'highlights unread count' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (email accounts) and lists some actions (logs into, generates summaries), but lacks comprehensive detail about specific capabilities like filtering, categorization, or what the summaries contain. | 2 / 3 |
Completeness | Clearly answers both what (logs into email accounts, generates daily summaries) AND when (explicit 'Use when' clause with triggers: summary of emails, check important messages, create daily digests). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'email summary', 'important messages', 'daily email digests', plus specific provider names (Gmail, Outlook, QQ Mail). Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on email login and summarization with distinct triggers (Gmail, Outlook, email summaries, digests). Unlikely to conflict with general document or communication skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable guidance for email automation with browser-use CLI, with good coverage of multiple email providers and automation options. However, it's overly verbose for a skill file, lacks validation checkpoints in workflows (especially important for login-dependent operations), and would benefit from splitting advanced content like scheduling into separate files.
Suggestions
Add explicit validation steps after login attempts (e.g., 'Verify login succeeded by checking for inbox elements before proceeding')
Move scheduling configuration (crontab, launchd) and output examples to separate reference files to reduce main skill length
Add error handling in the complete script with checks like 'if page contains login form, authentication failed'
Trim the feature list and security tips sections which add length without adding actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose with some unnecessary sections (e.g., feature list with emojis, extensive output examples, detailed launchd plist). The core functionality could be conveyed more efficiently, though it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable bash commands and scripts throughout. Code examples are copy-paste ready with specific browser-use CLI commands, JavaScript extraction code, and complete shell scripts for automation. | 3 / 3 |
Workflow Clarity | Steps are listed sequentially but lack explicit validation checkpoints. The complete script has numbered steps but no error handling or verification between steps (e.g., no check if login succeeded before extracting emails). Missing feedback loops for login failures. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one monolithic file. The extensive scheduling configuration (crontab, launchd) and output examples could be split into separate reference files. No external file references for advanced topics. | 2 / 3 |
Total | 9 / 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 | |
45f9fac
Table of Contents
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.