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

—

Does it follow best practices?

Impact

93%

1.69x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

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

A well-structured, highly actionable command reference with clean progressive disclosure, held back only by absent validation guidance around destructive email operations.

Suggestions

Add verification/feedback steps for destructive and batch operations (e.g., confirm before `message delete`, suggest `envelope list` after `message move` to verify the result).

Reduce duplication between the inline Configuration Setup block and references/configuration.md by keeping a minimal example in the body and deferring the full IMAP/SMTP block to the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-focused with no concept explanations Claude already knows; brief annotations like 'Interactive reply (opens $EDITOR)' earn their place rather than padding.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands (`himalaya message read 42`, `himalaya message reply 42 --all`) plus a complete heredoc template-send example and a working config.toml snippet.	3 / 3
Workflow Clarity	Prerequisites include a verify step (`himalaya --version`) and config setup is sequenced, but destructive operations (delete, move) and batch flag changes lack validation/feedback-loop checkpoints, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	A clearly signaled, one-level-deep References section points to two real files (configuration.md, message-composition.md) with parenthetical descriptions, and the body stays an overview rather than nesting references.	3 / 3
	Total	11 / 12 Passed

Description

72%

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, well-targeted description with strong trigger terms and a clear niche, weakened only by missing explicit 'when to use' guidance and a second-person imperative clause.

Suggestions

Add an explicit 'Use when ...' clause stating when Claude should invoke this skill (e.g., 'Use when the user needs to manage, read, send, or search emails from the terminal').

Rephrase 'Use `himalaya` to list, read, write...' in third person (e.g., 'Manages emails via the himalaya CLI: list, read, write...') to align with the expected voice.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('list, read, write, reply, forward, search, and organize emails') matching the anchor-3 example, but the imperative 'Use `himalaya` to...' is second-person voice, which the guidelines penalize by reducing specificity by one.	2 / 3
Completeness	It clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, so per the guidelines completeness is capped at 2 with 'when' only implied.	2 / 3
Trigger Term Quality	It uses natural terms users would actually say ('manage emails', 'read', 'reply', 'forward', 'search emails', 'multiple accounts'), giving good coverage rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	The email-CLI niche is clearly scoped via the named tool `himalaya` and IMAP/SMTP context, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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
Commit: dfab3c6

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