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 ./openclaw/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 (himalaya), protocols (IMAP/SMTP), and a comprehensive list of actions. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The trigger terms are naturally varied and cover both user-facing actions and technical terminology.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about sending, reading, or managing emails from the command line, mentions himalaya, or needs IMAP/SMTP email operations.'
| 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 for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'emails', 'IMAP', 'SMTP', 'terminal', 'himalaya', 'reply', 'forward', 'search', plus technical terms like 'MML' and 'MIME Meta Language' that power users would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: CLI email management via himalaya specifically. The combination of terminal-based email, IMAP/SMTP, and the named tool 'himalaya' makes it highly 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. However, it's somewhat verbose for a SKILL.md overview, inlining detailed configuration that could be deferred to the referenced file. It also lacks workflow sequencing and validation checkpoints for destructive operations like delete and move.
Suggestions
Move the full config.toml example to references/configuration.md and keep only the wizard command (`himalaya account configure`) and a brief note in the main skill.
Add a verification step after setup (e.g., `himalaya envelope list` to confirm connection works) and after destructive operations (delete/move) to confirm success.
Add a brief 'typical workflow' section showing the sequence: configure → verify → list → read → reply, to give Claude a mental model of how operations chain together.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete commands, but includes some unnecessary elements like the full config file example (which could be referenced out) and explanatory phrases like 'Himalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends' that Claude doesn't need. The skill is somewhat long for what could be more tightly organized. | 2 / 3 |
Actionability | Nearly every section provides copy-paste ready commands with specific flags and arguments. The configuration example is complete and executable, commands include concrete IDs and folder names, and multiple approaches are shown (interactive vs piped template for sending). | 3 / 3 |
Workflow Clarity | Individual commands are clear, but there's no sequenced workflow for multi-step operations like 'set up account, verify connection, then use.' The delete operation has no confirmation/validation step, and there's no feedback loop for verifying that moves, sends, or deletes succeeded. | 2 / 3 |
Progressive Disclosure | References to configuration.md and message-composition.md are well-signaled at the top, but the main file includes a large inline configuration block that could live in the referenced configuration.md. The skill would benefit from keeping the overview leaner and pushing detailed config and advanced usage to reference 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
- trpc-group/trpc-agent-go
- Commit
fcc550d
- 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.