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

73%

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

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.

A well-structured, highly actionable command reference with real, clearly-signaled bundle files and efficient prose. The weaknesses are the missing validation/caution around destructive operations (delete, move) and the redundant inline configuration example that duplicates the dedicated reference file.

Suggestions

Add a caution and verification step around destructive operations — e.g. note whether `message delete` moves to trash or permanently deletes, and suggest re-running `himalaya envelope list` to confirm the result.

Replace the full inline config.toml with the wizard command plus a minimal 3-4 line stub, pointing to references/configuration.md for the complete example, to remove the duplication.

Sequence the setup as an explicit numbered workflow (install → verify with `himalaya --version` → configure → send a test message) so the getting-started path has clear checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable bash blocks with almost no concept over-explanation, but the ~22-line inline config.toml example duplicates what references/configuration.md already provides and could be trimmed to a pointer, fitting the 4 anchor (minor trimmable excess).	4 / 5
Actionability	Every operation — list, search, read, reply, forward, write, template send, move, copy, delete, flags, accounts, attachments, output formats, debug — ships a copy-paste-ready command, including a working heredoc pipe for non-interactive sending, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	Prerequisites → wizard/manual config → operations gives a coherent setup sequence and the tip about message IDs being folder-relative is a useful checkpoint, but the destructive `himalaya message delete 42` operation has no validation, caution, or trash-vs-permanent note, so the destructive-operation cap holds the score at 3.	3 / 5
Progressive Disclosure	Both bundle files (references/configuration.md, references/message-composition.md) exist, are one level deep, and are clearly signaled with one-line scope descriptions plus a contextual re-link in Tips; the only gap is the inline config duplicating the reference file, which fits the 4 anchor's minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

71%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 strong, specific description that names the tool, protocols, and a comprehensive set of concrete email actions in third person. Its main weakness is the absence of any explicit "when to use" trigger clause, which caps completeness, and some natural trigger synonyms (send, inbox, mail) are missing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to manage, read, send, or search email from the terminal or mentions himalaya, IMAP, or SMTP."

Include common natural synonyms users would say — "send" (currently only "write"), "inbox", and "mail" — alongside the existing verbs.

Optionally state the "when" in terms of the environment (headless/terminal email workflows) to further reduce overlap with generic email skills.

Dimension	Reasoning	Score
Specificity	"list, read, write, reply, forward, search, and organize emails" names seven concrete actions plus the tool, protocols (IMAP/SMTP), and MML, matching the comprehensive-coverage anchor; there is no meaningful coverage gap for the email-management domain.	5 / 5
Completeness	The "what" is clear and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance — "Use `himalaya` to..." instructs usage rather than stating when the skill applies — which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural verbs like "reply", "forward", "search", and "organize emails from the terminal" give good keyword coverage, but common user phrasings such as "send", "inbox", and "mail" are missing, so it falls short of the comprehensive synonym coverage of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Binding the skill to the specific `himalaya` binary and MML makes it mostly distinct, but it could still trigger on the bare keyword "email" in overlap with other email-related skills, so it fits the minor-overlap 4 anchor rather than the minimal-conflict 5 anchor.	4 / 5
	Total	16 / 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: 1c7dc1b

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