Cross-Channel Notify

Send a single message through both email (himalaya) and iMessage (bluebubbles) with consistent formatting.

Workflow

1. Collect inputs: to_email, to_imessage (E.164 or chat_guid), subject, body (markdown).
2. Format: Apply markdown formatting rules from config (see references/formatting.md). Strip unsupported markup for iMessage; keep full markdown for email.
3. Send email: Use himalaya template send with the formatted body.
4. Send iMessage: Use the message tool with channel: "bluebubbles", passing the plain-text rendering of the formatted body.
5. Report: Confirm delivery on each channel; note any failures.

Formatting Rules

The skill reads formatting preferences from a config file at ~/.config/cross-channel-notify/format.yaml. If absent, defaults apply.

See references/formatting.md for the full schema and defaults.

Email Send

cat \x3C\x3C 'EOF' | himalaya template send
From: \x3Csender>
To: \x3Cto_email>
Subject: \x3Csubject>
Content-Type: text/markdown

\x3Cformatted_body>
EOF

iMessage Send

{
  "action": "send",
  "channel": "bluebubbles",
  "target": "\x3Cto_imessage>",
  "message": "\x3Cplain_text_body>"
}

Error Handling

• If himalaya is not configured, skip email and warn.
• If bluebubbles is not configured, skip iMessage and warn.
• If neither channel is available, abort with a clear message.
• Always report which channels succeeded/failed.

Config Location

~/.config/cross-channel-notify/format.yaml

Create it on first use if missing. See references/formatting.md for the schema.