hermes-mail-triage

原文涵盖的主题

• Hermes Mail Triage
• Freshness check
• Native vs pattern
• Pipeline at a glance
• Critical rules
• Sources

A triage pipeline that reads mail on a schedule, classifies by questions rather than keywords, runs a mechanical check on the raw message before any "newsletter / ad / spam / phishing" verdict, proposes a numbered list, and moves nothing until the owner answers "ok all" or "ok except ...". Hermes provides the scheduler and mail access; the triage logic, sender memory and the never-move-alone rule are patterns this skill defines. Before writing or changing any Hermes config, run hermes --version and hermes update --check, then read https://github.com/NousResearch/hermes-agent/releases/latest. If the installed or latest version is newer than 0.23.0, read every release note since 0.23.0 ("Upgrade notes" first) and adjust. Never apply guidance from this skill to a newer version without that check. | Piece | Status in 0.23.0 | Where | |-------|------------------|-------| | Reading a mailbox | Native: email adapter (IMAP/SMTP, one account per adapter per profile) or the bundled Himalaya email skill (terminal himalaya CLI) | mailbox-topology.md, hermes-gateways | | Several mailboxes in one agent | Not documented as native - several profiles, or Himalaya / an MCP mail tool with several acc

这里只展示节选，请以完整原文和当前要求为准。