email-triage
Triage Joel's email inboxes via the joelclaw email CLI. Scan, categorize, archive noise, surface actionable items, and draft replies. Use when: 'check my email', 'scan inbox', 'triage email', 'what needs a reply', 'clean up inbox', 'archive junk', 'email summary', 'anything important in email', or any request involving email inbox review or cleanup.
90
88%
Does it follow best practices?
Impact
92%
2.87xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 an excellent skill description that hits all the marks. It provides specific concrete actions, names the tool used, includes a comprehensive 'Use when' clause with natural trigger phrases, and is clearly scoped to a distinct niche (Joel's email via a specific CLI). It serves as a strong example of a well-crafted skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scan, categorize, archive noise, surface actionable items, and draft replies. Also names the specific tool ('joelclaw email CLI'). | 3 / 3 |
Completeness | Clearly answers both 'what' (triage email inboxes, scan, categorize, archive, surface actionable items, draft replies) and 'when' (explicit 'Use when:' clause with extensive trigger phrases and a catch-all for email inbox review or cleanup). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'check my email', 'scan inbox', 'triage email', 'what needs a reply', 'clean up inbox', 'archive junk', 'email summary', 'anything important in email'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it's scoped to a specific person's email (Joel's), a specific CLI tool (joelclaw), and a specific domain (email triage/inbox management). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 concrete, executable examples throughout. Its main weakness is that it's somewhat long — the Front Search API reference section is thorough but could be extracted to a separate reference file to improve progressive disclosure and reduce the token footprint of the main skill. The domain-specific knowledge (Joel's inboxes, VIP contacts, noise senders) is well-organized and genuinely useful context Claude wouldn't otherwise have.
Suggestions
Extract the 'Front Search API Reference' section into a separate FRONT_SEARCH_REFERENCE.md file and link to it from the main skill, reducing the main file's token footprint while preserving discoverability.
Consolidate the 'Signals for Archive' and 'Common Noise Senders' sections with the categorization guidance in step 2 to reduce redundancy — or move them to a separate TRIAGE_SIGNALS.md reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive and most content earns its place, but there's some redundancy (e.g., archive signals are listed both in the categorization section and again in dedicated 'Signals for Archive' section). The Front Search API reference section is quite detailed and could potentially be split to a reference file. However, most of this is domain-specific knowledge Claude wouldn't have, so it's largely justified. | 2 / 3 |
Actionability | Excellent actionability throughout — every command is copy-paste ready with real flags and examples, jq patterns are provided for output parsing, and the triage workflow gives concrete steps with executable commands at each stage. The archive-bulk dry-run pattern and archive-ids batching are specific and immediately usable. | 3 / 3 |
Workflow Clarity | The triage workflow is clearly sequenced (load → categorize → present → execute) with explicit validation checkpoints: dry-run before bulk archive, read before deciding, and the presentation format template ensures Joel reviews before action. The 'draft-then-approve for replies — never send directly' constraint adds a critical safety checkpoint for destructive operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a long monolithic file (~200+ lines) where the Front Search API Reference section could be split into a separate reference file. The skill mixes quick-reference material (CLI commands) with detailed API documentation (search filter syntax, entity filters) that would benefit from separation. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- joelhooks/joelclaw
- Commit
ce9ca8e
- 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.