Menu

Individual skill

send-email

Compose and send a one-off email to a named recipient via Resend - written in the operator's voice, then sent in-run through the shared send caps with an operator audit copy

skills/send-email/SKILL.md

Read pinned source

Source commit 25575a6be3bfab41925964de55654056a2fe0c39

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
789
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
> **${var}** — who to email and why, e.g. `to=jane@acme.com | subject=Intro | about=propose a 20-min call on X`. Freeform also works ("email jane@acme.com to follow up on yesterday's demo"). `cc=` is optional. The reply-shape `revise:<instruction>` (Telegram force-reply, e.g. `revise:make it warmer`) refines the **last composed draft for review only — it never sends**.

Read `soul/` (for voice) and `memory/MEMORY.md` (for context) before composing.

## What this does

Composes a single, purposeful email and sends it **in-run** via Resend (`./secretcurl`), gated by the shared send caps + kill-switch and logged to the shared ledger `memory/email-log.json`. The send is irreversible, so it's the skill's **final** action, behind a set of fail-closed checks (see "Send (in-run)" below): a skipped or failed check means *do not send*, never *send anyway*. This is the general-purpose sibling of vuln-scanner's disclose arm (Arm C, `var=disclose`) — same caps + audit CC, any recipient and purpose instead of only vuln maintainers.

This is **not** a bulk or cold-outreach tool. One deliberate recipient per run, with a genuine reason to write. If the request reads as mass-mailing, list-blasting, or spam, refuse and log `SEND_EMAIL_REFUSED: not a 1:1 purposeful email`.

## Steps

### Revise intercept (Telegram force-reply — re-stage for review only, NEVER auto-send)

**Before anything else**, if `${var}` starts with `revise:`, the operator replied to a "refine this email?" prompt. Handle it here and **end the run** — the normal compose/send flow below does NOT run, and **nothing is ever sent**: