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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured triage skill with executable commands and a clear workflow. Its main weakness is monolithic structure: substantial API reference material is inlined rather than split into separate reference files.

Suggestions

Move the Front Search API Reference into a references/ file (e.g. SEARCH.md) and keep only the essential syntax summary in SKILL.md, linking out for the full reference.

Promote dry-run verification to an explicit numbered checkpoint in the Triage Workflow (e.g. '3.5 Dry-run archive queries before executing') so batch/destructive validation is unmissable.

Replace hard-coded example dates (2026-02-01, 2026-01-15) with relative phrasing like '<recent date>' or move them to a dated examples section to avoid time-sensitive drift.

Dimension	Reasoning	Score
Conciseness	Mostly lean executable commands with no padding on known concepts, but the inlined Search API reference, Signals lists, and dated examples (2026-02-01) could be trimmed slightly. Not a 5 because a few inline reference blocks exceed lean.	4 / 5
Actionability	Copy-paste-ready CLI commands with all flags, jq extraction patterns, and documented output shapes cover every common operation (scan, archive single/bulk, read, list).	5 / 5
Workflow Clarity	Four-step triage workflow is clearly sequenced and batch/destructive archive operations carry dry-run validation, but that validation is scattered rather than an explicit numbered checkpoint within the workflow.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no buried references, but the substantial inlined Search API reference and Key Context material are not split into reference files and no references/ bundle is used.	3 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete actions, comprehensive natural triggers, and an explicit Use-when clause, all scoped to a distinct niche. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists five concrete triage actions ('Scan, categorize, archive noise, surface actionable items, and draft replies'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (five named actions) and 'when' via a concrete 'Use when:' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Provides nine natural trigger phrases including synonyms ('check my email', 'scan inbox', 'triage email', 'archive junk'), well beyond what users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Scoped to 'Joel's email inboxes via the joelclaw email CLI' gives it a clear niche with minimal overlap against other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/email-triage/SKILL.md
Commit: 7094ced

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.