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
Quality
77%
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
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 exactly 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 variations like 'mail', 'inbox', 'send email', 'check messages' alongside the technical terms.
| 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' with detailed capabilities, but lacks an explicit 'Use when...' clause. The 'when' is only implied through the action verbs and context, not explicitly stated. | 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 | Highly distinctive with specific tool name 'himalaya', CLI/terminal context, and IMAP/SMTP protocols. Unlikely to conflict with other skills due to the specific email client and command-line focus. | 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 CLI reference skill that excels in conciseness and actionability, providing comprehensive coverage of himalaya commands with executable examples. The main weakness is the lack of validation checkpoints, particularly after configuration setup and before destructive operations like delete. The progressive disclosure is appropriate with clear references to supplementary documentation.
Suggestions
Add a verification step after configuration setup (e.g., 'Verify connection: `himalaya account check` or `himalaya envelope list` to confirm credentials work')
Include a note about delete behavior (whether it moves to trash or permanently deletes) and any recovery options
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing direct commands without explaining what email or IMAP is. Every section delivers actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Fully executable commands throughout with copy-paste ready examples. The configuration file example 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 well-signaled references to configuration.md and message-composition.md for advanced topics. The main file serves as a comprehensive quick reference while pointing to detailed materials for complex topics like MML syntax. | 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.