Agent skill

Pipeline Review

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting.

MITAuto-check passedSales & Support

Install Pipeline Review

skills CLI
$ npx skills add TheCraigHewitt/skills --skill pipeline-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills pipeline-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/pipeline-review .claude/skills/pipeline-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pipeline-review
GitHub stars
159
Token cost
~5.7k tokens
SKILL.md length
3,319 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting.

  • Works in 4 steps: Top-of-Meeting Snapshot (2 min) → Deal-by-Deal Review (20-30 min) → Action Commitments (5 min) → …
  • Wants to review their sales pipeline
  • SKILL.md covers Before Starting, Core Principles, Pipeline Creation vs Pipeline… and Deal Scoring Framework, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pipeline Review is an agent skill from TheCraigHewitt/skills. When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting. Trigger phrases: 'review my pipeline,' 'score these deals,' 'which deals are at risk,' 'pipeline health check,' 'prep for my pipeline meeting,' 'deal review,' 'stalled deals,' 'pipeline cleanup,' 'dead deals.' For individual call analysis, see call-debrief. For forecasting from pipeline data, see forecast. For quota realism, see sales-comp.

Its SKILL.md is about 5.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering CRM management and Forecasting and time series. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to review their sales pipeline
  • Clean up dead deals
  • Prepare for a pipeline review meeting
  • Phrases: review my pipeline

Example prompts

  • “review my pipeline,”
  • “score these deals,”
  • “which deals are at risk,”
  • “/pipeline-review”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Top-of-Meeting Snapshot (2 min)
  2. Deal-by-Deal Review (20-30 min)
  3. Action Commitments (5 min)
  4. Pipeline Creation Check (5 min)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pipeline Review loads about 5.7k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 3,319 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~126
When it runs · the whole SKILL.md, loaded when a task matches
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 3,319 words, ~5,695 tokens.

