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 real executable examples throughout. Its main weakness is length — the Front Search API reference and CLI command documentation could be split into separate reference files to keep the main skill focused on the triage workflow. The content is well-organized but would benefit from progressive disclosure to reduce token cost when loaded into context.
Suggestions
Extract the Front Search API Reference section into a separate FRONT_SEARCH.md file and link to it from the main skill, keeping only a brief summary of the most critical gotchas (no is:unread, UNIX timestamps only) inline.
Consider moving the full CLI command reference into a separate CLI_REFERENCE.md, keeping only the most-used commands (inbox, archive-ids, archive-bulk, read) with minimal examples in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and contains genuinely useful reference material (Front search API, CLI commands, field names), but some sections are verbose — the search API reference is quite long and could be tightened, and some heuristic lists (signals for archive/reply) include explanations Claude could infer. The 'Canonical Email Interface' section explaining not to use gog is valuable domain knowledge though. | 2 / 3 |
Actionability | Excellent actionability throughout — every CLI command is copy-paste ready with real flags and examples, jq extraction patterns are provided with actual field paths, the triage workflow has concrete steps with executable commands, and the archive operations show both single and bulk patterns with real syntax. | 3 / 3 |
Workflow Clarity | The triage workflow is clearly sequenced (load → categorize → present → execute) with explicit validation steps: dry-run before bulk archive, read before deciding, and the presentation format template provides a clear checkpoint for Joel's approval. The draft-then-approve constraint for replies adds a safety checkpoint. Rate limiting guidance is included for destructive batch operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a monolithic document (~200+ lines) with no references to external files. The Front Search API Reference section and the detailed CLI command reference could be split into separate reference files, with the SKILL.md providing a concise overview and links. For a skill this long, inline reference material competes with the workflow content. | 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
825972c
- 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.