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

75%

Does it follow best practices?

Impact

93%

1.69x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/himalaya/SKILL.md

The canonical home for this skill is himalaya in Hung-Reo/hungreo-openclaw

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, well-organized command reference with properly split one-level-deep reference files. Its main weakness is the absence of validation/confirmation steps around destructive operations, which limits workflow clarity.

Suggestions

Add validation or confirmation guidance for destructive operations, e.g. note that 'message delete' is permanent and advise verifying the ID via 'message read' first, or confirm the target folder exists before 'message move'.

Add a brief verification step after configuration setup, such as running 'himalaya account list' or 'himalaya envelope list' to confirm credentials work before further operations.

Link to the relevant reference file at the point of use (e.g., point to references/configuration.md in the Configuration Setup section) rather than only in the Tips section.

Dimension	Reasoning	Score
Conciseness	A lean command cheat-sheet with brief labels and executable snippets; minor redundancies (e.g., 'List Emails' header plus 'List emails in INBOX (default)') could be trimmed, but it does not over-explain concepts Claude already knows.	4 / 5
Actionability	Fully executable, copy-paste-ready commands across all common operations, plus a complete TOML configuration example covering both backend and send backend.	5 / 5
Workflow Clarity	Destructive operations ('message delete', 'message move') are presented without any validation or confirmation step; per the rubric, missing validation for destructive operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Two real one-level-deep reference files (configuration.md, message-composition.md) are clearly signaled in a References section with descriptions, and the body is well-organized with clear headers; minor gap is that inline references are mostly relegated to the Tips section rather than placed at the relevant operations.	4 / 5
	Total	16 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, listing many concrete email actions, but lacks an explicit 'Use when...' trigger clause and omits common synonyms like 'mail' and 'inbox'. Adding explicit trigger guidance would raise completeness and trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to manage, read, send, reply, forward, search, or organize emails from the terminal, or mentions himalaya, IMAP/SMTP, or CLI email workflows.'

Include natural synonyms such as 'mail' and 'inbox' alongside 'emails' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists seven concrete actions (list, read, write, reply, forward, search, organize) plus multiple-account support and MML composition, giving comprehensive coverage of the tool's capabilities.	5 / 5
Completeness	Clearly states what the skill does, but provides no explicit 'Use when...' trigger clause; per the rubric guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes the natural term 'emails' and common verbs users would say, but misses synonyms like 'mail' or 'inbox' and leans on technical jargon (IMAP/SMTP, MML).	4 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche (terminal email management via himalaya) with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 13 / 16 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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/himalaya/SKILL.md
Commit: ba4a78e

Reviewed: 1 day 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.