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

70%

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 ./src/qwenpaw/agents/skills/himalaya-en/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.

Highly actionable command reference with broad coverage, but it lacks validation checkpoints around destructive operations and ships a broken reference to a non-existent message-composition.md. Tightening redundant prose and fixing the reference would meaningfully raise quality.

Suggestions

Add validation/verification guidance before destructive commands (e.g., confirm the message ID via 'himalaya envelope list' before 'message delete', or note irreversibility) to lift workflow clarity above 3.

Either create references/message-composition.md or remove the citation in the Tips section; if kept, list it in the References section so all references are surfaced in one place.

Trim the redundant opening sentence and rephrase 'If meet with error, try:' into clear guidance to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening sentence ('Himalaya is a CLI email client that lets you manage emails from the terminal...') restates the description, and awkward prose like 'If meet with error, try:' could be tightened.	3 / 5
Actionability	Provides copy-paste-ready commands and a complete Python snippet covering list, read, send, search, move, delete, flags, attachments, and debugging — fully executable across common cases.	5 / 5
Workflow Clarity	Destructive and batch operations ('message delete', 'message move', 'message copy') are documented without validation or verification checkpoints, which caps workflow clarity at 3 per the destructive-operations guidance.	3 / 5
Progressive Disclosure	A References section signals references/configuration.md (a real file), but references/message-composition.md is cited in the Tips section and does not exist in the bundle, so references are incomplete and not clearly surfaced.	3 / 5
	Total	14 / 20 Passed

Description

75%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, well-scoped description with strong action coverage and distinctiveness, but it lacks an explicit 'when to use' trigger clause, which caps completeness. Adding a 'Use when...' sentence would raise it to a top-tier description.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to manage, send, read, or search emails from the terminal' to satisfy the completeness 'when' requirement.

Include common synonyms like 'inbox', 'send mail', or '.eml' to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'list, read, write, reply, forward, search, and organize emails' — giving comprehensive coverage of the tool's capabilities.	5 / 5
Completeness	The 'what' is clearly stated ('CLI to manage emails... list, read, write...') but there is no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Includes natural terms like 'emails', 'IMAP/SMTP', and 'terminal', but misses common synonyms users might say such as 'inbox', 'send mail', or file/protocol extensions.	4 / 5
Distinctiveness Conflict Risk	Names a specific tool (himalaya) and a narrow domain (terminal email via IMAP/SMTP), creating a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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: agentscope-ai/QwenPaw
Path: src/qwenpaw/agents/skills/himalaya-en/SKILL.md
Commit: bacac74

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