himalaya – Marketing & SEO skill for AI agents
Himalaya CLI: IMAP/SMTP email from terminal.
Install the himalaya skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/himalaya-666ad.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /himalaya – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/himalaya-666ad.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $himalaya – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/himalaya-666ad.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /himalaya – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/himalaya-666ad.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /himalaya – then describe the task you want done.
SKILL.md content
Himalaya Email CLI
Himalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.
This skill is separate from the Hermes Email gateway adapter. The gateway
adapter lets people email the agent and uses Hermes' built-in IMAP/SMTP
adapter; this skill lets the agent operate a mailbox from terminal tools and
requires the external himalaya CLI.
References
references/configuration.md(config file setup + IMAP/SMTP authentication)references/message-composition.md(MML syntax for composing emails)
Prerequisites
1. Himalaya CLI installed (himalaya --version to verify)
2. A configuration file at ~/.config/himalaya/config.toml
3. IMAP/SMTP credentials configured (password stored securely)
Installation
# Pre-built binary (Linux/macOS — 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 --lockedConfiguration Setup
Run the interactive wizard to set up an account:
himalaya account configureOr create ~/.config/himalaya/config.toml manually:
[accounts.personal]
email = "[email protected]"
display-name = "Your Name"
default = true
backend.type = "imap"
backend.host = "imap.example.com"
backend.port = 993
backend.encryption.type = "tls"
backend.login = "[email protected]"
backend.auth.type = "password"
backend.auth.cmd = "pass show email/imap" # or use keyring
message.send.backend.type = "smtp"
message.send.backend.host = "smtp.example.com"
message.send.backend.port = 587
message.send.backend.encryption.type = "start-tls"
message.send.backend.login = "[email protected]"
message.send.backend.auth.type = "password"
message.send.backend.auth.cmd = "pass show email/smtp"
# Folder aliases (himalaya v1.2.0+ syntax). Required whenever the
# server's folder names don't match himalaya's canonical names
# (inbox/sent/drafts/trash). Gmail is the common case — see
# `references/configuration.md` for the `[Gmail]/Sent Mail` mapping.
folder.aliases.inbox = "INBOX"
folder.aliases.sent = "Sent"
folder.aliases.drafts = "Drafts"
folder.aliases.trash = "Trash"> Heads up on the alias syntax. 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]).
Hermes Integration Notes
- Reading, listing, searching, moving, deleting all work directly through the terminal tool
- Composing/replying/forwarding — piped input (
cat << EOF | himalaya template send) is recommended for reliability. Interactive$EDITORmode works withpty=true+ background + process tool, but requires knowing the editor and its commands - Use
--output jsonfor structured output that's easier to parse programmatically - The
himalaya account configurewizard requires interactive input — use PTY mode:terminal(command="himalaya account configure", pty=true)
Common Operations
List Folders
himalaya folder listList Emails
List emails in INBOX (default):
himalaya envelope listList emails in a specific folder:
himalaya envelope list --folder "Sent"List with pagination:
himalaya envelope list --page 1 --page-size 20Search Emails
himalaya envelope list from [email protected] subject meetingRead an Email
Read email by ID (shows plain text):
himalaya message read 42Export raw MIME:
himalaya message export 42 --fullReply to an Email
To reply non-interactively from Hermes, read the original message, compose a reply, and pipe it:
# Get the reply template, edit it, and send
himalaya template reply 42 | sed 's/^$/\nYour reply text here\n/' | himalaya template sendOr build the reply manually:
cat << 'EOF' | himalaya template send
From: [email protected]
To: [email protected]
Subject: Re: Original Subject
In-Reply-To: <original-message-id>
Your reply here.
EOFReply-all (interactive — needs $EDITOR, use template approach above instead):
himalaya message reply 42 --allForward an Email
# Get forward template and pipe with modifications
himalaya template forward 42 | sed 's/^To:.*/To: [email protected]/' | himalaya template sendWrite a New Email
Non-interactive (use this from Hermes) — pipe the message via stdin:
cat << 'EOF' | himalaya template send
From: [email protected]
To: [email protected]
Subject: Test Message
Hello from Himalaya!
EOFOr with headers flag:
himalaya message write -H "To:[email protected]" -H "Subject:Test" "Message body here"Note: himalaya message write without piped input opens $EDITOR. This works with pty=true + background mode, but piping is simpler and more reliable.
Move/Copy Emails
Move to folder (target folder comes first, then the message ID):
himalaya message move "Archive" 42Copy to folder (target folder comes first, then the message ID):
himalaya message copy "Important" 42Delete an Email
himalaya message delete 42Manage Flags
Add flag:
himalaya flag add 42 --flag seenRemove flag:
himalaya flag remove 42 --flag seenMultiple Accounts
List accounts:
himalaya account listUse a specific account:
himalaya --account work envelope listAttachments
Save attachments from a message:
himalaya attachment download 42Save to specific directory:
himalaya attachment download 42 --downloads-dir ~/DownloadsOutput Formats
Most commands support --output for structured output:
himalaya envelope list --output json
himalaya envelope list --output plainDebugging
Enable debug logging:
RUST_LOG=debug himalaya envelope listFull trace with backtrace:
RUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope listTips
- Use
himalaya --helporhimalaya <command> --helpfor detailed usage. - Message IDs are relative to the current folder; re-list after folder changes.
- For composing rich emails with attachments, use MML syntax (see
references/message-composition.md). - Store passwords securely using
pass, system keyring, or a command that outputs the password.
Related skills
- cro-review – /c-level-agents:cro-review [plan] — Pipeline-paranoid interrogation of revenue, win…
- networkx – Creates, analyzes, and visualizes complex networks and graphs in Python with NetworkX…
- reverse-engineer-marketing – When the user wants to reverse engineer how another company grew and copy what worked…
- customer-success-manager – Monitors customer health, predicts churn risk, and identifies expansion opportunities…
- revops – When the user wants help with revenue operations, lead lifecycle management, or…
- nwb-conversion – Converts neuroscience acquisition data to Neurodata Without Borders files with NeuroConv…
- deal-desk – Use when reviewing a specific inbound deal before close — when sales has asked for a…
- sales-enablement – When the user wants to create sales collateral, pitch decks, one-pagers, objection…