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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

65%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.

A highly actionable CLI reference with excellent copy-paste commands and honest documentation of known failure modes. It is held back by an inline config block duplicating the reference file, a broken reference to a nonexistent message-composition.md, and missing validation steps around destructive message operations.

Suggestions

Remove the ~50-line inline TOML example (it duplicates references/configuration.md) and replace it with a one-line pointer plus the wizard command.

Fix or remove the reference to references/message-composition.md in the Tips section, since that file does not exist in the bundle.

Add verification guidance around destructive operations, e.g. confirm the envelope ID by re-listing before "message delete"/"message move", and note how to undo or check the destination folder afterward.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-focused content, but the ~50-line inline TOML config block substantially duplicates references/configuration.md and 163-mail-specific notes are scattered across three separate sections, so it could be noticeably tightened.	3 / 5
Actionability	Every operation ships copy-paste-ready commands, including the non-interactive pipeline "export EDITOR=cat; himalaya template write -H ... \| himalaya template send", a fully executable Python smtplib attachment example, and warnings quoting exact error messages ("cannot parse MML message: empty body").	5 / 5
Workflow Clarity	Prerequisites and a setup sequence are present with useful error-recovery notes, but destructive operations ("himalaya message delete 42", "himalaya message move 42") lack any validation or verification steps, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are well organized and references/configuration.md is a real one-level-deep reference, but the body cites references/message-composition.md which does not exist in the bundle, and configuration content that belongs in the reference file is duplicated inline in SKILL.md.	3 / 5
	Total	14 / 20 Passed

Description

71%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.

A specific, tool-named description with strong action coverage and good natural keywords. Its main weakness is the complete absence of a 'when to use this skill' trigger clause, which caps completeness, alongside slightly CLI-flavored vocabulary in place of natural user phrases.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to read, send, reply to, forward, or search emails from the terminal, or mentions himalaya, inbox, or IMAP/SMTP."

Replace or supplement the CLI verb "write" with the natural phrase "send email" so the description matches what users actually say.

Include a few common synonyms ("mail", "inbox", "email client") to strengthen trigger-term coverage toward the top anchor.

Dimension	Reasoning	Score
Specificity	"list, read, write, reply, forward, search, and organize emails" enumerates multiple concrete, specific actions with comprehensive coverage of email management operations, matching the top anchor rather than anchor 4's 'minor gaps in coverage'.	5 / 5
Completeness	The 'what' is explicit and concrete (list, read, write, reply, forward, search, organize; multiple accounts; MML composition), but there is no "Use when..." clause or equivalent trigger guidance — "Use `himalaya` to..." instructs how to use the tool, not when to invoke the skill, capping completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "emails", "reply", "forward", "search", and "terminal" are present, but "write" is CLI jargon where users would say "send email", and synonyms like "mail" or "inbox" are missing, so it falls short of comprehensive synonym/extension coverage.	4 / 5
Distinctiveness Conflict Risk	The named tool plus the IMAP/SMTP terminal-email niche is mostly distinct with only minor overlap risk against other mail-related skills, fitting anchor 4 rather than anchor 5's fully minimal conflict risk.	4 / 5
	Total	16 / 20 Passed

Validation

75%

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 — 12 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: ZHangZHengEric/Sage
Path: app/skills/himalaya/SKILL.md
Commit: 81bddde

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