Stack the right tools and signals for the workflow.
Picks the tools that move the data and the signals that tell the workflow who and what matters, so it runs on the right inputs. Not a buy-everything shopping trip.
In plain English: “What tools and signals does this workflow need?”
Inside: The tools and signals the workflow needs, and the context to run on.
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.
Everything the skill does, in full.
Assembles the stack for one workflow: the tech that carries the data and the signals that give it context. The point is not to shop for tools or to rebuild infrastructure. It is to give this specific workflow the right inputs, so it runs on real context instead of a lone tool guessing.
- 11. Walk the steps and name the context each one needs. For account prep: which account, what fit, what timing, what history. Context is the signal a step needs to do its job.
- For each step, name the signal first, then the tech that carries it. Fit is a signal (your ICP model). Timing is a signal (intent, product usage). The CRM, the enrichment vendor, the dialer are tech that carry data. Signal first, tech second.
- Buy the plumbing, build the thin edge. Buy the commodity tech you would be crazy to rebuild. Build only the small layer that is your advantage: the scoring logic, the rules, the view. Most of the edge is signal logic, not infrastructure.
- Assemble the context, do not just connect tools. A stack of tools with no signals is plumbing with nothing flowing through it. The output of this move is the workflow running on the right signals.
- Decide per workflow. The signals and tech that fit this workflow may be wrong for the next. The unit is the workflow, not the contract.
- Buying a platform and calling it context. A tool is not a signal.
- Wiring up tools with no signal flowing through them.
- Rebuilding infrastructure because building feels productive.
[the signals you stacked, the tech that carries them, and the context the workflow now runs on]
Hand the stacked workflow to Split: start with Cut the Drag, then Keep the Judgment. The Sales Operator. Receipts only.
Where an operator takes this next.
The stack is planned. Here is where an operator takes it once the manual version proves out.
The stack is only as good as what is flowing through it, wire the signal, not just the tool.
Build the thin scoring layer as a Salesforce flow so fit and timing route the lead automatically, no rep has to notice it happened.
Push the Amplitude intent spike into Slack as a DM the moment it crosses your threshold, instead of a dashboard nobody checks.
Run new leads through Clay on intake so fit and timing are already on the record when the rep opens it.
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.