himalaya

Himalaya CLI for IMAP/SMTP mail: list, read, search, compose, reply, forward, copy, move, delete.

Quality

77%

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

Quality

Content

80%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 well-structured, command-dense reference with excellent progressive disclosure into two real, accurately described reference files. Its weaknesses are the missing validation/verification steps around destructive and batch mail operations and the irrelevant PilotDeck migration metadata that pads the file.

Suggestions

Add verification checkpoints after destructive or batch operations, e.g. after "himalaya message move <id> <folder>" re-run "himalaya envelope list" to confirm the message landed correctly.

Remove or relocate the "PilotDeck Migration Note" section; it is review-process metadata, not skill content, and wastes context tokens.

Clarify the search syntax (e.g. that "from alice@example.com subject invoice" are filter arguments to "envelope list") so the one search example is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-focused with minimal prose ("Use `himalaya` for IMAP/SMTP email from shell"), but the "PilotDeck Migration Note" section is review/migration metadata that does not help execute the skill and could be trimmed, fitting the efficient-with-minor-excess (4) anchor rather than every-token-earns-its-place (5).	4 / 5
Actionability	Every section provides copy-paste-ready commands (e.g. "himalaya envelope list", "himalaya message reply <id>", "himalaya flag add <id> --flag seen") covering the common mail cases (list, read, search, compose, reply, forward, copy, move, delete, flag), matching the fully-executable anchor.	5 / 5
Workflow Clarity	Sections are sensibly sequenced (Setup → Read/search → Write → Organize) and a Safety section says "Confirm before sending, deleting, or moving many messages", but destructive and batch operations (delete, move, copy) lack validation/verification checkpoints (e.g. re-listing the folder to confirm the move), which caps workflow clarity at 3 per the rubric guidelines.	3 / 5
Progressive Disclosure	The body is a concise overview with two clearly signaled, one-level-deep references ("references/configuration.md": account config, auth, backend setup; "references/message-composition.md": MML compose syntax), both of which exist on disk and match their descriptions; detailed MML content is correctly deferred ("read `references/message-composition.md` first").	5 / 5
	Total	17 / 20 Passed

Description

75%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 strong on specificity and distinctiveness, listing nine concrete mail actions tied to a named tool and protocol. Its main weakness is the missing "Use when..." trigger clause, which caps completeness, plus a few natural synonyms (email, send, inbox) that would improve trigger matching.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to read, send, reply to, forward, or organize email, or mentions himalaya, IMAP, SMTP, or their inbox."

Include common user-facing synonyms such as "email" and "send" alongside "mail" to broaden natural trigger matching.

Consider mentioning account/configuration tasks (e.g. "configure mail accounts") since setup is a core part of the skill body.

Dimension	Reasoning	Score
Specificity	"list, read, search, compose, reply, forward, copy, move, delete" lists nine concrete actions and names the domain ("IMAP/SMTP mail"), matching the comprehensive-coverage anchor; coverage of core mail operations is complete rather than having minor gaps.	5 / 5
Completeness	The "what" is clear and concrete, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines; it is not 4 because the "when" is entirely absent rather than merely implicit or under-specified.	3 / 5
Trigger Term Quality	Natural terms like "mail", "search", "reply", "forward", and "compose" are present, but common variations users would say are missing ("email", "send", "inbox"), so it falls between the good-coverage (4) and comprehensive-synonym (5) anchors, closer to 4.	4 / 5
Distinctiveness Conflict Risk	"Himalaya CLI for IMAP/SMTP mail" names a specific tool and protocol niche with distinct triggers, giving minimal conflict risk with other skills; it fits the clear-niche anchor exactly.	5 / 5
	Total	17 / 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: OpenBMB/PilotDeck
Path: skills/himalaya/SKILL.md
Commit: 66bfd09

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