mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-04-12 12:43:32 +08:00

Files

Affaan Mustafa 5196647681 chore: checkpoint hermes-generated ops skills

2026-04-02 15:14:20 -07:00

5.7 KiB

Raw Blame History

name, description, origin

name	description	origin
email-ops	Evidence-first mailbox triage and sent-mail-safe reply workflow for Hermes. Use when organizing folders, drafting or sending through Himalaya, or verifying a message landed in Sent.	Hermes

Email Ops

Use this when the user wants Hermes to clean a mailbox, move messages between folders, draft or send replies, or prove a message landed in Sent.

Prerequisites

Before using this workflow:

install and configure the Himalaya CLI for the target mailbox accounts
confirm the account's Sent folder name if it differs from Sent

Skill Stack

Pull these companion skills into the workflow when relevant:

investor-outreach when the email is investor, partner, or sponsor facing
continuous-agent-loop when the task spans draft, approval, send, and Sent proof across multiple steps
search-first before assuming a mail API, folder name, or CLI flag works
eval-harness mindset for Sent-folder verification and exact status reporting

When To Use

user asks to triage inbox or trash, rescue important mail, or delete only obvious spam
user asks to draft or send email and wants the message to appear in the mailbox's Sent folder
user wants proof of which account, folder, or message id was used

Workflow

Read the exact mailbox constraint first. If the user says himalaya only or forbids Apple Mail or osascript, stay inside Himalaya.
Resolve account and folder explicitly:
- check himalaya account list
- use himalaya envelope list -a <account> -f <folder> ...
- never misuse -s INBOX as a folder selector
For triage, classify before acting:
- preserve investor, partner, scheduling, and user-sent threads
- move only after the folder and account are confirmed
- permanently delete only obvious spam or messages the user explicitly authorized
For replies or new mail:
- read the full thread first
- choose the sender account that matches the project or recipient
- if the user has not explicitly approved the exact outgoing text, draft first and show the final copy before sending
- store approval state with python3 $HERMES_HOME/scripts/email_guard.py queue ...
- before any send, require python3 $HERMES_HOME/scripts/email_guard.py approve --id <id> plus python3 $HERMES_HOME/scripts/email_guard.py can-send --id <id> --account <account> --recipient <recipient> --subject <subject>
- before any send or reply, run python3 $HERMES_HOME/scripts/email_guard.py history --recipient <recipient> --subject <subject snippet> --days 45 --json to catch prior outbound and accidental repeats
- if the exact Himalaya send syntax is uncertain, check himalaya ... --help or a checked-in helper path before trying a new subcommand
- compose with himalaya template send or himalaya message send using file-backed content when possible, not ad hoc heredoc or inline Python raw-MIME wrappers
- avoid editor-driven flows unless required
If the request mentions attachments or images:
- resolve the exact absolute file path before broad mailbox searching
- keep the task on the local send-and-verify path instead of branching into unrelated web or repo exploration
- if Mail.app fallback is needed, pass the attachment paths after the body: osascript $HERMES_HOME/scripts/send_mail.applescript "<sender>" "<recipient>" "<subject>" "<body>" "/absolute/file1" ...
If the user wants an actual send and Himalaya fails with an IMAP append or save-copy error, a CLI dead end, or a raw-message parser crash, do not immediately resend. First verify whether the message already landed in Sent using the history check or himalaya envelope list -a <account> -f Sent .... If the failure was an invalid command path or a panic before Sent proof exists, report the exact blocked state such as blocked on invalid himalaya send path or blocked on himalaya parser crash and preserve the draft. Only if there is still no sent copy and the user explicitly approved the send may you fall back to $HERMES_HOME/scripts/send_mail.applescript. If the user constrained the method to Himalaya only, report the exact blocked state instead of silently switching tools.
During long-running mailbox work, keep the loop tight: draft -> approval -> send -> Sent proof. Do the next irreversible step first, and do not branch into unrelated transports or searches while the current blocker is unresolved. If a budget warning says 3 or fewer tool calls remain, stop broad exploration and spend the remaining calls on the highest-confidence execution or verification step, or report exact status and next action.
If the user wants sent-mail evidence:
- verify via himalaya envelope list -a <account> -f Sent ... or the account's actual sent folder
- report the subject, recipient, account, and message id or date if available
Report exact status words: drafted, approval-pending, approved, sent, moved, flagged, deleted, blocked, awaiting verification.

Pitfalls

do not claim a message was sent without Sent-folder verification
do not use the wrong account just because it is default
do not delete uncertain business mail during cleanup
do not switch tools after the user constrained the method
do not invent himalaya smtp or other unverified send paths
do not build last-minute raw-send wrappers when the checked commands and guard scripts already cover the path
do not wander into unrelated searches while an attachment path or Sent verification is unresolved
do not keep searching through the budget warning while the user is asking for a status update

Verification

the requested messages are present in the expected folder after the move
sent mail appears in Sent for the correct account
the final report includes counts or concrete message identifiers, not vague completion language

5.7 KiB Raw Blame History