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).

1.69x

Quality

77%

Does it follow best practices?

Impact

93%

1.69x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/himalaya/SKILL.md

Quality

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 limits its completeness score, and could benefit from more natural trigger terms users might actually say when needing 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', 'email client' to improve discoverability.

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 messages'.	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 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 CLI skill that provides comprehensive, actionable guidance for using Himalaya. The content is concise, assumes Claude's competence, and offers executable examples throughout. The main weakness is the lack of validation steps after configuration and no guidance on error recovery for destructive operations like delete.

Suggestions

Add a verification step after configuration setup (e.g., 'Test connection: `himalaya envelope list` - if this fails, check credentials and server settings')

Include a note about delete behavior (trash vs permanent) and how to recover if needed

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 shows 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 a concise overview and well-signaled references to detailed materials (configuration.md, message-composition.md). Content is appropriately organized into logical sections without being monolithic.	3 / 3
	Total	11 / 12 Passed

Validation

72%

Warnings & errors only

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: 50ef2f3

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.