Sending email from a task

recoup-platform-email-helper

Send an email via the Recoup API the reliable way — a Node helper that serializes the body correctly and fails loudly instead of sending an empty email. Use whenever a task needs to email a report/summary/notification to the account owner or a recipient. ALWAYS use this script to send email; never hand-build `curl … -d "{…}"` with inline `jq`/shell interpolation (that silently produces empty "Message from Recoup" footer-only emails). Pairs with recoup-platform-api-access (which it sends through).

recoupable/skills·4.5Kinstalls5stars

SKILL.md

Full skill instructions

Sending email from a task

Send email by running the bundled Node script — do not assemble JSON in the shell.

Why this exists

Hand-rolling the send (curl -sS … -d "{… \"html\": $(echo "$HTML" | jq -R -s '.') …}") is fragile: depending on quoting/escaping it produces a malformed body, and the API used to silently deliver an empty footer-only email titled "Message from Recoup" with success:true. The model gets this wrong stochastically. This script removes shell serialization entirely.

How to send

Write the email body to a file (recommended for HTML — avoids all escaping issues):

cat > /tmp/report.html <<'HTML'
<h1>Daily Report</h1>
<p>…your real content…</p>
HTML

Send it:

node "$SKILL_DIR/scripts/send-email.mjs" \
  --subject "Daily Report — $(date '+%B %d, %Y')" \
  --html-file /tmp/report.html \
  --to [email protected]

$SKILL_DIR is this skill's install directory (~/.agents/skills/recoup-platform-email-helper); use the absolute path to scripts/send-email.mjs.

Flags

Flag	Meaning
`--subject <s>`	Subject line (optional — the API derives one from the body if omitted).
`--html-file <path>` / `--html <s>`	HTML body. Prefer `--html-file`.
`--text-file <path>` / `--text <s>`	Plain-text body.
`--to <email>`	Recipient (repeatable). Omit to default to the account's own email ("email me this").
`--cc <email>`	CC (repeatable).
`--chat-id <id>`	Room id for the footer "continue the conversation" link.
`--dry-run`	Serialize + validate and print the payload; do not send. Use to preview.

Rules

Exactly one body is required. The script refuses to send (exit code 2) if there is no non-empty --html/--text. Never try to send an empty email.
Check the exit code. Non-zero means it did not send — read stderr and fix it; do not report success. The script prints the Resend message id on a real send.
The script reads RECOUP_API_KEY / RECOUP_ACCESS_TOKEN and RECOUP_API_BASE from the environment — these are already set in the sandbox. Never print or hard-code them.
Node only (the sandbox runtime is node22; python3 is not guaranteed). Zero dependencies.

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/recoupable/skills --skill recoup-platform-email-helper

View on GitHub

recoup-platform-email-helper

recoup-platform-api-access
Call the Recoup API and external connectors directly — fetch any platform resource (artists, socials, organizations, research, documents) and run connector actions (Google Docs/Sheets/Drive edits, Gmail, TikTok, Instagram). Use whenever you need raw Recoup data, a platform resource, to write curl against api.recoupable.dev, or to read/write something outside Recoup like a Google Doc URL or a spreadsheet. The plumbing every other skill rides on. To onboard or operate on an artist use the recoup-roster-* skills; for first-run connection use recoup-platform-connect-account.
4.5K installs
recoup-platform-build-os
Scaffold and run a label's self-managing "music-company OS" inside its own git repo — the full label-intelligence workspace (folders, a self-managing CLAUDE.md mirrored to AGENTS.md, a read-only doctor + never-stale janitor, compound-learning and self-improvement loops, an in-place plugin) seeded with Recoup's conventions (top-level artists/{slug}/RECOUP.md identity files, releases/{slug}/RELEASE.md) and backed by the Recoup API as system of record. Use for "set up our label OS", "build the org workspace", "turn this repo into our label brain", or onboarding a new org/label repo. Pulls the real roster from the live account (auth via recoup-platform-connect-account), onboards artists API-first via recoup-roster-add-artist, and calls the other recoup-* skills (research/content/release/song/catalog) instead of reinventing them. The single workspace/OS builder — also covers the lightweight "just mirror my roster into folders" case.
4.3K installs
recoup-roster-manage-artist
Work inside one artist's folder — read and update their context, brand, songs, and releases. Use for "organize [artist]'s files", "update [artist]'s brand/context", "what's in [artist]'s workspace", or any task about a named artist's files. To list your whole roster use recoup-roster-list-artists; for research/metrics on an artist use recoup-research-artist-overview.
4.3K installs
recoup-roster-add-artist
Onboard a brand-new artist to your roster and enrich them — the 8-call chain (create → Spotify match → research → catalog → socials → knowledge base) that sets up the artist and their workspace folder. Use for "create/add/onboard an artist", "set up [artist]", "we just signed [artist]", or "new signing". To see your roster use recoup-roster-list-artists; to work inside an existing artist's files use recoup-roster-manage-artist.
4.3K installs

More skills from recoupable

recoupable/skills

recoup-roster-list-artists

See who's on your roster — answers "what artists do I have" by walking the workspace and falling back to your live account when the filesystem is empty. Use for "what artists do I have", "list my roster", "who's on my roster", or "what's in this sandbox". To add a new artist use recoup-roster-add-artist; to work inside one artist's files use recoup-roster-manage-artist.

5 4.3K

View