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

73%

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

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 that clearly identifies the tool (himalaya), its domain (CLI email management), and lists comprehensive specific actions. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical specificity and unique tool name make it highly distinctive.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about managing 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 actions described.	2 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'emails', 'IMAP', 'SMTP', 'terminal', 'himalaya', 'reply', 'forward', 'search', plus the tool name itself. Covers common email-related actions and the CLI context well.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific tool name 'himalaya', the CLI/terminal context, IMAP/SMTP protocols, and MML. Unlikely to conflict with other skills as it occupies a very clear niche of terminal-based email management.	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, actionable reference for the Himalaya CLI with excellent concrete examples covering all major operations. Its main weaknesses are the lack of workflow sequencing with validation checkpoints (e.g., verifying config before sending) and some content that would be better placed in the referenced files rather than inline. The skill reads more like a command reference card than a guided workflow.

Suggestions

Add a validation workflow after configuration: e.g., run `himalaya account check` or `himalaya envelope list` to verify connectivity before proceeding to other operations, with error recovery guidance.

Move the full config.toml example to `references/configuration.md` and keep only a brief mention or minimal example in the main skill to improve conciseness and progressive disclosure.

Add a brief 'typical workflow' section showing a sequenced multi-step process (e.g., search → read → reply → verify sent) with explicit checkpoints.

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 notes 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	Individual commands are clear, but there's no sequenced workflow for common multi-step tasks (e.g., setup → verify → use). The prerequisites section lists requirements but doesn't include validation steps like verifying the config works before proceeding to email operations. No feedback loops for error recovery.	2 / 3
Progressive Disclosure	References to configuration.md and message-composition.md are well-signaled, but the main file includes a full configuration example that arguably belongs in the referenced configuration.md. The skill is somewhat long (~150 lines) with content that could be better distributed across reference files.	2 / 3
	Total	9 / 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: 0c1ec2b

Reviewed: about 2 hours 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.