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).

1.69x

Quality

73%

Does it follow best practices?

Impact

93%

1.69x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/himalaya/SKILL.md

Quality

Discovery

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.

This is a strong description with excellent specificity and distinctiveness, clearly naming the tool, protocols, and concrete actions. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are natural and comprehensive for the email CLI domain.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to send, read, or manage emails from the command line, or mentions himalaya, IMAP, or SMTP.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: list, read, write, reply, forward, search, and organize emails. Also mentions specific protocols (IMAP/SMTP), multiple accounts support, and MML composition.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions and capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the nature of the actions described.	2 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'emails', 'IMAP', 'SMTP', 'terminal', 'himalaya', 'reply', 'forward', 'search', plus the tool name itself. Covers both the tool name and the domain vocabulary well.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — references a specific CLI tool ('himalaya'), specific protocols (IMAP/SMTP), terminal-based email management, and MML. Very unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a solid, actionable CLI reference skill with concrete, executable commands covering all major himalaya operations. Its main weaknesses are moderate verbosity—particularly the full config file that duplicates what should be in the referenced configuration.md—and the lack of validation steps after configuration setup. The structure is clear but could benefit from pushing detailed content to reference files and adding a connection verification step.

Suggestions

Move the full config.toml example to references/configuration.md and keep only the wizard command (`himalaya account configure`) plus a brief note in the main skill, reducing duplication and length.

Add a validation step after configuration setup, e.g., `himalaya account check` or `himalaya envelope list` to verify the connection works before proceeding to other operations.

Consider adding a brief 'Common workflow' section showing a typical sequence (e.g., list → read → reply) to improve workflow clarity beyond individual command references.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete commands, but includes some unnecessary elements like the full config file example (which could be in the referenced configuration.md) and some light explanatory text that could be trimmed. The inline comments and section headers are generally lean.	2 / 3
Actionability	Every operation includes fully executable, copy-paste ready bash commands with realistic examples. The configuration file is complete and specific, commands include concrete flags and arguments, and multiple variations are shown (e.g., reply vs reply-all, interactive vs piped compose).	3 / 3
Workflow Clarity	The skill is organized as a reference of individual commands rather than multi-step workflows. While the prerequisites section establishes setup order, there are no validation checkpoints (e.g., verifying config works before proceeding, checking connection after setup). For a CLI reference skill this is mostly acceptable, but the configuration setup lacks a verification step like testing the connection.	2 / 3
Progressive Disclosure	References to configuration.md and message-composition.md are clearly signaled at the top, which is good. However, the main file is quite long (~150 lines of content) and the full configuration example could live in the referenced configuration.md rather than being duplicated here. The skill would benefit from a leaner overview with more content pushed to reference files.	2 / 3
	Total	9 / 12 Passed

Validation

72%

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 — 8 / 11 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	8 / 11 Passed

Repository: attilaczudor/Test
Commit: b3cef5f

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