CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

The body is a highly actionable, domain-dense operating manual with real commands, output shapes, and validated batch-archive patterns. Its main structural weakness is that it is monolithic — the Front search API reference and sender heuristics are strong candidates for one-level-deep reference files — and it carries minor duplication and time-sensitive field notes.

Suggestions

Move the 'Front Search API Reference' section (~45 lines of filter/status/date syntax) into a references/front-search.md file and keep only the essential gotchas (no is:unread, unix timestamps, no negation, 15-filter max) inline with a clear pointer.

Deduplicate the [aih] VIP rule, which appears nearly verbatim in both 'Key Context' and 'Signals for "Reply Needed"', and consolidate it into one canonical location.

Add an explicit verification checkpoint before the fast `archive-ids` path (e.g., echo the ID list with subjects and confirm before executing), mirroring the dry-run discipline already present for archive-bulk.

DimensionReasoningScore

Conciseness

Nearly every token carries non-obvious domain detail (Front search quirks, CLI flags, cache TTL, real IDs) with no explanations of things Claude already knows, but the [aih] VIP rule is duplicated nearly verbatim in two sections and the "migration to `body` underway" field note is time-sensitive churn that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with flags, pagination, and realistic examples (e.g., `joelclaw email inbox -q "is:open is:unreplied" -n 50`, jq extraction patterns with a backwards-compatible variant), plus the exact read output shape.

5 / 5

Workflow Clarity

The four-step triage workflow is clearly sequenced and batch/destructive operations have validation (archive-bulk is dry-run by default, "Always dry-run first to verify the query matches what you expect"), but the fast `archive-ids` path has no explicit verify-before-execute checkpoint and 429/rate-limit handling is advisory rather than a recovery loop.

4 / 5

Progressive Disclosure

Sections are flat and well-organized with no nested references, but the ~45-line Front Search API Reference is inlined in SKILL.md instead of a separate references/ file — no bundle reference files exist at all, so content that should be separate is inline.

3 / 5

Total

16

/

20

Passed

Description

96%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.

A strong description: concrete third-person capability list paired with an explicit, natural-language trigger clause. The only weakness is slight breadth at the edges (reply drafting, the catch-all trigger) that could collide with other email-related skills.

DimensionReasoningScore

Specificity

The description lists five concrete, comprehensive actions — "Scan, categorize, archive noise, surface actionable items, and draft replies" — in third person, fully covering the triage domain rather than just naming it.

5 / 5

Completeness

Explicitly answers both "what" ("Triage Joel's email inboxes via the joelclaw email CLI" plus concrete actions) and "when" with an explicit "Use when:" clause containing concrete trigger phrases — the exact 5-anchor pattern.

5 / 5

Trigger Term Quality

Eight natural trigger phrases users would actually say ("check my email", "scan inbox", "what needs a reply", "clean up inbox", "archive junk", etc.) plus a catch-all clause; matches the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The niche (Joel's Front inboxes via a specific CLI) is mostly distinct, but "draft replies" and the broad "any request involving email inbox review or cleanup" leave minor overlap risk with general email/reply-drafting skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.