Himalaya
Himalaya CLI for IMAP/SMTP mail: list, read, search, compose, reply, forward, copy, move, delete.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Himalaya when an AI agent needs a reusable SKILL.md workflow for this job: Himalaya CLI for IMAP/SMTP mail: list, read, search, compose, reply, forward, copy, move, delete.
When not to use it
Skip Himalaya when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/himalaya # Save SKILL.md to ~/.claude/skills/himalaya/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/himalaya/SKILL.md. For a shared project, commit the folder at .claude/skills/himalaya/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Himalaya skill for this task: Use Himalaya when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 69/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Himalaya
Use `himalaya` for IMAP/SMTP email from shell.
## References
- `references/configuration.md`: account config, auth, backend setup. - `references/message-composition.md`: MML compose syntax.
## Setup
```bash himalaya --version himalaya account configure ```
Config path: `~/.config/himalaya/config.toml`.
Prefer password managers/keyrings for credentials; do not paste secrets into chat/logs.
## Read/search
```bash himalaya folder list himalaya envelope list himalaya message read <id> himalaya envelope list from [email protected] subject invoice ```
## Write
```bash himalaya message write himalaya template write himalaya template send < /tmp/message.txt himalaya message reply <id> himalaya message forward <id> ```
Use MML for attachments and rich messages; read `references/message-composition.md` first.
## Organize
```bash himalaya message copy <id> --to <folder> himalaya message move <id> --to <folder> himalaya message delete <id> himalaya flag add <id> --flag seen himalaya flag remove <id> --flag seen ```
## Notes
- Use `--account` when multiple accounts exist. - Quote exact message IDs in summaries.
Intended uses
- Use Himalaya when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.