Build the pipeline report a review actually needs.
Coverage, creation, movement, and aging on one page, ending in the deals to decide this week.
Inside: Coverage vs target, creation vs goal, aging, and a decision list.
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.
it reads the whole pipeline automatically, plus history for creation and movement.
pulls the target and the coverage ratio without a copy-paste.
tightens the aging and gone-quiet checks.
This was built for a B2B SaaS org running a staged pipeline. Set these to your stack:
Run any process you like. The skill reads coverage, creation, movement, and aging against your own targets, so point it at your numbers, not anyone else's.
| Set this | What it is | Default / Example |
|---|---|---|
| STAGE field | the opportunity stage | Opportunity.StageName |
| TARGET source | the number pipeline must cover | quotaplan →a BI tool |
| COVERAGE ratio | healthy pipeline-to-target multiple | 3x (re-tune to your win rate) |
| CREATION goal | new pipeline you need per period | your per-period target |
| AGING basis | days in stage that mean aging | 30 (re-tune) |
| DECISION window | close date that means act now | this week / this period |
Everything the skill does, in full.
Reads your open pipeline and answers the four questions a review asks: do we have enough coverage, are we creating enough, is it moving, and which deals need a decision now. It ends with a short list of deals to act on, not a wall of rows.
- 1Coverage vs target
Open pipeline in the period divided by the target it must cover. State the ratio and whether it clears your bar. Below coverage is the first thing a review needs to know, so it leads.
- 2Creation vs goal
New pipeline created this period against what you needed to create. Coverage can look fine while creation quietly dries up. This is the leading indicator, so it gets its own line.
- 3Movement
What changed since last time: deals that advanced, deals that slipped a stage, deals that pushed their close date. Movement is the difference between a live pipeline and a parked one.
- 4Aging
Deals sitting in one stage past the aging basis. An old deal is not a bad deal, but an old deal nobody has touched is. Show days in stage and days dark side by side.
- 5Deals that need a decision
The short list. Deals inside the decision window, deals that are stuck, deals that are aging and quiet. Each one gets a next move, not just a flag.
- Coverage is always shown as a ratio against a named target, never a raw dollar total alone.
- Creation is measured against a goal, not reported as a number floating on its own.
- "Aging" cites days in stage. A deal is not old because it feels old.
- The decision list is short and every entry has a move.
PIPELINE REPORT · This period Coverage $1.8M open vs $600K target · 3.0x, at bar Creation $210K created vs $250K goal · 84%, behind Movement 4 advanced, 2 slipped a stage, 3 pushed close date Aging 5 deals over 30 days in stage, 2 of them dark 14+ days Decide this week 1. Vertex ($67K, close Thu): champion quiet 12 days. Re-engage or slip it. 2. Blend Labs ($28K, in stage 34d): no next step. Set one or disqualify. 3. Northwind ($112K, dark 21d): last outreach or mark it lost.
The coverage ratio (3x), the aging basis (30 days), and the creation goal are defaults, not laws. They suited a mid-market SaaS cycle with a roughly one-in-three win rate. If yours differs, re-tune the multiple to your close rate. The logic does not change. The thresholds are yours.
Where an operator takes this next.
The weekly pull proves the four questions are the right ones. Here's the version that's ready before the review starts.
Four questions, asked the same way every week, is what makes the review fast.
A scheduled Claude task pulls the CRM Monday at 6am and has the report waiting before the meeting, no manual export.
Connect Slack so a deal crossing 30 days in stage posts to the owner the day it happens, instead of surfacing a week later in the report.
Connect a meeting or email tool so "champion quiet" reflects real last-touch data across email and calls, not just the CRM activity field.
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.