himalaya

CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).

Quality

71%

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

The canonical home for this skill is himalaya in Hung-Reo/hungreo-openclaw

Quality

Content

68%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 highly actionable with executable commands throughout and good progressive disclosure to real reference files. It loses points for an inline config block that duplicates a reference file and for missing validation checkpoints around destructive email operations.

Suggestions

Remove the inline TOML configuration block from SKILL.md and point readers to references/configuration.md, keeping only the wizard command inline.

Add a brief validation/verification step before destructive or batch operations (e.g., confirm the message ID by reading first, or list the target folder before moving) to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean command listings, but a full inline TOML configuration block duplicates content already in references/configuration.md, an unnecessary repetition that prevents a higher score.	3 / 5
Actionability	Nearly every section provides copy-paste ready, executable commands (e.g., `himalaya envelope list`, `himalaya message read 42`, `himalaya message move 42 "Archive"`) covering the common cases fully.	5 / 5
Workflow Clarity	Operations are listed as a catalog without sequenced workflows or validation checkpoints, and the destructive operations (delete, move, flag remove) lack verification steps, so the rubric cap of 3 applies.	3 / 5
Progressive Disclosure	A clear References section signals two real one-level-deep files (configuration.md, message-composition.md) and the command overview is appropriately inline, though the duplicated inline config block is a minor organization gap.	4 / 5
	Total	15 / 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 specific and clearly distinct, listing many concrete email actions, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding natural trigger phrasing would raise the score.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to read, send, reply to, or organize email from the terminal" to lift completeness above 3.

Include more natural synonyms users say (e.g., "inbox", "mail", "send email") to improve trigger term coverage toward 5.

Dimension	Reasoning	Score
Specificity	The description enumerates seven concrete actions ("list, read, write, reply, forward, search, and organize emails"), matching the anchor for multiple specific concrete actions with comprehensive coverage.	5 / 5
Completeness	It clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "emails", "manage emails", and "from the terminal" are present, but common synonyms such as "inbox", standalone "mail", or "send email" are missing, so it falls just short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The niche is clearly defined (CLI email client over IMAP/SMTP with MML composition), giving it distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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: Bitterbot-AI/bitterbot-desktop
Path: skills/himalaya/SKILL.md
Commit: 017761f

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.