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

73%

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%

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

Highly actionable command reference undermined by duplicated config content, a broken reference path, and missing validation checkpoints around destructive operations.

Suggestions

Remove the inline config.toml block from the body and point to references/configuration.md to eliminate duplication and respect token budget.

Fix or remove the references/message-composition.md citation — that file does not exist in the bundle, so the reference is broken.

Add a validation/confirmation step before destructive commands (e.g. re-list the message or confirm the ID before `message delete`/`message move`) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference, but the full config.toml block is duplicated between the body and references/configuration.md, and the inline smtplib script repeats something Claude already knows — both could be tightened.	2 / 3
Actionability	Concrete, copy-paste-ready bash commands throughout plus a complete executable Python attachment example, matching the level-3 anchor rather than the pseudocode level-2 anchor.	3 / 3
Workflow Clarity	Sequences like the template write\|send pipeline are present, but destructive operations (message delete, message move) have no validation/confirmation checkpoints, capping this at 2 per the rubric guidance.	2 / 3
Progressive Disclosure	One reference is signaled clearly, but the body cites references/message-composition.md which does not exist in the bundle, and config content is inline-duplicated instead of split out — structure is present but not cleanly organized.	2 / 3
	Total	9 / 12 Passed

Description

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.

A specific, action-rich description with strong trigger terms and a clear niche, held back only by the absence of an explicit "Use when..." trigger clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to manage, read, reply to, or send email from the terminal, or mentions himalaya/IMAP/SMTP."

Consider dropping the parenthetical "(MIME Meta Language)" gloss, which is jargon users rarely say and dilutes the natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "list, read, write, reply, forward, search, and organize emails" — matching the level-3 anchor for several specific actions rather than the level-2 single-domain anchor.	3 / 3
Completeness	Clearly states what the skill does but lacks any "Use when..." or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural verbs users would say ("read", "reply", "forward", "search emails") are well covered; not level 2 because it goes beyond a single generic keyword into the full set of common email verbs.	3 / 3
Distinctiveness Conflict Risk	"CLI to manage emails via IMAP/SMTP" with the himalaya binary and MML note carves a clear email-CLI niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: ce79d60

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