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

68%

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.

The content is highly actionable with comprehensive command examples, but suffers from a broken reference (message-composition.md), duplicated configuration content, and missing validation around destructive email operations.

Suggestions

Add validation/verification before destructive operations (e.g. confirm the folder exists and the ID is correct before `message delete`/`message move`, and verify the send succeeded after `template send`).

Create references/message-composition.md (cited in Tips) or remove the dangling reference, and move the inline IMAP/SMTP config block to references/configuration.md to avoid duplication.

Move the large inline Python smtplib attachment script into references/ (or a scripts/ file) and keep only a short pointer plus the key limitation note in the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples, but the large inline Python smtplib attachment block and the config block (duplicated with references/configuration.md) add padding that could be trimmed or offloaded.	3 / 5
Actionability	Abundant copy-paste-ready commands cover the common cases (list, search, read, send, move/copy, delete, flags, attachments, output formats) with specific flags and concrete examples, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Operations are clearly sequenced per task, but destructive/batch commands like `himalaya message delete 42` and `himalaya message move` have no validation or verification checkpoints, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	A References section signals references/configuration.md (a real one-level file), but the Tips section cites references/message-composition.md which does not exist, and the config block is inlined rather than deferred to the reference file.	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.

The description is specific and concrete with good trigger terms and a clear niche, but it lacks an explicit 'Use when...' trigger clause, capping completeness at 3. Adding explicit invocation triggers would raise the score.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when the user asks to read, send, reply to, search, or organize emails from the terminal.'

Include natural synonyms such as 'mail' alongside 'email' and mention common file extensions or contexts (e.g. attachments) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("list, read, write, reply, forward, search, and organize") plus concrete details (IMAP/SMTP, terminal, multiple accounts, MML), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Has a clear 'what' (CLI to manage emails via IMAP/SMTP with listed actions) but no explicit 'Use when...' trigger clause; 'when' is only weakly implied, so it is capped at 3 per the guidelines.	3 / 5
Trigger Term Quality	Good natural keywords ("read", "reply", "forward", "search", "emails") but missing common synonyms (mail/email interchange) and file-extension-style triggers, fitting the good-but-few-terms-missing anchor.	4 / 5
Distinctiveness Conflict Risk	Tied to the specific himalaya CLI with IMAP/SMTP and terminal framing gives a clear niche with minimal conflict risk, though it could still overlap with a generic email-sending skill.	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: f93356b

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.