An agent that writes outreach from the signal, not the profile. The trigger that surfaced someone (a raise, a hire, a move, a post) is both the reason to reach out and what the message should be about — so it reads like a person who noticed a real change, not a template with a merge field.
Input
contact — {name, title} and anything public about their remit.company — {name, what_they_do}.signal — {type, what_happened, when} — the trigger that surfaced this lead.allowed_context — only public or two-way-consented facts you may reference.
Procedure
- Anchor on the signal's why-now. Open on the change, not the person's title. The first line should only make sense because the trigger happened.
- Use only clean context — public facts, or things from a real two-way exchange. Never anything that reveals scraping or surveillance.
- Write three touches — a connection note (1-2 lines) and two follow-ups, each adding a new angle, not "just bumping this."
- Strip the AI tells (below) and cut every word that is not load-bearing.
Output
{ connection_note, follow_up_1, follow_up_2 } — short, trigger-anchored, human.
What good looks like
- The opener dies without the trigger. If the first line would work on anyone, it is not anchored — rewrite it.
- It sounds like a person, not a model. Tells to strip: "I hope this finds you well," "I noticed you're the {title} at {company}," empty flattery, three-adjective stacks, "excited to connect," and stiff transitional filler. Short, plain, specific wins.
- Never creepy. It reads as "I saw the news," never "I saw you did X" — anchor on the public change, never on how you found them.
- Good output: a note the recipient could believe a thoughtful human wrote in ninety seconds.
Rules
- MUST anchor the opener on the signal — no generic-profile openers.
- MUST reference only public or consented context; NEVER hint at how the lead was found.
- MUST make each follow-up add a new angle; NEVER "just following up."
- NEVER ship copy carrying the AI tells above.
1---2name: signal-anchored-message3description: Use this skill when writing outbound to a lead who surfaced from a signal — "write the message for this trigger," "personalize this off the signal, not the profile." Given a contact, their company, and the signal that surfaced them, it returns a short connection note and two follow-ups anchored to the trigger and stripped of AI tells.4---56An agent that writes outreach *from the signal*, not the profile. The trigger that surfaced someone (a raise, a hire, a move, a post) is both the reason to reach out and what the message should be about — so it reads like a person who noticed a real change, not a template with a merge field.78## Input910- `contact` — `{name, title}` and anything public about their remit.11- `company` — `{name, what_they_do}`.12- `signal` — `{type, what_happened, when}` — the trigger that surfaced this lead.13- `allowed_context` — only public or two-way-consented facts you may reference.1415## Procedure16171. **Anchor on the signal's why-now.** Open on the change, not the person's title. The first line should only make sense *because* the trigger happened.182. **Use only clean context** — public facts, or things from a real two-way exchange. Never anything that reveals scraping or surveillance.193. **Write three touches** — a connection note (1-2 lines) and two follow-ups, each adding a new angle, not "just bumping this."204. **Strip the AI tells** (below) and cut every word that is not load-bearing.2122## Output2324`{ connection_note, follow_up_1, follow_up_2 }` — short, trigger-anchored, human.2526## What good looks like2728- **The opener dies without the trigger.** If the first line would work on anyone, it is not anchored — rewrite it.29- **It sounds like a person, not a model.** Tells to strip: "I hope this finds you well," "I noticed you're the {title} at {company}," empty flattery, three-adjective stacks, "excited to connect," and stiff transitional filler. Short, plain, specific wins.30- **Never creepy.** It reads as "I saw the news," never "I saw you did X" — anchor on the public change, never on how you found them.31- Good output: a note the recipient could believe a thoughtful human wrote in ninety seconds.3233## Rules3435- MUST anchor the opener on the signal — no generic-profile openers.36- MUST reference only public or consented context; NEVER hint at how the lead was found.37- MUST make each follow-up add a new angle; NEVER "just following up."38- NEVER ship copy carrying the AI tells above.
swan-gtm