Generate predictive pipeline forecasts with confidence intervals and scenario modeling for revenue planning
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill pipeline-forecasting
> Build accurate, data-driven revenue forecasts using historical conversion rates, deal velocity, and confidence-weighted projections.
Based on Clari's Revenue Operations methodology and Forrester's B2B Revenue Waterfall, combining:
| Claude Does | You Decide |
|-------------|------------|
| Calculates weighted pipeline by stage | Which deals to include/exclude |
| Applies historical conversion rates | Override factors for specific deals |
| Generates confidence intervals | Final commit number to leadership |
| Identifies forecast risks | Actions to close gaps |
| Models best/worst/likely scenarios | Which scenario to plan against |
I need a pipeline forecast for Q1. Here's our current pipeline:
[Paste pipeline data: Deal name, Stage, Value, Close Date, Rep]
Historical context:
- Average win rate: 25%
- Stage 3→Close rate: 45%
- Stage 4→Close rate: 70%
- Average sales cycle: 45 days
Target: $2.5M for Q1
Segment deals into:
Weighted Value = Deal Value × Stage Probability × Rep Factor
Stage Probabilities (adjust to your data):
- Stage 1 (Discovery): 10%
- Stage 2 (Qualification): 20%
- Stage 3 (Proposal): 40%
- Stage 4 (Negotiation): 70%
- Stage 5 (Verbal): 90%
Pipeline Coverage = Total Pipeline ÷ Target
- Healthy: 3-4x coverage
- At Risk: 2-3x coverage
- Critical: <2x coverage
Flag deals with:
Input:
Pipeline for Q1:
- Acme Corp: Stage 4, $150K, Jan 30, Rep: Sarah
- Beta Inc: Stage 3, $80K, Feb 15, Rep: Mike
- Gamma Ltd: Stage 2, $200K, Mar 1, Rep: Sarah
- Delta Co: Stage 4, $120K, Feb 28, Rep: Lisa
- Echo Systems: Stage 1, $500K, Mar 15, Rep: Mike
Target: $400K
Output:
## Q1 Pipeline Forecast
### Weighted Pipeline
| Deal | Stage | Value | Probability | Weighted |
|------|-------|-------|-------------|----------|
| Acme Corp | 4 | $150K | 70% | $105K |
| Delta Co | 4 | $120K | 70% | $84K |
| Beta Inc | 3 | $80K | 40% | $32K |
| Gamma Ltd | 2 | $200K | 20% | $40K |
| Echo Systems | 1 | $500K | 10% | $50K |
| **Total** | | **$1.05M** | | **$311K** |
### Scenario Analysis
- **Worst Case (Commit)**: $189K (Acme + Delta at 70%)
- **Likely Case**: $245K (Commit + 50% Best Case)
- **Best Case**: $361K (All weighted)
### Coverage Ratio
- Pipeline: $1.05M
- Target: $400K
- Coverage: 2.6x ⚠️ (At Risk - need 3x+)
### Risks Identified
1. ⚠️ Echo Systems ($500K) is Stage 1 with Mar close - unlikely
2. ⚠️ Gap of $155K between Likely ($245K) and Target ($400K)
### Recommendations
1. Pressure test Acme and Delta for verbal commits
2. Accelerate Beta Inc to Stage 4 this week
3. Add $200K+ new pipeline to reach 3x coverage
Input:
January pipeline by rep:
Sarah: $450K weighted, $280K commit
Mike: $320K weighted, $150K commit
Lisa: $280K weighted, $200K commit
Team target: $500K
Output:
## January Team Forecast
| Rep | Weighted | Commit | % to Target |
|-----|----------|--------|-------------|
| Sarah | $450K | $280K | 56% |
| Mike | $320K | $150K | 30% |
| Lisa | $280K | $200K | 40% |
| **Team** | **$1.05M** | **$630K** | **126%** |
### Forecast Summary
- **Team Commit**: $630K (126% of $500K target) ✅
- **Confidence**: HIGH - commit exceeds target
### Risk Watch
- Mike at 30% commit coverage - needs deal acceleration
- Sarah carrying most weight - concentration risk
## [Period] Revenue Forecast
**Generated:** [Date]
**Pipeline Cutoff:** [Date]
### Summary
- Target: $X
- Commit: $X (X% of target)
- Best Case: $X
- Coverage: Xx
### By Segment
[Table]
### Risks & Mitigations
[List]
### Actions This Week
[List]
deal-risk-scoring - Assess individual deal healthlead-scoring - Qualify top-of-funnelaccount-health - Customer retention signalsWorkflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility
Automate Cloudinary media management including folder organization, upload presets, asset lookup, transformations, and usage monitoring through natural language commands
You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.
Build and operate reproducible genomics workloads on DNAnexus with the dx CLI, dxpy, apps/applets, native workflows, dxCompiler, and Nextflow. Use for DNAnexus data transfers, dxapp.json development, execution monitoring, workflow import, and project automation.
Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
Take guia-matthieu/pipeline-forecasting from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.