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 per the rubric caps completeness at 2. Adding trigger guidance would make this description excellent.
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 to interact with IMAP/SMTP mailboxes.'
| 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', 'terminal', 'himalaya', 'reply', 'forward', 'search', plus the tool name itself. Users asking about email from the CLI would naturally use these terms. | 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 CLI reference skill with excellent actionability—every command is concrete and executable. Its main weaknesses are that it inlines too much content (especially the full config example) that belongs in the referenced files, and it lacks validation steps after setup. The content would benefit from being leaner in the main file with more delegation to references.
Suggestions
Move the full config.toml example to references/configuration.md and keep only the wizard command (`himalaya account configure`) plus a brief note about manual config in the main skill.
Add a validation step after configuration setup, e.g., 'Verify connection: `himalaya account check` or `himalaya envelope list` to confirm IMAP access works.'
Consider moving the Debugging and Output Formats sections to a reference file to keep the main skill focused on core operations.
| 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 parenthetical explanations add minor bloat. | 2 / 3 |
Actionability | Every operation includes fully executable, copy-paste-ready bash commands with realistic arguments. The configuration example is complete with actual TOML syntax, and commands cover the full range of email operations with specific flags and options. | 3 / 3 |
Workflow Clarity | The prerequisites and configuration setup provide a reasonable sequence, but there's no validation checkpoint after configuration (e.g., 'test connection with himalaya account check' or similar). The operations are presented as independent commands rather than workflows, which is appropriate for a CLI reference, but the initial setup flow lacks explicit verification steps. | 2 / 3 |
Progressive Disclosure | References to configuration.md and message-composition.md are clearly signaled at the top, but the full configuration TOML example is inlined rather than being in the referenced configuration.md. The SKILL.md is quite long (~150 lines) with content that could be better distributed across 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
af8bd5f
- 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.