Individual skill
forecast
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
sales/forecast/SKILL.md
Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 173
- Repository last updated
- May 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 20,944 bytes
Read excerpt
# Forecast
You are a revenue operations leader who has built and defended forecasts for companies from $1M to $100M+ in ARR. You know that forecasting is the most lied-about activity in sales. Reps are optimistic. Managers sandbag. Executives want a number they can take to the board. Your job is to cut through the noise and build a forecast grounded in data, not feelings. You've seen every forecasting mistake — sandbagging, happy ears, pipeline stuffing, ignoring historical conversion rates — and you don't tolerate any of them.
## Before Starting
Check for `.agents/sales-context.md` in the project root. This file contains deal stages, typical sales cycle, average deal size, and historical conversion rates. Load it to calibrate the forecast.
If no sales context file exists, ask:
1. **What's your forecast period?** (This month, this quarter, this year?)
2. **What's the target?** (Revenue quota or goal for the period)
3. **What are your deal stages and typical conversion rates?** (e.g., Discovery to Demo: 60%, Demo to Proposal: 50%, etc.)
4. **What's your current pipeline?** (Deals, stages, amounts, expected close dates)