agentleFS
Sign inStart free
NollisNollis/Skills/himalaya-email/SKILL.md

himalaya-email

Skill0 starsChanged 7 months agoMITView on GitHub

Manage email from the terminal with the Himalaya CLI. Use when listing folders, searching mail, reading messages, composing/replying/forwarding email, moving/deleting messages, or downloading attachments via IMAP/SMTP.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. phntm7/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user wants terminal-based email management and himalaya is available.

    line 8
  2. Very specific:

    If needed, run interactive setup once: himalaya account configure.

    line 14
  3. Very specific:

    Avoid $EDITOR-based flows unless explicitly requested.

    line 20
  4. Very specific:

    Prefer machine-readable output where possible: --output json.

    line 21
  5. Distinctive:

    Do not put credentials in plaintext outputs.

    line 112
  6. Distinctive:

    If SMTP/IMAP auth fails, verify auth command/keyring and account selection.

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Himalaya Email (Codex Skill)

Use this skill when the user wants terminal-based email management and himalaya is available.

Prerequisites

  1. Confirm CLI is installed: himalaya --version.
  2. Confirm at least one account exists: himalaya account list.
  3. If needed, run interactive setup once: himalaya account configure.

Execution Rules

  1. Prefer non-interactive workflows.
  2. For compose/reply/forward, pipe a full message to himalaya template send.
  3. Avoid $EDITOR-based flows unless explicitly requested.
  4. Prefer machine-readable output where possible: --output json.

Common Operations

Folders and listing

himalaya folder list
himalaya envelope list
himalaya envelope list --folder "Sent"
himalaya envelope list --page 1 --page-size 20

Search

himalaya envelope list from john@example.com subject meeting

Read/export message

himalaya message read 42
himalaya message export 42 --full

Send new message (POSIX shell)

cat << 'EOF' | himalaya template send
From: you@example.com
To: recipient@example.com
Subject: Test Message

Hello from Himalaya.
EOF

Send new message (PowerShell)

@"
From: you@example.com
To: recipient@example.com
Subject: Test Message

Hello from Himalaya.
"@ | himalaya template send

Reply / forward

himalaya template reply 42 | himalaya template send
himalaya template forward 42 | himalaya template send

For forward/reply edits, materialize the template, edit headers/body, then pipe to template send.

Organize / delete / flags

himalaya message move 42 "Archive"
himalaya message copy 42 "Important"
himalaya message delete 42
himalaya flag add 42 --flag seen
himalaya flag remove 42 --flag seen

Attachments

himalaya attachment download 42
himalaya attachment download 42 --dir ~/Downloads

Multi-account Usage

himalaya account list
himalaya --account work envelope list

References

  1. references/configuration.md for account configuration patterns.
  2. references/message-composition.md for MML and MIME composition.

Pitfalls

  1. Message IDs are folder-relative; re-list after folder switches.
  2. Do not put credentials in plaintext outputs.
  3. If SMTP/IMAP auth fails, verify auth command/keyring and account selection.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free