himalaya

Himalaya CLI: IMAP/SMTP email from terminal.

Quality

62%

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 ./skills/email/himalaya/SKILL.md

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 well-organized, highly actionable command reference: nearly every section is executable copy-paste code with agent-specific guidance (PTY notes, JSON output, piping vs $EDITOR). Main gaps are the absent validation checkpoints around destructive operations (delete/move) and duplication between the inline configuration walkthrough and references/configuration.md.

Suggestions

Add validation checkpoints before destructive/batch operations — e.g. 'Read the message (himalaya message read <id>) to confirm the right ID before deleting' and verify folder names with 'himalaya folder list' before move/copy — which would lift workflow_clarity above the destructive-operation cap of 3.

Trim the inline config.toml to a minimal quick-start stub and delegate the full example, alias warning, and provider configs to references/configuration.md to remove the near-verbatim duplication.

Cut the opening paragraph that restates the frontmatter description, keeping only the Hermes-gateway disambiguation sentence.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste command blocks, and prose sections carry non-obvious, high-value information (Hermes disambiguation, the v1.2.0 alias pitfall, argument ordering). However, the full config.toml block and the ~10-line alias warning are duplicated nearly verbatim in references/configuration.md, and the opening paragraph repeats the frontmatter — matching anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed'). Not anchor 5 because that duplication could be trimmed; not anchor 3 because there is no padding or explanation of concepts Claude already knows.	4 / 5
Actionability	Every section provides fully executable, copy-paste-ready commands covering the common cases: installation (three routes), configuration, list/search/read, reply/forward/compose (both piped and interactive), move/copy/delete, flags, attachments, multiple accounts, output formats, and debugging. This matches anchor 5 ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases').	5 / 5
Workflow Clarity	The setup sequence is clear (verify install → configure account → credentials), but the skill's destructive operations ('himalaya message delete 42', 'himalaya message move') and send have no validation checkpoints — no confirm-the-ID-before-delete step and no post-operation verification. Per the judging guidelines, missing validation for destructive/batch operations caps workflow clarity at 3 ('Steps listed but validation gaps; sequence present but checkpoints missing or implicit').	3 / 5
Progressive Disclosure	A dedicated References section lists both bundle files with a parenthetical of what each covers, both referenced paths exist (references/configuration.md, references/message-composition.md), they are one level deep, and they are cross-linked inline (config comment and Tips). Minor organization gap: the Configuration Setup section duplicates a full config.toml and the alias warning already detailed in references/configuration.md — matching anchor 4 ('Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'). Not anchor 5 because content is not cleanly split — the duplication blurs the overview/reference boundary.	4 / 5
	Total	16 / 20 Passed

Description

48%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 precisely identifies the tool (Himalaya CLI, IMAP/SMTP, terminal email) but says nothing about what it does or when to use it — no action verbs, no 'Use when...' clause, and no natural user phrasings like 'send email' or 'check inbox'. It is distinct by naming a niche tool, yet thin on capabilities and triggers.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to send, read, reply to, or search emails from the terminal or mentions their inbox or mailbox.'

List 2-4 concrete actions (send, read/reply, search envelopes, manage folders and flags) so the description conveys capabilities, not just tool identity.

Include natural synonyms users would say — 'email', 'inbox', 'mailbox', 'command line' — to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the exact tool and domain ("Himalaya CLI: IMAP/SMTP email from terminal") but contains no action verbs at all — no send, read, reply, or manage — matching anchor 2 ('Names the domain but actions are minimal or generic'). Not anchor 1 since it is specific rather than vague/abstract, and not anchor 3 since it never lists even 1-2 concrete actions.	2 / 5
Completeness	The 'what' is present at tool-identity level (CLI email via IMAP/SMTP from terminal), but the 'when' is entirely missing — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not anchor 2 because the 'what' is not vague.	3 / 5
Trigger Term Quality	Includes relevant keywords ('email', 'IMAP', 'SMTP', 'CLI', 'terminal') but misses the natural phrases users would say: 'send email', 'read/check email', 'inbox', 'mailbox', 'command line' — matching anchor 3 (some relevant keywords, missing common variations or synonyms). Not anchor 4 because everyday verb-based trigger phrases are absent.	3 / 5
Distinctiveness Conflict Risk	Naming the specific tool 'Himalaya CLI' gives a clear niche with minimal generic conflict, but the description includes no disambiguating triggers and the skill body itself acknowledges a closely related skill (the Hermes email gateway adapter) that the description does not distinguish from — matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'). Not anchor 5 because there are no distinct trigger phrases to lock in the niche.	4 / 5
	Total	12 / 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: NousResearch/hermes-agent
Path: skills/email/himalaya/SKILL.md
Commit: 68fa7e9

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