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).
79
73%
Does it follow best practices?
Impact
93%
1.69xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/himalaya/SKILL.mdQuality
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. Its 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 naturally varied and cover both technical and common user language.
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'. Covers the tool name, protocols, and common email actions users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'himalaya', the CLI/terminal context, IMAP/SMTP protocols, and MML format. 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 reference-style skill with excellent actionability—nearly every operation has a concrete, executable command example. The main weaknesses are that it's somewhat long for a SKILL.md (the full config TOML and exhaustive command listing could be partially offloaded to reference files), and it lacks workflow sequencing with validation steps, particularly around setup verification and destructive operations like delete.
Suggestions
Add a verification step after configuration setup (e.g., 'himalaya account check' or 'himalaya envelope list' to confirm connectivity) to improve workflow clarity.
Move the full TOML configuration example to the referenced `references/configuration.md` and keep only a minimal example or just the wizard command in SKILL.md to improve conciseness and progressive disclosure.
Add a caution or verification note before destructive operations like `message delete`, such as confirming the message ID with `message read` first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete commands, but includes some unnecessary elements like the full TOML configuration example (which is quite long) and the prerequisites section stating obvious things. The tips section also has some filler. However, it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | Nearly every section provides copy-paste ready commands with concrete examples including specific flags, message IDs, folder names, and email addresses. The configuration example is complete and executable, and operations cover the full range of email management tasks. | 3 / 3 |
Workflow Clarity | Individual commands are clear, but there's no sequenced workflow with validation checkpoints. For example, after configuration setup there's no verification step (e.g., 'test connection with himalaya account check'). The delete operation has no confirmation or undo guidance. Operations are presented as isolated commands rather than connected workflows. | 2 / 3 |
Progressive Disclosure | References to `references/configuration.md` and `references/message-composition.md` are mentioned, but no bundle files were provided to verify they exist. The main file includes a full configuration example that could arguably live in the referenced configuration file, and the content is somewhat long for a SKILL.md overview. The structure is flat with good section headers but could better leverage the referenced files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%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
Table of Contents
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.