himalaya

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

Quality

70%

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

72%

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

The content is highly actionable with executable command examples and well-structured progressive disclosure to real reference files, but it could tighten its token use and add explicit verification steps for destructive/batch mail operations.

Suggestions

Remove the PilotDeck Migration Note or relocate it out of the skill body; it is review metadata unrelated to using himalaya.

Add a verification/feedback step for risky operations, e.g. re-list the target folder after `message move`/`copy` and confirm the message landed before proceeding with bulk actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused assuming Claude's competence, but the "PilotDeck Migration Note" section and incidental prose add non-actionable tokens that could be trimmed, fitting the "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	Concrete, copy-paste-ready `himalaya` commands with real flags (e.g. `--flag seen`, `from alice@example.com subject invoice`, `--account`) appear throughout, matching the fully-executable highest anchor.	3 / 3
Workflow Clarity	Sequences and a Safety section exist, but destructive/batch operations (send, delete, move many) lack explicit validation or feedback loops (e.g. verify send succeeded, re-check folder after move), which the rubric caps at 2.	2 / 3
Progressive Disclosure	The overview body points to two well-signaled, one-level-deep references (`references/configuration.md`, `references/message-composition.md`), both real files, with detail appropriately split out — matching the clear-overview anchor.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive, listing nine concrete mail actions, but it is framed in technical CLI/IMAP terms and lacks an explicit "Use when..." trigger clause, leaving trigger quality and completeness at the middle level.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to manage email, read or search an inbox, or send/reply/forward messages from the shell."

Soften the technical framing by including natural terms like "email" and "inbox" alongside "IMAP/SMTP mail".

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — "list, read, search, compose, reply, forward, copy, move, delete" — matching the highest anchor that lists several specific actions rather than a vague domain mention.	3 / 3
Completeness	It clearly answers "what" via the action list but provides no explicit "when"/"Use when..." trigger clause, which per the rubric guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "mail", "list", "read", "search", "compose", "reply", and "forward" are relevant, but the framing leans technical ("CLI for IMAP/SMTP mail") and omits common natural variations such as "email", "inbox", or "send mail".	2 / 3
Distinctiveness Conflict Risk	Naming a specific tool ("Himalaya CLI for IMAP/SMTP mail") carves a clear niche unlikely to trigger for unrelated skills, satisfying the highest distinctiveness anchor.	3 / 3
	Total	10 / 12 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: c88d7d1

Reviewed: about 13 hours 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.