Content
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, actionable skill that provides clear step-by-step guidance with specific MCP tool calls and parameters. The workflow is well-sequenced with a complete output template and safety guardrails. Minor weaknesses include some unnecessary framing/explanatory text and a slightly long single-file structure that could benefit from tighter editing.
Suggestions
Trim the introductory paragraphs — Claude doesn't need to be told 'Your job is to give the user a calm, structured start to their day' or what the MCP server does at a high level. Jump straight into the workflow.
Consider extracting the detailed categorization criteria (Urgent/Important/FYI/Noise definitions) into a referenced file to keep the main SKILL.md as a leaner overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary framing (e.g., 'Your job is to give the user a calm, structured start to their day') and explanatory text that Claude doesn't need. The preamble about what the skill does and the MCP server could be trimmed. However, the categorization criteria and action steps are well-justified and earn their tokens. | 2 / 3 |
Actionability | The skill provides specific MCP tool calls with exact parameter names (e.g., `is_unread: true`, `labels: ["INBOX"]`, `limit: 50`), concrete query strings to use, specific tool methods like `Superhuman_Mail.create_or_update_draft` and `Superhuman_Mail.update_thread`, and a complete output template. This is highly executable guidance. | 3 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced (gather → categorize → present → offer actions), with explicit parallel execution in Step 1, clear categorization criteria in Step 2, a structured output template in Step 3, and concrete follow-up actions in Step 4. The 'Important notes' section includes edge case handling (50+ unread inbox) and a critical safety constraint (never send without approval). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a fairly long single file with no references to supporting materials. The categorization criteria, output template, and important notes could potentially be split into referenced files for a cleaner overview. However, for a skill of this complexity, keeping it in one file is defensible. | 2 / 3 |
Total | 10 / 12 Passed |