meeting-scheduler
Handles end-to-end meeting scheduling using the Superhuman Mail MCP server — from finding available times to sending the invite or proposing times via email. Use this skill whenever someone asks to "schedule a meeting with [person]", "find a time to meet", "book a call", "set up a meeting", "when am I free to meet with [person]", "propose times to [person]", "send my availability", "create a meeting invite", "schedule a 1:1", "find overlap in our calendars", "reschedule my meeting with [person]", or any variation of coordinating a meeting. Also trigger when someone says "I need to find time with [person]", "can you check my calendar and suggest times", "set up a recurring sync", "block time for [task]", or when an email thread involves scheduling and the user wants to act on it. Trigger broadly — if someone needs help coordinating when people meet, this skill should activate.
88
83%
Does it follow best practices?
Impact
98%
1.66xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 strong skill description with exceptional trigger term coverage and clear completeness in answering both what and when. Its main weakness is that the 'what' portion could be more specific about the concrete actions and capabilities beyond the high-level 'finding available times to sending the invite', as the description is heavily weighted toward trigger phrases rather than capability enumeration. The description is also somewhat verbose and repetitive in its trigger examples.
Suggestions
Expand the capability description to list more specific concrete actions (e.g., 'checks calendar availability, detects scheduling conflicts, creates calendar events, sends meeting invites, proposes multiple time slots, handles rescheduling, sets up recurring meetings') rather than relying so heavily on trigger phrase enumeration.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (meeting scheduling) and mentions some actions like 'finding available times', 'sending the invite', and 'proposing times via email', but the actual capabilities are not comprehensively listed — it's more focused on trigger phrases than detailing specific concrete actions like calendar lookup, conflict detection, recurring meeting creation, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (end-to-end meeting scheduling from finding available times to sending invites via Superhuman Mail MCP server) and 'when' (extensive explicit 'Use this skill whenever...' clause with numerous trigger scenarios). The 'when' guidance is exceptionally thorough. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'schedule a meeting', 'find a time to meet', 'book a call', 'set up a meeting', 'when am I free', 'propose times', 'send my availability', 'create a meeting invite', 'schedule a 1:1', 'reschedule', 'find overlap in our calendars', 'block time', 'check my calendar'. These are highly natural and comprehensive. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to meeting scheduling via the Superhuman Mail MCP server, which is a distinct niche. The mention of the specific tool (Superhuman Mail MCP server) and the focused domain (meeting coordination) make it unlikely to conflict with other skills like general email handling or calendar viewing. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and well-defined validation checkpoints throughout the scheduling process. Its main weakness is moderate verbosity — the guidelines section largely restates rules already embedded in the workflow steps, and some explanatory text could be trimmed. The single-file structure is adequate but could benefit from tighter editing given its length.
Suggestions
Remove the 'Important guidelines' section or reduce it to only net-new rules not already stated in the workflow steps — identity verification, user inclusion, and working hours filtering are all thoroughly covered inline.
Trim the introductory paragraph ('You are a scheduling assistant...') since the workflow steps already make the skill's purpose self-evident.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. Phrases like 'You are a scheduling assistant that handles the full loop' and explanations of what to do when context is available are somewhat redundant for Claude. The guidelines section at the end repeats several points already covered in the workflow steps (e.g., verifying identity, including the user on invites, respecting working hours). Could be tightened by ~30%. | 2 / 3 |
Actionability | The skill provides specific MCP tool names, exact parameter names (participants, start_date, duration_minutes, etc.), concrete format requirements (RFC3339), and clear examples of how to format output and draft instructions. The guidance is directly executable with the named Superhuman Mail MCP tools. | 3 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced (parse → resolve identity → check availability → filter timezones → present options → book/email/block) with explicit validation checkpoints: confirming identity before proceeding, filtering slots across timezones with a clear fallback if all are eliminated, requiring user confirmation before booking, and presenting drafts for review before sending. Error recovery paths are well-defined (ambiguous contacts, no available slots, timezone conflicts). | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents, which is acceptable given no bundle files exist. However, at ~150+ lines, sections like the detailed guidelines and the scheduling threads handling could benefit from being split out or condensed. The internal structure with clear headers is good, but the length pushes it beyond ideal for a single SKILL.md. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- superhuman/mcp-mail
- Commit
03565c9
- 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.