Build a signal library that fires, decays, and combines.
“We say we should watch for funding and hiring, but nothing fires. How do we build signals that act?”
Turns "we should watch for funding" into real signals: how you detect each one, what it is worth, how it decays, which combinations score higher, and the hook that earns the reply. The file that makes your context repo act.
What this skill does
Turns "we should watch for funding" into a real signal library: each signal with how you detect it, what it is worth, how it decays, which combinations score higher, and the message hook that earns the reply. This is the file that makes your context repo act, not just describe. A list of alerts that is never scored or decayed is not a signal library.
Inputs
Your ICP definition (from Define Your ICP), so signals are scored against real fit. And whatever you know about the moments that precede a deal: funding, a new hire, a product-usage spike, a competitor switch, intent. No connectors required to design it; connect your data sources when you want to detect them live.
How it works
- 11. List the moments that precede a deal. The events that mean now, not someday: a new RevOps hire, a Series B in the last 60 days, a usage spike, a competitor renewal coming up. Start with 5 to 8, not 30.
- Give each a detection method. How you actually see it: a Crunchbase alert, a job-board scrape, a product-usage threshold, an intent feed. A signal you cannot detect is a wish.
- Score each in points, against fit. The same signal on a Tier 1 account is worth more than on a Tier 3. Points, not vibes.
- Set a decay curve. A funding round from 150 days ago is not the signal it was at 10 days. Decay the points over time so your active list reflects real urgency, not old history. This one step fixes the list that quietly fills with stale accounts.
- Add combination bonuses. Two signals together tell you more than either alone. A Series B plus a new RevOps hire is not a 65-point account, it is an 80-point account: budget exists and someone is rebuilding. Write the pairs that matter and the bonus each earns.
- Write a message hook per signal. The one line that makes the outreach obviously about them, tied to the signal that fired.
- Leave a performance-log stub. A column for meetings generated per signal, empty for now. Episode 4 fills it, and the library starts to learn which signals actually pay.
relevance
Run the four-part relevance check on a cold message before it sends, or on a draft that already exists.
Turn a finished campaign into a change your agent can read.
Rebuilds the decisions behind one outbound campaign, ties every number back to one of them, separates what worked from why it worked, and writes one specific change into the list, the angle library, or the instructions.