← Back to Skills

himalaya-email-manager

akaihola
Updated Today
8 views
0
View on GitHub
Communicationai

About

This Claude Skill enables email management through the Himalaya CLI tool using IMAP. It allows developers to search, summarize, and delete emails from an IMAP account with natural language queries. Use it for automated email workflows like getting daily summaries or performing batch operations directly from Claude.

Quick Install

Claude Code

Recommended
Plugin CommandRecommended
/plugin add https://github.com/akaihola/skills-akaihola
Git CloneAlternative
git clone https://github.com/akaihola/skills-akaihola.git ~/.claude/skills/himalaya-email-manager

Copy and paste this command in Claude Code to install this skill

Documentation

Himalaya Email Manager

Manage emails using Himalaya IMAP CLI tool. Search, summarize, and delete emails from an IMAP account. Use natural language queries for email operations.

Configuration

Himalaya config: ~/.config/himalaya/config.toml Invocation: uv run scripts/<script>.py (handles Python environment and dependencies) Note: nix-shell commands are embedded in Python scripts

Get Daily Email Summary

Show emails from the past 24 hours in INBOX and Sent folders:

uv run scripts/email-summary.py

Options:

  • -v, --verbose - Show himalaya commands being executed

Output includes:

  • Rich table format with timestamps, senders, and subjects
  • Categorized by folder (πŸ“₯ INBOX, πŸ“€ Sent)
  • Unicode support (Finnish characters, emojis)

Search Emails

Find emails by sender, subject, date range, or folder:

uv run scripts/email-search.py [options]

Options:

  • --folder FOLDER - Folder to search (default: INBOX)
  • --from SENDER - Filter by sender email/name (case-insensitive)
  • --subject TEXT - Filter by subject text (case-insensitive)
  • --date-start DATE - Start date (YYYY-MM-DD)
  • --date-end DATE - End date (YYYY-MM-DD)
  • --limit N - Maximum results (default: 20, capped at 100)
  • --no-limit - Bypass the 100-result limit cap
  • -v, --verbose - Show himalaya commands being executed
  • --help - Show help message

All filters apply with AND logic. Results include message IDs for deletion. Dates must be in YYYY-MM-DD format. FROM filter matches both sender name and email address.

Examples:

# Search by sender
uv run scripts/email-search.py --from "spotify.com"

# Search by subject
uv run scripts/email-search.py --subject "invoice"

# Search by date range
uv run scripts/email-search.py --date-start "2025-12-17" --date-end "2025-12-31"

# Search in Sent folder
uv run scripts/email-search.py --folder Sent --limit 10

# Multiple filters
uv run scripts/email-search.py --from "@newsletter.com" --subject "unsubscribe" --limit 5

# Search with no limit
uv run scripts/email-search.py --limit 200 --no-limit

Save Emails to File

Save email content to a file in various formats:

uv run scripts/email-save.py <message-id> [options]

Options:

  • --folder FOLDER - Folder to search (default: INBOX)
  • --output PATH - Output directory or file path (default: current directory)
  • --format FORMAT - Output format: markdown, text, or json (default: markdown)
  • --date-prefix - Add YYYY-MM-DD date prefix to filename (uses email date)
  • --download-attachments - Download email attachments
  • --attachment-dir PATH - Directory for attachments (default: himalaya downloads directory)
  • --overwrite - Overwrite existing file without confirmation
  • -v, --verbose - Show himalaya commands being executed
  • --help - Show help message

Arguments:

  • message-id - Message ID to save (obtained from search results)

Output formats:

  • markdown: Rich format with headers and metadata
  • text: Plain text with basic headers
  • json: Raw JSON output from himalaya (envelope + body data)

Filename behavior:

  • Default: {message-id}.{ext}
  • With --date-prefix: {YYYY-MM-DD}-{subject-sanitized}.{ext}
  • Subject characters: Spaces and emojis preserved, slashes converted to dashes

Examples:

# Save as markdown to current directory
uv run scripts/email-save.py 56873

# Save to specific directory
uv run scripts/email-save.py 56873 --output ~/saved-emails

# Save with date prefix
uv run scripts/email-save.py 56873 --date-prefix --output /tmp/emails

# Save as text format
uv run scripts/email-save.py 56873 --format text

# Save as JSON
uv run scripts/email-save.py 56873 --format json

# Save to specific file path
uv run scripts/email-save.py 56873 --output ~/important-email.md

# Overwrite existing file without prompt
uv run scripts/email-save.py 56873 --overwrite --output ~/email.md

# Save from Sent folder
uv run scripts/email-save.py --folder Sent 12345 --output ~/sent-emails

# Save with attachments
uv run scripts/email-save.py 56873 --download-attachments

# Save with attachments to custom directory
uv run scripts/email-save.py 56873 --download-attachments --attachment-dir ~/attachments

Delete Emails

Delete emails by message ID with safety preview:

uv run scripts/email-delete.py <message-id> [options]

