Build your signal library and wire it to motion
Episode 3, made runnable. You built the context brain in Episode 2. The signal library is the file that turns it from a reference doc into a system that acts. Define your signals, then wire the freshest to a motion. A signal without a motion is just a dashboard.
Build your signal library and wire it to motion
Episode 3, made runnable.
You built the context brain in Episode 2. The signal library is the file that turns it from a reference doc into a system that acts. Define your signals, then wire the freshest to a motion. A signal without a motion is just a dashboard.
Details
Details
Details
Details
The product channel
Usage turned into the best-converting channel.
A real signal library with detection
Decay
Combinations
Then one signal scored
You have signal everywhere: usage spikes, intent, funding, hiring. And it dies in a dashboard nobody acts on. Worse, most teams never decay it, so their active list quietly fills with six-month-old events. A signal without a motion is just a chart.
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
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.
Fair across channels, blank fields never scored as zero, with a why behind each account's score.
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.
Takes a read's output and drafts what goes out, draft-first and fully logged, ready to paste or write directly when connected.
A real signal library with detection, decay, and combinations, then one signal scored, acted on while fresh, and routed back where it belongs.
- All 4 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: A RevOps lead has funding, hiring, product-usage, and intent data sitting in separate dashboards nobody acts on, and wants one signal wired end-to-end to a booked touch this week.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: The best signal category is a blank column.
Without it: Signals fire into a channel nobody rereads.
Without it: Fresh signals age into trivia.
Without it: Half the buying committee moves unseen.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
If you sell a product people can use before they buy, you already have a product-led channel. The question is never whether it exists. It is whether your usage data has been turned into context a rep can act on. Map the events first. The motion comes after.
Dig into the full build →A signal is only as good as the motion it triggers
The library hands the team scored signals with decay and combinations; the pipeline comes from a rep touching the account while the signal is still warm. Here is how a GTM leader wires the human half so signals become meetings instead of dashboard rows.
When a signal fires, the owner states the read, the play, and the deadline out loud the same day. The team drills this on live signals weekly until the route from fired to first touch is reflex.
- 01Teach the read per signal type
A hire signal, a usage spike, and a funding event each mean a different next move. Walk the team through the library's categories so the response matches the signal, not a generic sequence.
- 02Separate the two clocks
Decay says how long a signal counts toward score; freshness says how long the outreach window stays open. Train the team on both, because a scoring signal is not automatically a sendable one.
- 03Hold the fired-to-touch SLA
Every signal comms-agent routes carries an owner and a deadline set by its freshness window, and the weekly review starts with the signals that expired untouched.
- 04Reweight by what converted
Monthly, compare which signal types and combinations produced meetings and pipeline, then adjust the library's points and decay curves. The library learns or it goes stale.
One plugin. 4 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.