himalaya

Himalaya CLI: IMAP/SMTP email from terminal.

Quality

58%

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/email/himalaya/SKILL.md

Quality

Content

76%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 strong, highly actionable command reference with good file structure and a valuable silent-failure gotcha, weakened mainly by absent validation/verification steps around destructive send/delete operations.

Suggestions

Add an explicit verification step after send (e.g. list the Sent folder or check exit code) and a confirm-before-delete note to satisfy the destructive/batch validation expectation.

Move the full config.toml block and the alias-syntax deep dive into references/configuration.md, keeping only a minimal example plus a pointer in SKILL.md.

Collapse the redundant reply approaches (template pipe vs. manual build vs. reply-all) into one recommended path with the alternatives noted in one line.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command reference with no padding about what email/IMAP is, though the long inline config.toml block and the duplicated reply approaches leave minor instances that could be trimmed, fitting the efficient-with-minor-over-explanation anchor rather than the every-token-earns-its-place anchor above.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands with real flags across the common cases (e.g. `himalaya envelope list --folder "Sent"`, `cat << 'EOF' \| himalaya template send`, `himalaya message move "Archive" 42`), matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	Sequences exist for reply/forward/compose but lack explicit validation checkpoints, and destructive operations like `message delete` are shown with no verify step, so per the destructive/batch cap it stays at the anchor for steps present but checkpoints missing rather than the clear-sequence anchor above.	3 / 5
Progressive Disclosure	A clear References section signals two one-level-deep files (both verified to exist) with brief descriptions and the overview stays in SKILL.md, but the sizable inline config.toml plus alias gotcha keep it just short of the cleanly-split anchor above.	4 / 5
	Total	16 / 20 Passed

Description

41%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 is compact and identifies a clear, specific niche but is missing action verbs and any explicit trigger/"Use when" guidance, which caps completeness and trigger quality.

Suggestions

Add concrete actions, e.g. "Send, read, search, and organize IMAP/SMTP email from the terminal."

Append a trigger clause such as "Use when the user wants to send or manage email from the command line or mentions himalaya."

Soften the protocol jargon with natural terms like "email" and "inbox" so it matches how users phrase the request.

Dimension	Reasoning	Score
Specificity	The phrase "Himalaya CLI: IMAP/SMTP email from terminal" names the specific tool and protocol domain but states no concrete actions (no send/read/search/manage verbs), matching the anchor that names the domain with minimal or absent actions rather than the entirely-vague anchor below.	2 / 5
Completeness	It gives a clear "what" (IMAP/SMTP email from terminal via Himalaya) but provides no "when"/"Use when..." clause, so per the cap it lands at the anchor for a clear what with missing or only weakly implied when.	3 / 5
Trigger Term Quality	"email" and "terminal" are natural terms, but the description is dominated by technical jargon (IMAP/SMTP, CLI) and omits the action phrases users actually say ("send an email", "check my inbox"), fitting the anchor with one or two generic keywords missing the natural phrases.	2 / 5
Distinctiveness Conflict Risk	Naming a specific tool (Himalaya) plus a narrow niche (terminal IMAP/SMTP email) makes it mostly distinct with only minor overlap risk against related email skills; it lacks the explicit trigger phrases needed for the anchor above.	4 / 5
	Total	11 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/email/himalaya/SKILL.md
Commit: 48f69e5

Reviewed: 5 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.