pipeline-health-analyzer — Claude Code skill: deal analysis
Reads a deal export, flags stalled and at-risk opportunities, scores close probability and prescribes next actions.
npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a claude-codeWhat pipeline-health-analyzer does
The skill takes a CSV with deal name, stage, value, rep, deal age, days in current stage, last activity date, close date and probability. From that it computes pipeline-by-stage metrics: deal count, total value, average deal size, average days in stage and stage-to-stage conversion. Each number gets compared against historical benchmarks.
Every deal is scored across six health dimensions: stage velocity, engagement, qualification depth, stakeholder coverage, competitive position and 30-day momentum. Stalled and at-risk deals get flagged when they run past benchmark time in stage, go quiet, slip their close date or sit on a single contact. For critical deals the skill works out the root cause and ranks actions as immediate, this-week or backstop. Re-engagement copy comes from references/email-templates.md.
The forecast splits deals into Commit, Best Case, Pipeline and Upside, with weighted and risk-adjusted value, then models best-case, expected and worst-case against quota. The report is assembled from references/output-template.md using plain status words (Healthy / At Risk / Critical) and trend words (Up / Flat / Down). The author advises running it weekly rather than monthly, because pipeline health degrades fast. No export means the first step is a request for one.
What it helps with
- spot deals sitting in one stage past the benchmark
- compute stage-to-stage conversion and compare it to historical rates
- score close probability per deal and re-score the outliers
- build a forecast split into Commit, Best Case, Pipeline and Upside
- draft re-engagement emails for deals that have gone dark
Example prompts for the agent
- Here's the quarterly deal export — analyze pipeline health and show me the stalled deals
- Score close probability for every deal and re-score the ones that break calibration
- Build the quarterly forecast by category and model best-case, expected and worst-case
How to install pipeline-health-analyzer
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a claude-code2Manually: put the files in place
~/.claude/skills/pipeline-health-analyzer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pipeline-health-analyzer/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a codex2Manually: put the files in place
.agents/skills/pipeline-health-analyzer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a cursor2Manually: put the files in place
.cursor/skills/pipeline-health-analyzer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills pipeline-health-analyzer2Manually: put the files in place
.github/skills/pipeline-health-analyzer/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path pipeline-health-analyzerManually: put the files in place
.devin/skills/pipeline-health-analyzer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pipeline-health-analyzer
How do I install pipeline-health-analyzer in Claude?
Run npx skills add OneWave-AI/claude-skills --skill pipeline-health-analyzer -a claude-code. The skill lands at ~/.claude/skills/pipeline-health-analyzer/SKILL.md.
What does pipeline-health-analyzer do?
It computes pipeline-by-stage metrics, scores each deal across six health dimensions, flags stalled and at-risk opportunities and ranks follow-up actions. The output is a report with a forecast and scenario planning.
What data does the skill need?
A CSV export with deal name, stage, value, rep, deal age, days in current stage, last activity date, close date and probability. If probability is missing, the skill asks for it.
Source text
SKILL.md · MIT
--- name: pipeline-health-analyzer description: Analyze pipeline health, identify stalled deals, predict close probability, and suggest actions to move deals forward. Improves forecast accuracy and prevents revenue leakage. Use when deals get stuck or forecast accuracy is poor. --- # 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.
© OneWave-AI · MIT · OneWave-AI/claude-skills