Turn job postings at your accounts into deal moves.
Watches job postings at the accounts already in your pipeline and customer book, and reads each one as a deal signal. Every read ties to a named deal and ends in one dated move, not a cold sequence.
In plain English: “What are my accounts hiring for?”
Inside: The four posting reads, the in-play scope rule, the deal-tied radar table, and the verify-before-acting gates.
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.
postings arrive on their own, across the whole book.
deal stage, close date, and renewal date attach to each read automatically.
This was built for a B2B SaaS seller with a mixed book of opps and renewals. Set these to your world:
The scope rule is the whole skill. Open opps, active trials, renewals inside 6 months, and named expansion targets are in. Everything else is out, no matter how interesting the posting.
| Set this | What it is | Default / Example |
|---|---|---|
| PROBLEM keywords | role keywords that mean your problem | "revenue operations""sales enablement""data quality" |
| OWNER titles | the titles that would own your product | Head of RevOpsDirector of Sales Ops |
| CHECK cadence | how often the radar sweeps | weekly (re-tune to your cycle length) |
| ACCOUNT scope | which accounts are in play | open oppsactive trialsrenewals inside 6 monthsexpansion targets |
Everything the skill does, in full.
Watches job postings at the accounts already in your pipeline and customer book, and reads each one as a deal signal. A posting can mean the timing just got better, a new stakeholder is about to arrive, the decision dynamics are about to shift, or the budget is about to disappear. This skill makes the read, ties it to the specific deal or renewal it affects, and names one dated move on that deal. It is not a prospecting tool. If the account is not already in play, it is out of scope. Where trigger-outreach takes any buying signal and writes a timely cold-ish touch for new accounts, this skill is scoped to accounts already in play and its output is a deal move, not an outreach sequence.
- 1Read 1: They are hiring for the problem you solve
A posting that describes the pain your product removes is a timing signal. Someone got budget to fix the problem, and headcount is the expensive way to fix it. The move belongs on the live deal: raise the posting's problem statement in your next call and position against the cost of the hire, not against a competitor.
- 2Read 2: They are hiring the role that would own your product
A posting for the title that would run your tool means a new stakeholder is entering the deal. Get there first. If the deal closes before they start, you want the incumbent tool to be yours. The move: ask your contact who is hiring for it and what the new owner will walk into, and get your product into the onboarding conversation.
- 3Read 3: A leadership change posting
A VP or C-level posting at an in-play account means the decision dynamics are about to shift. Your current buyer may lose authority, your deal may get re-litigated, your renewal may get re-evaluated by someone with no history with you. The move: pressure-test the deal's approval path now, before the new leader lands, and get the business case in writing.
- 4Read 4: A hiring freeze or posting takedown
Postings that vanish, or a public freeze, are budget risk on the deal. If they stopped hiring for the problem, they may stop buying for it too. The move: qualify the budget directly this week, and if it is a renewal, move the value conversation up before the cut list gets written.
- A posting is a hypothesis, not a fact. Verify before you act on it. Postings go stale, get reposted by agencies, and sit open for roles already filled.
- Never quote a posting back to a prospect verbatim in a way that reads as surveillance. Reference the problem, not the paragraph.
- Tie every read to a named deal or renewal, or it does not count. A signal with no deal attached is trivia.
- One move per read, with a date on it. A read that ends in "monitor" is not a read.
PIPELINE HIRING RADAR · sample data · 4 in-play accounts Account Deal / Stage Posting seen Read Move (dated) Acme Corp Opp / Proposal Sr RevOps Manager Owner hire Ask contact who owns onboarding, by Fri Northwind Renewal / 90 days VP Sales (new role) Leadership shift Get business case in writing, this week Vertex Opp / Eval "fix pipeline data" Problem hire Position vs cost of hire, next call Tue Blend Labs Trial / Active 3 postings pulled Freeze risk Qualify budget directly, call Wed Out of scope this run: 2 postings at accounts with no open deal. Logged, not read.
Where an operator takes this next.
The read is step one. Here is where an operator takes it once the manual version proves out.
The radar is only as good as its refresh rate. Automate the sweep, keep the judgment.
Connect Clay's job-postings enrichment or Common Room so every in-play account is checked on your cadence, not just the 10 you have time for.
Set up a scheduled Claude task to run the sweep every Monday and post the reads that touched a named deal to your Slack channel before pipeline review.
Push each read into the Salesforce opportunity as a logged signal, so the deal history shows what you saw and when you moved.
LinkedIn shows when the owner-hire role gets filled. The start date of that person is a calendar event on your deal.
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.