Know if you have enough at-bats for next quarter.
Forward-looking coverage math per channel and per rep, so you see the gaps before they cost you the number.
Inside: The coverage math per channel and per rep, and the gap read.
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.
accounts, owners, channel attribution, and forecasted value, live.
powers the product channel and the new-user signal.
better ranking and the "why now" line.
To use your own channels, replace the channel list with whatever your business runs. To use your own targets, set a per-channel pipeline number and the coverage math re-bases against it.
| Set this | What it is | Default / Example |
|---|---|---|
| CRM connector | System of record for accounts, owners, pipeline | A CRM |
| Product-analytics connector | Source of product usage and active-user counts | A product-analytics tool |
| Channel field | The account field that classifies channel | A "channel source" field; never the opportunity-level channel field |
| Fit-score field | Account-level ICP fit score | An "account fit score" field0-100 |
| Forecast / target field | Account-level forecasted value used in coverage math | A "forecasted value" field |
| Channels | Your acquisition channels | InboundOutboundProduct |
| Coverage targets | Per-channel pipeline target for the period | Set from your quota plan |
| Activity sources | The signals that count as "engaged" | Callsemailstasksproduct eventsweighted by recency |
| Daily drop size | Accounts surfaced per day | 10 |
Everything the skill does, in full.
This skill answers the top-of-funnel coverage question: do you have enough at-bats to hit next quarter's number, and where are the gaps? It reads your CRM and a product-analytics tool, runs forward-looking coverage math per channel and per rep, ranks the hottest accounts to work, builds a daily prioritized account drop with a named owner per account, and surfaces the segments you are under-prospecting. It is built for the person who runs the pipeline review, not the person who works a single lead.
- 11. Classify every account by channel. Read the channel field and group accounts into your channels.
- Run forward-looking coverage math per channel. Project the pipeline needed to hit the period target using win rate and cycle time, then compare projected against needed. Output a covered-percentage and a health flag (healthy, under, over) per channel.
- Score account engagement velocity per rep. Count accounts engaged in a trailing window using your activity sources, weighted by recency, against book size.
- Rank hot accounts. A composite of recent signal, account-fit score, and product engagement.
- Detect the new-user signal. Flag accounts showing fresh active users as a distinct work item.
- Surface under-prospected segments. Cross fit score against coverage. Name the gap as segment plus channel, with target and current percentages.
- Build the daily drop. Top N prioritized accounts, each with a recommended owner and a one-line "why now."
- Compute the coverage gap. Target, current projection, dollar gap, and the math to close it. End with the single point of leverage.
- Coverage math is forward-looking. It projects pipeline needed for the next period, not just open opps.
- The daily drop names a recommended owner, with the account fact that justifies the routing.
- Under-prospected surfacing is segment plus channel, with target and current percentages.
- Fail loud on missing fields. Never invent a field name or definition.
TEAM PIPELINE COVERAGE · Period target: 1.8M new revenue Per-channel coverage: INBOUND: 890K projected vs 900K needed · 99% covered · HEALTHY OUTBOUND: 310K projected vs 720K needed · 43% covered · UNDER PRODUCT: 202K projected vs 180K needed · 112% covered · OVER THE DAILY DROP, Monday 1. Account One Recent funding + sales hiring spike Owner: Rep A Fit 87 2. Account Two Cost-consolidation trigger Owner: Rep C Fit 73 3. Trial Account 3 active users, 1 power user Owner: Rep B Fit 68 Under-prospected segments: - Mid-market, Outbound: 22% of target, 8% current coverage - Existing accounts with new-user signups in last 30d: 12 ignored Coverage gap math: Needs 1.8M. Current projection 1.4M (gap 400K). To close: 18 more opps at avg 22K + 60% win rate = 30 more meetings. Leverage point: Rep C plus the outbound segment.
The coverage targets, win rate, cycle time, average deal size, and the daily-drop size are defaults. Re-tune them to your plan. The thresholds that drive healthy, under, over are defaults too. Set them where your team draws the line. The activity-source weighting is a starting point; adjust which signals count and how recency decays.
Where an operator takes this next.
The coverage math and the daily drop prove the gap and the priority. Here's the version that runs before the rep's first coffee.
Coverage math answers "do we have enough." The daily drop is what actually closes the gap.
A scheduled Claude task pulls the CRM and product-analytics data every morning and delivers each rep's top-10 by 7am.
Connect Slack so a channel crossing below its coverage threshold posts straight to the manager, instead of surfacing at the weekly review.
Connect a hiring or funding signal source so the daily drop's reason line writes itself from live data, not a rep's memory.
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.