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

85%

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

Quality

Content

87%

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

An actionable, lean CLI reference with well-signaled, real bundle references and copy-paste commands throughout. The main gap is the absence of validation/verification steps around destructive operations and configuration setup.

Suggestions

Add verification steps after destructive operations, e.g. re-list the folder with `himalaya envelope list` after `message delete`/`move` to confirm the result.

Add a validation checkpoint to configuration setup, e.g. run `himalaya account list` after configuring to confirm credentials work before first use.

Avoid duplicating the full config TOML inline since it overlaps `references/configuration.md`; a minimal quick-start snippet plus the reference pointer would reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean: each operation is a header plus an executable command with no padding explaining what IMAP/SMTP or email are, respecting Claude's existing knowledge.	3 / 3
Actionability	Every operation ships a concrete, copy-paste-ready `himalaya` command (e.g. `himalaya message reply 42 --all`, `cat << EOF \| himalaya template send`), fully executable rather than pseudocode.	3 / 3
Workflow Clarity	Operations are cataloged clearly but destructive actions (delete, move, flag remove) and the config setup lack validation/verification checkpoints, which caps workflow clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	A clear References section signals two real one-level-deep files (`references/configuration.md`, `references/message-composition.md`) for detail, while the body keeps common operations inline with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

82%

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-targeted description with concrete actions and natural trigger terms, but it lacks an explicit "Use when..." trigger clause, capping completeness at 2. Adding a situational trigger would round it out.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to manage, read, reply to, forward, or search emails from the terminal."

Consider adding common user phrasings like "inbox", "mail", or "send email" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "list, read, write, reply, forward, search, and organize emails" — matching the anchor for enumerating several specific capabilities rather than vague language.	3 / 3
Completeness	Clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Covers natural terms users would say ("emails", "reply", "forward", "search", "list", "terminal") with good breadth; the technical "MML (MIME Meta Language)" is additive rather than the only vocabulary.	3 / 3
Distinctiveness Conflict Risk	The "CLI to manage emails via IMAP/SMTP" niche with the `himalaya` tool name is clearly distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: e73c717

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