himalaya

Manage IMAP and SMTP email accounts from the terminal using the Himalaya CLI.

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/agtktID/indagis-agent --skill himalaya-agtktid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: himalaya
Source: https://github.com/agtktID/indagis-agent/tree/main/skills/email/himalaya
Command: npx skills add https://github.com/agtktID/indagis-agent --skill himalaya-agtktid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reading, searching, and sending email normally requires a GUI client or custom API integration; this Skill lets an agent operate a full mailbox directly from the terminal using the Himalaya CLI over standard IMAP/SMTP protocols. ## Core Features & Use Cases - Mailbox Operations: List folders and envelopes, search messages, read or export raw MIME, move, copy, delete, and manage flags across multiple accounts. - Non-Interactive Composition: Send, reply, and forward emails by piping MML templates via stdin, with support for HTML parts, attachments, and inline images. - Provider Configuration: Set up IMAP/SMTP accounts for Gmail, iCloud, and generic providers with secure password handling via pass, keyring, or OAuth2. - Use Case: Ask the agent to check your inbox for a message from a specific sender, read it, and send a reply with an attached PDF report — all without leaving the terminal. ## Quick Start Use the himalaya skill to list the ten most recent emails in my inbox and read the one from my manager.

Frequently Asked Questions about himalaya

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

FAQPage Schema
How do I send an email from the command line with himalaya?▼

Pipe a message with headers and body via stdin to himalaya template send, for example using a heredoc with From, To, and Subject headers. This non-interactive approach avoids opening an editor and works reliably from scripts and agents.

How to configure himalaya for Gmail IMAP and SMTP?▼

Create a config.toml account with imap.gmail.com:993 and smtp.gmail.com:587, using an app password if 2FA is enabled. You must also set folder.aliases mapping sent to [Gmail]/Sent Mail, otherwise saving sent messages fails after delivery.

Does himalaya support multiple email accounts?▼

Yes, define multiple [accounts.NAME] sections in config.toml and mark one as default. Switch between them at runtime with the --account flag, for example himalaya --account work envelope list.

Why does himalaya message send fail on Gmail after the email is delivered?▼

This happens when folder aliases use the old singular [accounts.NAME.folder.alias] syntax, which v1.2.0 silently ignores. Save-to-Sent then fails after SMTP succeeds, and retrying sends duplicates. Use the plural folder.aliases.X dotted keys instead.

Can himalaya add attachments to outgoing emails?▼

Yes, compose the message in MML syntax and include parts like <#part filename=/path/to/file.pdf><#/part> in the body. Himalaya compiles MML into proper MIME multipart messages when sending via himalaya template send.