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

Fix and improve this skill with Tessl

tessl review fix ./skills/himalaya/SKILL.md

Quality

Content

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 command reference for the Himalaya CLI with excellent actionability — nearly every operation has a concrete, executable example. However, it's somewhat verbose for a skill file, duplicating configuration content that should live in the referenced configuration.md, and lacks validation checkpoints for destructive operations like delete or multi-step workflows like initial setup. The progressive disclosure could be improved by keeping the SKILL.md as a concise overview and pushing detailed examples to reference files.

Suggestions

Move the full TOML configuration example to references/configuration.md and keep only the wizard command (`himalaya account configure`) plus a brief pointer in the main skill file.

Add a validation step after configuration setup, e.g., 'Verify connection: `himalaya envelope list` — if this returns emails, your config is correct.'

Move less common operations (flags, attachments, debugging, output formats) to a separate reference file to keep the main skill lean and focused on core operations.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete commands, but includes some unnecessary elements like the full TOML config example (which could be in the referenced configuration.md) and the Prerequisites section stating obvious things. The Tips section also has some filler.	2 / 3
Actionability	Nearly every operation includes a concrete, copy-paste-ready command. The configuration example is complete and executable, search syntax is shown by example, and multiple approaches are given for composing emails (interactive, piped template, flags).	3 / 3
Workflow Clarity	The skill is primarily a command reference rather than a multi-step workflow, but the configuration setup lacks validation checkpoints (e.g., verifying the config works with a test connection). The delete operation has no confirmation/verification step, and there's no guidance on error recovery for failed sends or connection issues.	2 / 3
Progressive Disclosure	References to configuration.md and message-composition.md are listed, but the full configuration setup is duplicated inline rather than being deferred to the referenced file. The SKILL.md is quite long (~150 lines of commands) and could benefit from moving less common operations (flags, attachments, debugging) to a reference file.	2 / 3
	Total	9 / 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.

This is a strong description with excellent specificity and distinctiveness, clearly naming the tool (himalaya), its domain (email via CLI), and multiple 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 inclusion of technical terms like IMAP/SMTP and MML adds precision without sacrificing clarity.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to send, read, or manage emails from the terminal, mentions himalaya, or needs CLI-based email access.'

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 description.	2 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'emails', 'IMAP', 'SMTP', 'himalaya', 'terminal', 'reply', 'forward', 'search', 'compose'. Users asking about email from the CLI would naturally use many of these terms.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with the specific tool name 'himalaya', CLI/terminal context, IMAP/SMTP protocols, and MML format. Very unlikely to conflict with other skills.	3 / 3
	Total	11 / 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: b4fc4af

Reviewed: 2 months 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.