heinzel-emaillisted
Install: claude install-skill wintermeyer/heinzel
# heinzel-email
Send ad-hoc text and file attachments by email about a managed
server. The report content is *about* the server; whether the
mail leaves *from* the server or *from* your workstation is a
per-host preference that's asked once and remembered.
The full heinzel first-connection onboarding pipeline still
applies before any of this runs.
## Workflow
1. **Onboarding pipeline.** Run `rules/first-connection.md` in
full. No "quick question" exception — even a one-line email
still goes through blacklist/read-only check, DNS alias
detection, SSH user lookup, OS detection, server memory
load, and activity check.
2. **Load overrides.** Apply the heinzel rule-override chain
(later wins):
- `memory/custom-rules/heinzel-email.md` if present.
- `memory/servers/<host>/memory.md` (recipient, source,
transport, policies — see "Per-server memory" below).
- `memory/servers/<host>/rules.md` if present.
`memory/custom-rules/all.md` is already loaded by the
session-start preflight — do not re-read it.
3. **Resolve recipient.** In order of precedence:
1. **User said an explicit address** ("send to alice@…",
"mail it to bob@example.com") → use that. Don't override
it with stored values.
2. **Per-server memory** — `memory/servers/<host>/memory.md`
has an `Alert email:` line (the established pattern) →
use that.
3. **"Send me" shorthand** ("email me", "send me", "mail it
to me") and the user's default email is