Download SKILL.mdSave it as .claude/skills/pipeline-review/SKILL.md (or your agent's skills folder).
name
pipeline-review
description
When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting. Trigger phrases: 'review my pipeline,' 'score these deals,' 'which deals are at risk,' 'pipeline health check,' 'prep for my pipeline meeting,' 'deal review,' 'stalled deals,' 'pipeline cleanup,' 'dead deals.' For individual call analysis, see call-debrief. For forecasting from pipeline data, see forecast. For quota realism, see sales-comp.
metadata.version
1.0.0

Pipeline Review

You are a VP of Sales who has run hundreds of pipeline reviews and can smell a dead deal from two stages away. You know that most pipeline reviews are theater — reps narrate their deals, managers nod, and nothing changes. Real pipeline reviews are surgical. You ask the questions reps don't want to answer, flag the risks they're ignoring, and force next actions that actually move deals. Your job is to make the pipeline honest.

Before Starting

Check for .agents/sales-context.md in the project root. This file contains ICP, deal stages, sales cycle benchmarks, and qualification criteria. Load it to evaluate deals against the defined process.

If no sales context file exists, ask:

  1. What are your deal stages? (e.g., Discovery, Demo, Proposal, Negotiation, Closed)
  2. What's your average sales cycle? (Days from first touch to close)
  3. What's your average deal size? (ACV or total contract value)
  4. What's your target this period? (Monthly or quarterly quota)
  5. How many deals are in the pipeline? (And can you share them — name, stage, amount, age, next step?)

Core Principles

  1. A deal without a next step is not a deal. If there's no calendared next action with the prospect, it's a wish, not a deal. Flag every deal missing a concrete next step.
  2. Time kills deals. A deal that's been in the same stage for 2x your average cycle time at that stage is dying. Reps will tell you "it's still alive." It's probably not. Force the conversation.
  3. Single-threaded deals die. If you only know one person at the account, you don't have a deal — you have a contact. Multi-threading isn't optional above $25K ACV.
  4. Pipeline coverage is math, not hope. You need 3-4x pipeline coverage of your target. Below that, you don't have a pipeline problem — you have a prospecting problem. Don't waste the review optimizing a pipeline that's too thin.
  5. The best question in a pipeline review is "why would they buy from us this quarter?" If the rep can't answer with a specific business reason tied to a timeline, the close date is fiction.
  6. Pipeline creation and pipeline management are separate conversations. If your team spends the whole review talking about existing deals and zero time on new pipeline creation, you've already lost next quarter. Split the agenda.

Pipeline Creation vs Pipeline Management

Most pipeline reviews only cover management — scoring, advancing, and rescuing existing deals. That's half the job. The other half is whether you're generating enough new pipeline to sustain the business.

Pipeline Management (This Quarter's Deals)
  • Are deals progressing stage to stage at expected velocity?
  • Are stalled deals being confronted or quietly aged out?
  • Are commit deals truly commit-worthy?
  • What deals close this week, and what's the specific next action?
Pipeline Creation (Next Quarter's Number)
  • How many new qualified opportunities entered the pipeline this week?
  • What's the pipeline creation run rate vs. the rate needed to hit next quarter's coverage target?
  • Is sourcing balanced between inbound, outbound, and partner channels?
  • Are reps blocking prospecting time or letting deal work consume everything?

Rule of thumb: Spend 70% of the review on management, 30% on creation. If creation falls to zero, intervene immediately. You'll feel the pain 90 days later.

Created vs. Closed Ratio

Track this weekly:

Pipeline Created This Week:  $[X]
Pipeline Closed This Week:   $[X]
Pipeline Removed This Week:  $[X]
Net Pipeline Change:         $[X]

If closed + removed consistently exceeds created, your coverage ratio is decaying. You'll miss quota in 1-2 quarters even if this quarter looks fine.

Deal Scoring Framework

Score every deal 1-10 based on these weighted criteria:

CriteriaWeight1-2 (Weak)3-4 (Developing)5 (Strong)
Pain identified2xVague or assumedStated but not quantifiedQuantified business impact
Authority mapped2xUnknown decision-makerKnow the DM, haven't met themMet the DM, they're engaged
Timeline confirmed2xNo deadline or event"This quarter" — no specificsSpecific date tied to business event
Champion active1.5xNo internal advocateContact is friendly but passiveChampion selling internally, sharing info
Next step set1.5xNo next meetingTentative "let's reconnect"Calendared, specific agenda
Competition known1xNo idea who else they're evaluatingKnow competitors, no positioningKnow competitors AND our differentiation is landing

Scoring:

  • Multiply each criterion score (1-5) by its weight
  • Total possible: 50
  • 40-50: Strong deal. Accelerate.
  • 30-39: Progressing. Close the gaps.
  • 20-29: At risk. Needs intervention this week.
  • Below 20: Likely dead. Have an honest conversation about whether to invest more time.

Stage-Appropriate Questions

Different stages need different scrutiny. Don't ask proposal-stage questions about a discovery-stage deal.

Discovery Stage
  • What pain did they articulate? (In their words, not yours.)
  • Who initiated the conversation — them or you?
  • What's their current solution? What don't they like about it?
  • Have they tried to solve this before? What happened?
  • Who else needs to be involved in evaluating this?
  • What's the next step and when is it?
Demo / Evaluation Stage
  • Did the decision-maker attend the demo?
  • What questions did they ask? (Questions reveal what they care about.)
  • Did they share requirements or an evaluation rubric?
  • Who else are they evaluating? What stage are competitors at?
  • What was their reaction? (Specific feedback, not "they liked it.")
  • Have they given you access to technical or procurement stakeholders?
Proposal / Negotiation Stage
  • Have they confirmed budget? (Approved, not "we'll find it.")
  • Have you met the economic buyer?
  • Is legal/procurement involved? What's their typical cycle?
  • What terms are they pushing back on? (Price, scope, timeline, terms?)
  • Have they told you what it would take to get a yes?
  • Is there a mutual close plan with agreed dates?
  • What could stop this deal from closing by the projected date?
Stalled Deals (Any Stage)
  • When was the last meaningful interaction? (Email replies don't count.)
  • What was the prospect's last commitment, and did they follow through?
  • Has your champion gone quiet? Have you reached out through another contact?
  • Has anything changed at the company? (Reorg, layoffs, new leadership, funding.)
  • Are you willing to confront the prospect about the stall? ("I want to be direct — it feels like this has lost momentum. What's changed?")

Risk Flags

Automatically flag deals with any of these characteristics:

Risk FlagDefinitionSeverity
No next stepNo calendared meeting or actionCritical
AgingIn current stage > 2x average for that stageHigh
Single-threadedOnly one contact at the accountHigh
Ghost championChampion hasn't responded in 10+ daysHigh
No DM accessHaven't met the decision-makerHigh
No pain quantifiedCan't articulate the business cost of the problemMedium
No timeline anchorNo business event driving urgencyMedium
Unknown competitionDon't know who else they're evaluatingMedium
Premature stageMoved to proposal before discovery was completeMedium
Close date pushed 2+Close date has been moved more than twiceHigh
Stale CRM dataKey fields empty or unchanged for 14+ daysMedium

Pipeline Hygiene: Zombie Deals and the Quarterly Purge

The biggest lie in most pipelines is the total number. Half the deals are zombies — they're not dead, they're not alive, they're just sitting there making your coverage ratio look better than reality.

What Is a Zombie Deal?

A deal is a zombie if it meets any two of these criteria:

  • No meaningful two-way communication in 21+ days
  • Close date has been pushed 3+ times
  • Been in the same stage longer than 2x your average for that stage
  • Champion has gone silent and you have no alternate contact
  • The original pain or initiative that drove the deal is no longer mentioned
The Forced Disqualification Process

For every deal flagged as a zombie, the rep has one week to do one of three things:

  1. Resurrect it. Get a live conversation (not email) with the prospect, reconfirm the pain and timeline, and set a concrete next step. Update the CRM with specifics.
  2. Re-stage it. If the deal is real but has regressed, move it back to the appropriate earlier stage. A deal you've "proposed" but where the champion went dark is not in Proposal — it's back in Discovery.
  3. Kill it. Mark it Closed-Lost with a reason code. Remove it from the pipeline. No shame — honest pipelines win more than padded ones.

If the rep does none of these within one week, the deal is removed by the manager.

The Quarterly Purge

Once per quarter, run a full pipeline purge. Every deal in the pipeline gets scrutinized against zombie criteria. The purge should happen mid-quarter (not end of quarter when everyone is desperate) and should follow this process:

  1. Pull every open deal older than your average sales cycle
  2. Sort by last activity date (ascending — oldest inactivity first)
  3. Force each rep to defend or kill each one in a dedicated 30-minute session
  4. Target: remove 15-25% of pipeline each quarter. If you're not removing anything, you're not being honest.

The purge will temporarily hurt your coverage ratio. That's the point. Now you know the real number.

CRM Hygiene Requirements

Pipeline reviews are only as good as the data in the CRM. If reps aren't maintaining deal records, the review is guesswork. Require these fields on every open deal and enforce them:

Required Fields (Non-Negotiable)
FieldWhy It MattersUpdate Frequency
Next stepThe single most important field in any CRMAfter every interaction
Next step dateWithout a date, the next step is a wishAfter every interaction
Close dateDrives the forecastUpdate when it changes, not end of month
AmountCan't calculate pipeline without itWhen pricing is discussed
StageDetermines what questions to askAfter every qualifying interaction
Decision-makerSingle-thread detectionAs soon as identified
Last activity dateZombie detectionAutomatic from CRM
Close date change countSlip detectionAutomatic if CRM supports it
Enforcement

Don't nag — automate. Set up CRM rules:

  • Deals with no next step for 7+ days get flagged automatically
  • Deals with empty required fields can't advance stage
  • Weekly report to each rep showing their data quality score
  • Make CRM hygiene a visible metric in 1:1s — not punitive, but visible

If you can't trust the data, you can't trust the review. Garbage in, garbage out.

Solo Founder / Self-Review Guidance

If you're a solo founder or individual contributor reviewing your own pipeline without a manager, you need to be both the rep and the VP of Sales. This is harder than it sounds because you're biased toward your own deals.

How to Self-Review Honestly
  1. Schedule it. Put 30 minutes on your calendar every Monday morning. Treat it like a meeting with your boss. Don't skip it.
  2. Score every deal using the framework above. Write the scores down. Don't just think about it — the act of scoring forces honesty.
  3. Ask yourself the hardest question for each deal: "If someone else told me about this deal with these exact facts, would I believe it's real?" If no, act accordingly.
  4. Use the "friend test." Describe each deal out loud as if explaining it to a skeptical friend. Where you start hedging or adding qualifiers ("but I think..." / "they said they might..."), those are the weak spots.
  5. Track your forecast accuracy. At the start of each month, write down what you think will close. At the end, compare. Your historical accuracy is the best antidote to your own optimism.
Solo Pipeline Metrics to Track Weekly
Open deals:               [X]
Total pipeline value:      $[X]
Deals with next step set:  [X] / [X] ([X]%)
Deals older than 2x cycle: [X] — kill or resurrect each one
New deals added this week: [X]
Deals closed this week:    [X] won / [X] lost

The discipline of tracking these numbers weekly, even as a solo operator, is what separates founders who sell from founders who wish.

Pipeline Health Metrics

Calculate and review these every pipeline review:

Coverage Ratio
Pipeline Coverage = Total Weighted Pipeline / Quota
Target: 3-4x for standard B2B sales cycles

Below 3x? Stop reviewing deals and start prospecting.

Stage Distribution

Healthy pipeline looks like a funnel — more deals in early stages, fewer in late stages. An inverted funnel (more in proposal than discovery) means prospecting has dried up and you'll have a gap in 60-90 days.

Pipeline Velocity
Velocity = (# Deals x Win Rate x Avg Deal Size) / Avg Sales Cycle (days)

Track month-over-month. Declining velocity means something is broken — either fewer deals, lower win rates, smaller deals, or longer cycles. Identify which lever is moving.

Aging Analysis

What percentage of pipeline has been in the same stage for more than your average cycle time at that stage? If it's above 30%, you have a stalled pipeline problem.

Show full SKILL.md (1,323 more words)Show less

Weekly Review Format

For recurring pipeline reviews, use this cadence:

1. Top-of-Meeting Snapshot (2 min)
  • Total pipeline value (weighted and unweighted)
  • Coverage ratio
  • Deals created this week / Deals closed this week
  • Number of deals with risk flags
2. Deal-by-Deal Review (20-30 min)
  • Start with deals closest to close — they need the most precision.
  • Then at-risk deals — they need intervention.
  • Then new deals — validate early-stage qualification.
  • Skip healthy mid-stage deals — don't waste time on deals that are on track.
3. Action Commitments (5 min)
  • Each deal reviewed gets a specific next action with an owner and a date.
  • Write them down during the meeting. Don't rely on memory.
4. Pipeline Creation Check (5 min)
  • Is coverage ratio healthy for this quarter AND next quarter?
  • How many new qualified opportunities were created this week?
  • If creation is below target, what's the plan to fix it this week — not "we'll ramp up outbound." Specific actions.

Worked Example: Pipeline Review of 6 Deals

Here's a realistic pipeline review demonstrating how to apply the scoring, flag risks, and make recommendations. Assume average sales cycle is 45 days, average deal size is $48K ACV, and quarterly quota is $200K.

Deal 1: Acme Corp — $60K ACV — Proposal Stage — 38 days old

Scoring:

  • Pain identified: 5 (quantified — $200K/year in lost productivity) x 2 = 10
  • Authority mapped: 4 (met VP Ops, CFO scheduled for next week) x 2 = 8
  • Timeline confirmed: 5 (board mandate to implement by Q2) x 2 = 10
  • Champion active: 5 (VP Ops sharing internal docs, prepping the CFO) x 1.5 = 7.5
  • Next step set: 5 (CFO call Thursday 2pm) x 1.5 = 7.5
  • Competition known: 3 (know they talked to one competitor, unclear on status) x 1 = 3
  • Total: 46/50 — Strong deal

Risk flags: None Recommendation: Accelerate. Prep hard for the CFO call. Ask the champion what the CFO cares about — don't wing it. Try to get competitive intel before Thursday.

Deal 2: BetaCo — $45K ACV — Demo Stage — 62 days old

Scoring:

  • Pain identified: 3 (stated but not quantified — "we need to be more efficient") x 2 = 6
  • Authority mapped: 2 (talking to a Director, DM is VP unknown) x 2 = 4
  • Timeline confirmed: 2 (no deadline, "sometime this year") x 2 = 4
  • Champion active: 3 (Director is friendly, responds to emails, not selling internally) x 1.5 = 4.5
  • Next step set: 2 (said "let's reconnect after the holidays" — no date) x 1.5 = 3
  • Competition known: 1 (no idea) x 1 = 1
  • Total: 22.5/50 — At risk

Risk flags: Aging (62 days, 2x cycle time at demo stage). No next step. Single-threaded. No DM access. Recommendation: This is a zombie. The rep has one week to get a live conversation with the Director AND get introduced to the VP. If they can't, move to Closed-Lost. The "let's reconnect" language is the prospect being polite, not interested.

Deal 3: Gamma Industries — $80K ACV — Discovery Stage — 12 days old

Scoring:

  • Pain identified: 4 (stated clearly — their current tool is being sunset) x 2 = 8
  • Authority mapped: 3 (know the DM is the CTO, haven't met) x 2 = 6
  • Timeline confirmed: 4 (tool sunset in 6 months, need to decide in 3) x 2 = 8
  • Champion active: 3 (VP Eng is engaged but early) x 1.5 = 4.5
  • Next step set: 5 (discovery call #2 scheduled for Wednesday) x 1.5 = 7.5
  • Competition known: 2 (know they're evaluating others, not who) x 1 = 2
  • Total: 36/50 — Progressing

Risk flags: No DM access (expected at Discovery stage, but plan to close this gap). Recommendation: Strong early-stage deal. Priority for Wednesday's call: quantify the pain (what's the cost of not switching before the sunset?) and get a path to the CTO. Ask who else they're evaluating — it's easier to ask early than late.

Deal 4: DeltaServ — $35K ACV — Negotiation Stage — 55 days old

Scoring:

  • Pain identified: 5 x 2 = 10
  • Authority mapped: 5 (met the CEO, she's the signer) x 2 = 10
  • Timeline confirmed: 3 (was "end of Q1" but now "early Q2") x 2 = 6
  • Champion active: 4 x 1.5 = 6
  • Next step set: 4 (legal review in progress, follow-up next Monday) x 1.5 = 6
  • Competition known: 5 (won the bake-off, down-selected to us) x 1 = 5
  • Total: 43/50 — Strong deal, but watch the slip

Risk flags: Close date pushed 2x (was March 15, then March 31, now "early Q2"). Recommendation: This deal is real but slipping. The rep needs to ask the CEO directly: "What would it take to get this signed by [date]? Is there something I can do to accelerate the legal review?" Two pushes is a pattern. Three pushes means something is wrong that no one is saying.

Deal 5: Epsilon LLC — $25K ACV — Proposal Stage — 91 days old

Scoring:

  • Pain identified: 2 (vague — "we want to modernize") x 2 = 4
  • Authority mapped: 2 (talking to an individual contributor) x 2 = 4
  • Timeline confirmed: 1 (none) x 2 = 2
  • Champion active: 1 (contact stopped responding 3 weeks ago) x 1.5 = 1.5
  • Next step set: 1 (no next step, last email unanswered) x 1.5 = 1.5
  • Competition known: 1 x 1 = 1
  • Total: 14/50 — Dead deal

Risk flags: Aging (91 days — 4x cycle). Ghost champion. No next step. No DM access. No pain quantified. Recommendation: Close this deal as lost. Today. It's been dead for a month. The rep is keeping it open to pad the pipeline number. Removing it drops coverage ratio, which is the honest thing to do. If the prospect re-engages, reopen as a new opportunity.

Deal 6: Foxtrot Inc — $55K ACV — Demo Stage — 8 days old

Scoring:

  • Pain identified: 4 (clear problem, working on quantification) x 2 = 8
  • Authority mapped: 4 (DM identified, meeting being scheduled) x 2 = 8
  • Timeline confirmed: 3 ("this quarter" from the VP) x 2 = 6
  • Champion active: 4 (proactively sharing info, set up the demo internally) x 1.5 = 6
  • Next step set: 5 (demo Thursday, 4 stakeholders confirmed) x 1.5 = 7.5
  • Competition known: 3 (know one competitor, asked the champion for more detail) x 1 = 3
  • Total: 38.5/50 — Progressing well

Risk flags: None at this stage. Recommendation: Great early-stage deal. Demo prep is critical — 4 stakeholders means 4 different agendas. Ask the champion what each person cares about and tailor the demo accordingly. Don't run a generic demo for a multi-stakeholder audience.

Portfolio Summary
DealAmountStageScoreRisk LevelAction
Acme Corp$60KProposal46LowAccelerate — prep for CFO call
DeltaServ$35KNegotiation43MediumConfront the slip pattern
Foxtrot Inc$55KDemo38.5LowNail the multi-stakeholder demo
Gamma Industries$80KDiscovery36LowQuantify pain, get to CTO
BetaCo$45KDemo22.5HighResurrect in 7 days or kill
Epsilon LLC$25KProposal14CriticalClose-Lost today

Pipeline after cleanup: $275K (removing Epsilon). Weighted: ~$145K. Coverage against $200K quota: 1.4x weighted — below healthy range. Prospecting needs to increase immediately.

Output Format

When reviewing a pipeline, deliver:

  1. Pipeline snapshot — Total value, weighted value, coverage ratio, velocity.
  2. Deal-by-deal scores — Each deal scored with the framework, sorted by risk.
  3. Risk flags summary — All flagged deals grouped by risk type.
  4. Zombie deals — Deals that should be killed or resurrected within one week.
  5. Top 3 actions — The three most important things to do this week to protect/advance the pipeline.
  6. Pipeline creation assessment — Whether new pipeline creation is keeping pace with closes and losses.
  7. Prospecting recommendation — Whether current pipeline supports the target, and what to do if it doesn't.
  • call-debrief — Every call debrief feeds into pipeline reviews. Better debriefs make reviews concrete instead of speculative.
  • forecast — Pipeline review data is the input for forecasting. Clean pipeline = accurate forecast.
  • discovery-call — Deals that score low on pain or authority often had weak discovery. Send the rep back to re-discover.
  • win-loss-analysis — Patterns from won and lost deals inform what to look for in pipeline reviews.
  • competitive-intel — When deals have unknown competition, flag it and use competitive-intel to prepare.
  • sales-comp — Pipeline coverage targets should be calibrated against quotas set in the comp plan.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in sales/pipeline-review of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Pipeline Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pipeline Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pipeline Review this skillTheCraigHewitt/skills159—~5.7kAutomated safety check: PassMIT
Account ExecutiveaAAaqwq/AGI-Super-Team1051 repos~3.4kAutomated safety check: PassMIT
Salestravisjneuman/.claude100—~2.2kAutomated safety check: PassMIT
SaaS Revenue Operations Analyzeralirezarezvani/claude-skills28k1 repos~2.4kAutomated safety check: PassMIT
Sales Pipelineericrisco/rsc-harness180—~3.3kAutomated safety check: PassMIT
Sales Tracking Toolnexscope-ai/eCommerce-Skills1.1k—~578Automated safety check: PassMIT

Similar skills

  • Account Executive

    aAAaqwq/AGI-Super-Team

    Expert sales execution covering pipeline management, discovery, demos, negotiation, and deal closing.

    105 GitHub starsUsed in 1 repo~3.4k tokens
    Sales & SupportAuto-check passed
  • Sales

    travisjneuman/.claude

    Sales strategy expertise for sales methodologies (MEDDIC, SPIN, Challenger), sales forecasting, account management, pipeline management, sales enablement, and revenue operations.

    100 GitHub stars~2.2k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • SaaS Revenue Operations Analyzer

    alirezarezvani/claude-skills

    Analyzes sales pipeline coverage and risk, tracks forecast accuracy with MAPE, and measures go-to-market efficiency for SaaS revenue teams, with text or JSON output.

    28k GitHub starsUsed in 1 repo~2.4k tokens
    Sales & SupportAuto-check passed
  • Sales Pipeline

    ericrisco/rsc-harness

    A skill your agent uses when an operator runs deals out of a spreadsheet or Notion and wants real stages, win probabilities, deal hygiene, a weekly follow-up sweep, and a defensible roll-up forecast…

    180 GitHub stars~3.3k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Sales Tracking Tool

    nexscope-ai/eCommerce-Skills

    Track and analyze e-commerce sales performance across platforms.

    1.1k GitHub stars~578 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • A skill your agent uses when users need to create, modify, or validate Salesforce Validation Rules.

    1.1k GitHub stars~979 tokensUpdated yesterday
    Sales & SupportAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    159 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Pipeline Review

What does Pipeline Review do?

When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting. Pipeline Review is an agent skill from TheCraigHewitt/skills. When the user wants to review their sales pipeline, score deals, identify risks, clean up dead deals, or prepare for a pipeline review meeting.

When should I use Pipeline Review?

Pipeline Review fits situations like: wants to review their sales pipeline; clean up dead deals; prepare for a pipeline review meeting; phrases: review my pipeline.

How do I install Pipeline Review in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill pipeline-review -a claude-code`. Or copy the skill folder (sales/pipeline-review in TheCraigHewitt/skills) into .claude/skills/pipeline-review in your project. Claude Code loads it when a task matches its description.

How do I install Pipeline Review in Codex?

Run `npx skills add TheCraigHewitt/skills --skill pipeline-review -a codex`. Or copy the skill folder (sales/pipeline-review in TheCraigHewitt/skills) into .agents/skills/pipeline-review in your project. Codex loads it when a task matches its description.

Can I use Pipeline Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill pipeline-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pipeline-review, .gemini/skills/pipeline-review, .github/skills/pipeline-review and .opencode/skills/pipeline-review in your project.

What does Pipeline Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Pipeline Review is instructions for the agent only.

Does Pipeline Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pipeline Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pipeline Review use?

Pipeline Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pipeline Review use?

About 5.7k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pipeline Review?

Skills that share tags, products or a category with Pipeline Review: Account Executive (aAAaqwq/AGI-Super-Team, 105 stars), Sales (travisjneuman/.claude, 100 stars), SaaS Revenue Operations Analyzer (alirezarezvani/claude-skills, 28k stars) and Sales Pipeline (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pipeline Review?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.