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).
81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 93%
↑ 1.69xAgent success when using this skill
Validation for skill structure
Discovery
67%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 description excels at specificity and distinctiveness by naming the exact tool (himalaya) and listing concrete email operations. However, it lacks an explicit 'Use when...' clause which would help Claude know when to select this skill, and could benefit from more natural trigger terms users might actually say when asking for email help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to manage email from the command line, mentions himalaya, or needs terminal-based mail access.'
Include more natural trigger terms users might say: 'mail', 'inbox', 'send email', 'check messages', 'email client'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'list, read, write, reply, forward, search, and organize emails'. Also mentions specific technical capabilities like 'multiple accounts' and 'message composition with MML'. | 3 / 3 |
Completeness | Clearly answers 'what' (CLI email management with specific actions), but lacks an explicit 'Use when...' clause. The 'when' is only implied through the description of capabilities. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'emails', 'IMAP/SMTP', 'terminal', and the tool name 'himalaya', but missing common variations users might say like 'mail', 'inbox', 'send email', or 'check email'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically a CLI tool named 'himalaya' for terminal-based email via IMAP/SMTP. The tool name and terminal/CLI context make it unlikely to conflict with other email-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and conciseness. The commands are concrete and copy-paste ready, and the structure enables quick navigation. The main weakness is the lack of validation steps after configuration and for destructive operations like delete, which would help catch errors early.
Suggestions
Add a verification step after configuration setup (e.g., 'himalaya account check' or 'himalaya envelope list' to confirm connection works)
Include a note about message deletion behavior (trash vs permanent) and how to recover if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing direct commands and configuration examples without explaining what email, IMAP, or CLI concepts are. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Fully executable commands throughout with copy-paste ready examples. The configuration TOML is complete, and every operation includes the exact command syntax with realistic arguments. | 3 / 3 |
Workflow Clarity | Operations are clearly listed but lack validation checkpoints. For example, after configuration setup there's no verification step to confirm the account works, and delete operations have no confirmation or recovery guidance. | 2 / 3 |
Progressive Disclosure | Clear structure with quick reference to external files (configuration.md, message-composition.md) at the top. Content is well-organized into logical sections with appropriate depth for a skill overview. | 3 / 3 |
Total | 11 / 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 | |
- 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.