Turn a buying signal into a timely touch.
Read the trigger (funding, hire, launch, job posting, tech change), pick the one angle it earns, and write the touch while it is still fresh.
Inside: The trigger read, the freshness gate, and a one-angle draft.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it watches for funding, hiring, launches, and tech changes, so you catch the trigger the day it fires, not a week late.
it checks whether the account is already owned or in a deal, so the touch fits the relationship you actually have.
it drops the drafted touch straight into your outreach, ready to review and send.
This was built for a B2B team working signals into outbound. Set these to your motion:
Point it at your signals and your voice. The skill writes in the register you set, tied to the problem you actually solve, not a generic pitch.
| Set this | What it is | Default / Example |
|---|---|---|
| SIGNAL sources | where triggers come from | fundinghiringlaunchtech changenews |
| SEQUENCER | where the touch gets sent | any email or sequence tool |
| FRESHNESS window | how old a trigger can be and still count | 14 days (retune to your motion) |
| ANGLE map | which angle each trigger type earns | funding to capacityhire to mandate |
| VOICE | your tone and length rules | shortplainone askno flattery |
| VALUE hook | the problem you tie the trigger to | what the signal implies they now need |
Everything the skill does, in full.
Takes a buying signal and turns it into a message worth reading. It reads what the trigger actually means, picks the one angle the signal earns, and writes a short, specific touch that lands while the event is still fresh. No spray. No "congrats on the round" with a pitch stapled to it. A reason to reach out, and a message built around that reason.
- 1Read the trigger
Name what actually happened and what it implies. A funding round means new capacity and pressure to deploy it. A senior hire means a new mandate and a window to shape it. A product launch means a go-to-market push and new load on a team. A job posting names a gap in words the company chose. A tech change means a stack in motion. The read is the work. The message is downstream.
- 2Freshness gate
A trigger has a half-life. Check the date before you write. Inside the freshness window, the event is a live reason to reach out. Past it, the touch reads as late and the angle is weaker. If a signal is stale, say so and pick a different reason, or wait for the next one.
- 3Pick the angle (one, not three)
Each trigger earns one angle. Funding earns a capacity or scaling angle. A new leader earns a mandate or first-90-days angle. A launch earns a load or growth angle. A job post earns a "you named this gap" angle. A tech change earns a fit-with-your-new-stack angle. Pick the one the signal actually supports. Do not stack all of them into one message. One reason, said well, beats three reasons said fast.
- 4Write the touch
Short. Specific to the trigger. One ask. Open with the event as the reason you are reaching out, tie it to the problem it implies, and make one clear next step. No flattery-then-pivot. The signal is not a warm-up line, it is the whole reason the message exists, so the message should not survive with the trigger removed.
- 5Relevance test
Read it back and ask: could this exact message be sent to any other company? If yes, it is not signal outreach, it is a template with a name swapped in. Rewrite until the trigger is load-bearing.
- Every touch names the specific trigger. No generic opener dressed up as timely.
- The freshness date is checked. A stale trigger is flagged, not sent as if fresh.
- One angle per message. No stacking funding plus hiring plus launch into one touch.
- The message fails the relevance test if it could be sent to any other account. Rewrite it.
- Any metric used to illustrate is clearly illustrative, never presented as a real number about the target.
TRIGGER OUTREACH · Northwind (illustrative) Signal: Series B raise, 9 days ago (inside freshness window) Angle: New capacity, pressure to deploy the team fast Persona: VP Sales Draft: Subject: your Series B and the next 20 reps Saw the round close last week. Rounds like this usually mean a hiring plan that outpaces the process that has to support it. When a team doubles, the outbound motion is often the first thing that cracks. Worth 20 minutes to compare notes on what tends to break at that size? Why it works: the raise is the whole reason for the touch. Remove it and the message has nothing to stand on. That is the test.
Where an operator takes this next.
One good touch is the start. Here is where an operator takes it once the manual version works.
The stack stays simple: a signal source fires it, Claude reads and writes it, the CRM keeps it honest about the relationship, your sequencer sends it. You set the angle map once; it runs on every trigger after that.
Wire a signal source into a scheduled Claude task that drafts the touch the day a trigger fires and drops it in your sequencer for review. You react to a ready draft, not a news alert.
Have the task read Salesforce or HubSpot first, so an owned account or open deal gets a relationship-aware touch instead of a cold intro to someone you already know.
Fresh triggers go straight to a draft; stale ones get parked with a note. You never send "congrats on the round" three weeks late, and the good ones never sit.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.