菜单
Operates IMAP/SMTP mailboxes from the terminal with the Himalaya CLI (list, search, compose, reply, flags, attachments, JSON). Use when reading or sending mail non-interactively via himalaya. Not for Resend/React Email app integration (email) and not a Hermes inbound email gateway.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Kayforkind/skill-slice --skill himalaya命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | himalaya |
| description | Operates IMAP/SMTP mailboxes from the terminal with the Himalaya CLI (list, search, compose, reply, flags, attachments, JSON). Use when reading or sending mail non-interactively via himalaya. Not for Resend/React Email app integration (email) and not a Hermes inbound email gateway. |
| version | 1.1.1 |
| author | community |
| license | MIT |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["Email","IMAP","SMTP","CLI","Communication"],"homepage":"https://github.com/pimalaya/himalaya"}} |
| prerequisites | {"commands":["himalaya"]} |
Himalaya is a CLI email client that manages email from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends. This skill is separate from any Hermes Email gateway adapter — it operates a mailbox directly through the external himalaya CLI.
himalaya --version.~/.config/himalaya/config.toml (Windows: %USERPROFILE%\.config\himalaya\config.toml).pass, system keyring, or a command that outputs the password).# Windows (PowerShell) — via cargo (requires Rust toolchain)
cargo install himalaya --locked
# Or download pre-built binary from GitHub releases
# https://github.com/pimalaya/himalaya/releases
# Linux/macOS — pre-built binary (recommended)
curl -sSL https://raw.githubusercontent.com/pimalaya/himalaya/master/install.sh | PREFIX=~/.local sh
# macOS via Homebrew
brew install himalaya
# Or via cargo (any platform with Rust)
cargo install himalaya --locked
Run the interactive wizard (requires PTY mode in agent environments):
himalaya account configure
Or create ~/.config/himalaya/config.toml manually:
[accounts.personal]
email = "you@example.com"
display-name = "Your Name"
default = true
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
Load
references/configuration.mdwhen setting up a new account, troubleshooting authentication, or configuring folder aliases for non-standard providers (Gmail, Fastmail, etc.).
himalaya folder list
# List emails in INBOX (default)
himalaya envelope list
# List emails in a specific folder
himalaya envelope list --folder "Sent"
# List with pagination
himalaya envelope list --page 1 --page-size 20
himalaya envelope list from john@example.com subject meeting
# Read email by ID (shows plain text)
himalaya message read 42
# Export raw MIME
himalaya message export 42 --full
Always pipe via stdin from agent environments — this is the reliable path:
cat << 'EOF' | himalaya template send
From: you@example.com
To: recipient@example.com
Subject: Test Message
Hello from Himalaya!
EOF
Alternative with headers flag:
himalaya message write -H "To:recipient@example.com" -H "Subject:Test" "Message body here"
Load
references/message-composition.mdwhen composing rich emails with attachments, multipart MIME, or advanced MML syntax.
# Get the reply template, edit it, and send
himalaya template reply 42 | sed 's/^$/\nYour reply text here\n/' | himalaya template send
Or build the reply manually with proper headers:
cat << 'EOF' | himalaya template send
From: you@example.com
To: sender@example.com
Subject: Re: Original Subject
In-Reply-To: <original-message-id>
Your reply here.
EOF
Reply-all (interactive — needs $EDITOR, use template approach above instead for agent use):
himalaya message reply 42 --all
# Get forward template and pipe with modifications
himalaya template forward 42 | sed 's/^To:.*/To: newrecipient@example.com/' | himalaya template send
# Move to folder (target folder comes first, then the message ID)
himalaya message move "Archive" 42
# Copy to folder (target folder comes first, then the message ID)
himalaya message copy "Important" 42
himalaya message delete 42
# Add flag
himalaya flag add 42 --flag seen
# Remove flag
himalaya flag remove 42 --flag seen
# Save attachments from a message
himalaya attachment download 42
# Save to specific directory
himalaya attachment download 42 --downloads-dir ~/Downloads
# List accounts
himalaya account list
# Use a specific account
himalaya --account work envelope list
Most commands support --output for structured output — use json for programmatic parsing:
himalaya envelope list --output json
himalaya envelope list --output plain
# Enable debug logging
RUST_LOG=debug himalaya envelope list
# Full trace with backtrace
RUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope list
Pre-v1.2.0 docs used a [accounts.NAME.folder.alias] sub-section (singular alias). v1.2.0 silently ignores that form — TOML parses fine, but the alias resolver never reads it, so every lookup falls through to the canonical name.
On Gmail this means save-to-Sent fails after SMTP delivery succeeds, and himalaya message send exits non-zero. Any caller (agent, script, user) that retries on that exit code will re-run the entire send — including SMTP — producing duplicate emails to recipients.
Always use folder.aliases.X (plural, dotted keys, directly under [accounts.NAME]):
# CORRECT — v1.2.0+
folder.aliases.inbox = "INBOX"
folder.aliases.sent = "Sent"
# WRONG — silently ignored in v1.2.0+
# [accounts.personal.folder.alias]
# inbox = "INBOX"
himalaya message write and himalaya message reply without piped input open $EDITOR. This works with pty=true + background + process tool, but piping via stdin is simpler and more reliable in agent environments. Always prefer cat << 'EOF' | himalaya template send over interactive editor mode.
Message IDs are relative to the current folder. Always re-list envelopes after folder changes before operating on a message by ID.
himalaya account configure Requires Interactive InputThe wizard requires interactive input — use PTY mode: terminal(command="himalaya account configure", pty=true). In non-interactive agent environments, create config.toml manually instead.
Never hardcode passwords in config.toml. Use pass, system keyring, or a command that outputs the password via backend.auth.cmd.
Verify installation:
himalaya --version
Expected output: himalaya 1.x.x
Verify configuration is loaded:
himalaya account list
Expected: lists configured accounts with the default account marked.
Verify IMAP connectivity:
himalaya envelope list --page 1 --page-size 5
Expected: shows up to 5 envelopes from INBOX.
Verify SMTP by sending a test to yourself:
cat << 'EOF' | himalaya template send
From: you@example.com
To: you@example.com
Subject: Himalaya Test
This is a test message from Himalaya CLI.
EOF
Expected: command exits 0, message appears in INBOX.
Verify folder aliases (critical for Gmail):
himalaya folder list --output json
Confirm that aliased folders resolve correctly. Then send a test email and verify it appears in the Sent folder — if himalaya message send exits non-zero after successful SMTP delivery, your alias syntax is wrong (see Pitfalls).
