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.

Highly actionable, well-structured content with clean progressive disclosure to real reference files, weakened only by missing concrete validation loops for destructive mail operations and a small block of migration metadata.

Suggestions

Replace advisory Safety bullets with an explicit workflow for batch/destructive ops, e.g. list targets -> confirm count -> execute -> re-list to verify.

Remove or relocate the 'PilotDeck Migration Note' out of the skill body so it does not consume skill context.

Add a brief sequenced setup->read->write->organize flow so the grouped commands read as a coherent workflow.

Dimension	Reasoning	Score
Conciseness	The body is a lean, command-driven reference that assumes Claude's competence, though the 'PilotDeck Migration Note' is review metadata that does not earn its tokens.	4 / 5
Actionability	Copy-paste-ready himalaya commands (folder list, envelope list, message read, message reply, etc.) concretely cover the common read/write/organize cases.	5 / 5
Workflow Clarity	Commands are grouped by task but the destructive/batch operations (delete, move many) lack a concrete validate->fix->retry loop; the Safety section is advisory only, so workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	A concise overview points via clearly signaled, one-level-deep references to real bundle files (references/configuration.md, references/message-composition.md) for deeper detail.	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.

A specific, well-scoped description that names the tool and lists comprehensive actions, but it omits an explicit 'Use when...' trigger clause, capping completeness at 3.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to read, search, send, or organize email from the shell.'

Include the 'email' synonym and common terms like 'inbox' or 'send' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists nine concrete actions (list, read, search, compose, reply, forward, copy, move, delete) over a named IMAP/SMTP mail domain, matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' trigger clause, so per the rubric cap completeness cannot exceed 3.	3 / 5
Trigger Term Quality	Natural mail verbs (read, reply, forward, search) are present, but common synonyms like 'email', 'inbox', and 'send' are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Naming a specific tool (Himalaya) and protocol (IMAP/SMTP) gives it a clear niche with minimal overlap risk against other skills.	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: 9a33f4d

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.