himalaya

Manage IMAP/SMTP email from the terminal with JSON output.

Updated May 26, 2026
One-click install
npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill himalaya-ruiyangruiyi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: himalaya
Source: https://github.com/ruiyangruiyi/hermes-agent/tree/main/skills/email/himalaya
Command: npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill himalaya-ruiyangruiyi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of reading, searching, composing, and sending emails by letting you do everything through a terminal interface instead of a full email client UI.

Core Features & Use Cases

  • Terminal email operations (IMAP/SMTP): List folders and envelopes, search by sender/subject/body terms, read messages, and move/copy/delete emails.
  • CLI composition and sending via templates: Reply and forward using templates, or compose new messages from piped input for reliable automation.
  • Structured output and automation-friendly workflow: Supports JSON output for programmatic parsing and uses an interactive configuration wizard to set up authentication and folder aliases.

Use case example: You want to quickly triage today’s inbox messages, search for a specific topic, then draft and send a reply from within your workflow using non-interactive stdin-based composition.

Quick Start

Set up your IMAP/SMTP account by running the interactive wizard so Hermes can send and read emails reliably through Himalaya.

Frequently Asked Questions about himalaya

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage IMAP and SMTP emails directly from the terminal?

Terminal email management handles IMAP and SMTP protocols to list folders, search messages, read content, and compose replies. It requires a valid config.toml file with correct credentials and folder aliases mappings for your provider.

Can I automate email triage and output structured JSON from the CLI?

Automated email triage supports scheduled workflows and programmatic metadata parsing using JSON output. You can pipe non-interactive stdin input to compose messages, search by sender or subject, and process envelopes without a full email client UI.

What do I need to configure before sending and reading emails through a terminal CLI?

Configuration requires running an interactive wizard to set up IMAP and SMTP authentication in a config.toml file. You must define correct folder.aliases mappings, especially for providers like Gmail, to ensure reliable reading and sending operations.

How do I reply to or forward emails using templates in a terminal workflow?

CLI composition allows replying and forwarding emails using predefined templates. You can also compose new messages from piped stdin input, enabling reliable automation for sending messages directly within your terminal workflow.

Does terminal email management work with Gmail and other IMAP providers?

Terminal email management supports Gmail and other IMAP providers when configured with correct folder.aliases mappings in the config.toml file. The interactive setup wizard helps establish authentication and folder mappings for reliable provider integration.

What are the limitations of using a CLI for email instead of a full email client?

CLI email management lacks a graphical interface, relying entirely on terminal commands and a config.toml file for setup. While it enables fast triage and JSON automation, interactive reading and composition require terminal familiarity and manual configuration.