Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
onewave-ai avatar

Pipeline Health Analyzer

  • 251 installs
  • 237 repo stars
  • Updated July 15, 2026
  • onewave-ai/claude-skills

Analyzes sales pipeline health metrics, identifies bottlenecks, and provides recommendations to improve conversion.

About

The pipeline-health-analyzer skill evaluates sales pipeline data to diagnose health issues and conversion bottlenecks. It analyzes stage progression, deal velocity, win rates, and activity patterns to surface actionable insights. Ideal for sales managers who want data-driven visibility into pipeline performance.

  • Claude Code skill
  • Agent capability extension
  • Developer productivity
  • Workflow automation
  • Easy integration

Pipeline Health Analyzer by the numbers

  • 251 all-time installs (skills.sh)
  • +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #2,559 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill pipeline-health-analyzer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs251
repo stars237
Last updatedJuly 15, 2026
Repositoryonewave-ai/claude-skills

What it does

Analyzes sales pipeline health metrics, identifies bottlenecks, and provides recommendations to improve conversion.

Who is it for?

Sales managers and revenue operations teams

Skip if: Non-sales use cases

What you get

  • pipeline health analysis with recommendations

Files

SKILL.mdMarkdownGitHub ↗

Pipeline Health Analyzer

Identify pipeline risks, predict deal outcomes, and prescribe specific actions to accelerate stalled opportunities.

Contents

  • references/output-template.md - Full report skeleton to populate.
  • references/stage-analysis.md - Per-stage deep-dive patterns (Discovery, Demo, Proposal) and why deals stall.
  • references/forecasting.md - Forecast tables, probability calibration, AI re-scoring, scenario planning.
  • references/email-templates.md - Re-engagement email templates for stalled and dark deals.
  • references/examples.md - Trigger phrases, a worked example request, and best practices.

Workflow

1. Obtain the pipeline data. Request a CSV export with deal name, stage, value, rep, deal age, days in current stage, last activity date, close date, and probability if not provided. 2. Compute pipeline-by-stage metrics: deal count, total value, average deal size, average days in stage, and stage-to-stage conversion rates. Compare each against historical benchmarks. 3. Score each deal across six health dimensions: stage velocity, engagement level, qualification depth, stakeholder coverage, competitive position, and 30-day momentum. 4. Identify stalled and at-risk deals. Flag deals exceeding benchmark time in stage, with no recent activity, with slipped close dates, or with single-threaded contacts. 5. For each critical deal, determine the root cause and prescribe prioritized actions (immediate, this-week, backstop). Pull re-engagement copy from references/email-templates.md. 6. Build the forecast: categorize deals (Commit/Best Case/Pipeline/Upside), calculate weighted and risk-adjusted value, check probability calibration against actual close rates, and re-score outliers. Follow references/forecasting.md. 7. Model best-case, expected, and worst-case scenarios against quota, with a mitigation plan for the downside. 8. Produce strategic recommendations across immediate, short-term, and long-term horizons. 9. Assemble the report using references/output-template.md. Use plain status words (Healthy / At Risk / Critical) and trend words (Up / Flat / Down); never use emoji. 10. Close with the report card, next-review date, and week-over-week KPIs to track.

Operating Principles

  • Run weekly, not monthly; pipeline health degrades fast.
  • Base assessments on activity metrics, not rep intuition.
  • Disqualify dead deals early; a flowing pipeline is healthy.
  • Always end with concrete next steps, not just analysis.
  • Coach with the insights; do not weaponize them against reps.

See references/examples.md for trigger phrases, a worked example, and the full best-practices list.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.