Options:

  • --folder FOLDER - Folder to delete from (default: INBOX)
  • --execute - Actually perform deletion (default: dry-run mode)
  • -v, --verbose - Show himalaya commands being executed
  • --help - Show help message

Arguments:

  • message-id - Message ID to delete (obtained from search results)

Safety: Always run in dry-run mode first to verify the correct message. In interactive mode, you'll be prompted for confirmation before deletion. When called by OpenCode agent, deletion proceeds immediately with --execute flag.

Examples:

# Preview deletion
uv run scripts/email-delete.py 56838

# Actually delete (interactive - will prompt for confirmation)
uv run scripts/email-delete.py 56838 --execute

# Delete from specific folder
uv run scripts/email-delete.py --folder Sent 12345 --execute

Translate Natural Language Queries

Interpret natural language queries as appropriate script calls:

Summary queries:

  • "Show me today's emails" β†’ email-summary.py
  • "What emails did I get today?" β†’ email-summary.py
  • "Summary of recent emails" β†’ email-summary.py

Search queries:

  • "Find emails from Spotify" β†’ email-search.py --from "spotify.com"
  • "Show me emails about invoices" β†’ email-search.py --subject "invoice"
  • "Search for Atomikettu emails from the past two weeks" β†’ email-search.py --from "atomikettu" --date-start "2025-12-17" --date-end "2025-12-31"
  • "What did I send yesterday?" β†’ email-search.py --folder Sent --date-start "2025-12-30" --date-end "2025-12-30"
  • "Search INBOX for emails from [email protected]" β†’ email-search.py --from "[email protected]"
  • "Find emails with 'newsletter' in subject" β†’ email-search.py --subject "newsletter"

Save queries:

  • "Save email ID 56873" β†’ email-save.py 56873
  • "Save as JSON" β†’ email-save.py 56873 --format json
  • "Save to ~/emails folder with date prefix" β†’ email-save.py 56873 --output ~/emails --date-prefix

Delete queries:

  • "Delete email ID 56838" β†’ email-delete.py 56838 (show preview, ask for confirmation)
  • "Remove the email from Spotify" β†’ First search to find ID, then delete with confirmation

Implementation Notes

When calling scripts:

  1. Always invoke with uv run scripts/<script-name>.py (handles environment and deps)
  2. All nix-shell commands are embedded in Python scripts - don't add them manually
  3. For search by sender or subject, use --from and --subject flags
  4. Date range uses --date-start and --date-end (YYYY-MM-DD format)
  5. Case-insensitive search is automatic - don't worry about capitalization
  6. FROM filter searches both sender name and email address
  7. Always run delete operations in dry-run mode first without --execute flag
  8. Ask user for confirmation before running delete with --execute flag (interactive mode only)
  9. Use -v/--verbose to see himalaya commands being executed (for debugging)

Avoid these pitfalls:

  • Don't use --since or --until (not implemented - use --date-start/--date-end)
  • Don't try to search body content (only headers are available in JSON output)
  • Don't forget to add --execute flag when actually deleting (dry-run by default)
  • Don't use incorrect date format (must be YYYY-MM-DD)

Follow this workflow for search and delete:

  1. Use email-search.py to find messages
  2. Review results with user
  3. Use email-delete.py <ID> to preview deletion
  4. Get user confirmation
  5. Use email-delete.py <ID> --execute to actually delete

Technical context:

  • Backend: Himalaya v1.1.0 (Rust-based IMAP CLI tool) via Python 3.13 with typer and rich
  • Installation: Nix (nix-shell -p himalaya)
  • Output format: JSON β†’ Rich tables with Python json.loads()
  • Authentication: Keyring-based (managed by Himalaya)
  • Protocol: IMAP over TLS (direct server communication)
  • Date format: YYYY-MM-DD (ISO 8601)
  • Case sensitivity: All search filters are case-insensitive using Python .lower()
  • Agent detection: Uses sys.stdin.isatty() to determine if running interactively

Using the Scripts

All scripts use PEP 723 inline metadata and require Python 3.13+. Invoke with uv run to automatically handle Python environment and dependencies:

uv run scripts/<script-name>.py [options]

Dependencies (auto-managed by uv):

  • typer - for CLI argument parsing
  • rich - for beautiful terminal output

GitHub Repository

akaihola/skills-akaihola
Path: himalaya-email-manager

Related Skills

sglang

Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill

evaluating-llms-harness

Testing

This Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.

View skill

llamaguard

Other

LlamaGuard is Meta's 7-8B parameter model for moderating LLM inputs and outputs across six safety categories like violence and hate speech. It offers 94-95% accuracy and can be deployed using vLLM, Hugging Face, or Amazon SageMaker. Use this skill to easily integrate content filtering and safety guardrails into your AI applications.

View skill

langchain

Meta

LangChain is a framework for building LLM applications using agents, chains, and RAG pipelines. It supports multiple LLM providers, offers 500+ integrations, and includes features like tool calling and memory management. Use it for rapid prototyping and deploying production systems like chatbots, autonomous agents, and question-answering services.

View skill