agent-mail

Backward-compatible alias for the canonical clawmail protocol. Use when older prompts mention 'agent-mail'. For full, current coordination rules load the `clawmail` skill.

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/agent-mail/SKILL.md

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 content is a well-structured, concise alias skill that clearly directs Claude to the canonical clawmail skill while summarizing current rules. It is actionable and well-organized, with the only mild weakness being the lack of a richer multi-step workflow, which is appropriate for an alias skill.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanations of concepts Claude already knows; the only minor inefficiency is the brief rules summary duplicating intent already covered by the redirect, fitting the 'efficient, minor trims possible' anchor.	4 / 5
Actionability	It provides concrete commands (joelclaw mail, joelclaw mail --help), a specific redirect path (skills/clawmail/SKILL.md), and specific verbs (Announce Starting:, reserve paths), which is mostly executable guidance with minor gaps in full command syntax.	4 / 5
Workflow Clarity	As a single-purpose redirect skill the action is unambiguous via the Immediate Redirect section, and the summary rules give a light sequence; it is not a full validated multi-step workflow, so it sits below the 5 anchor that expects explicit validation checkpoints.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external bundle files, the body uses well-organized sections (Use This Skill When, Current Rules, Immediate Redirect, Related) and a clearly signaled one-level redirect to the canonical skill, matching the simple-skill exception for a 5.	5 / 5
	Total	17 / 20 Passed

Description

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

The description clearly communicates the skill's purpose as a backward-compatible alias and provides an explicit trigger, but it is light on concrete capabilities since the skill mostly redirects. Trigger term coverage is narrow, limited to the single legacy name.

Suggestions

Add one or two natural trigger variations users might say (e.g. 'agent mail', 'old mail protocol') to broaden trigger_term_quality.

State the concrete bridging action more explicitly (e.g. 'translates older agent-mail instructions into current clawmail coordination steps') to lift specificity.

Tighten the 'what' so it reads as a capability, not just a redirect, e.g. 'Bridges older agent-mail prompts to the current clawmail coordination protocol.'

Dimension	Reasoning	Score
Specificity	The description names the domain (alias for clawmail) but the only concrete action is 'load the clawmail skill', which is minimal and generic for an alias skill; it is below the 3 anchor that expects 1-2 concrete actions with some coverage.	2 / 5
Completeness	It answers both 'what' (backward-compatible alias) and 'when' (use when older prompts mention agent-mail) explicitly, with the 'when' being concrete and specific, fitting the anchor where both are present though the 'when' could be slightly more elaborated.	4 / 5
Trigger Term Quality	It includes the natural trigger phrase 'Use when older prompts mention agent-mail' with one relevant keyword, but lacks synonyms or variations users might say, fitting the anchor for some relevant keywords with missing common variations.	3 / 5
Distinctiveness Conflict Risk	The alias has a distinct, explicit trigger tied to the legacy 'agent-mail' name with minimal overlap risk against the canonical clawmail skill, fitting the 'mostly distinct, minor overlap' anchor.	4 / 5
	Total	13 / 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/agent-mail/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.