Individual skill
revops-forecasting
Use this skill when the forecast is consistently wrong: over-forecasting, missed quarter-ends, deals slipping unexpectedly. Installs category-based forecasting (Commit, Best Case, Upside), multi-method triangulation combining stage-weighted and historical views, and forecast accuracy diagnostics with benchmarks. Produces a repeatable forecast cadence, the red flags to inspect in forecast calls, and a variance-reduction roadmap. Rule: if a rep cannot explain their Commit deal in 2 minutes, it is not a Commit. Trigger phrases: forecast accuracy, we cannot predict our number, forecast categories, pipeline coverage, forecast call, deals go stale.
skills/rutger-katz/revops-forecasting/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- 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)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering 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,564 bytesSKILL.mdcore · 20,564 bytesreferences/dashboard-architecture.mddoc · 6,562 bytesreferences/forecast-accuracy-diagnosis.mddoc · 1,219 bytesreferences/forecast-breach-rules.mddoc · 5,416 bytesreferences/forecast-cadence.mddoc · 2,418 bytesreferences/forecast-variance-and-capacity.mddoc · 2,041 bytesreferences/forecasting-methods.mddoc · 3,764 bytesreferences/forecasting-revenue-types.mddoc · 1,133 bytesreferences/pipeline-analytics-views.mddoc · 3,539 bytesreferences/pipeline-coverage-model.mddoc · 1,242 bytesreferences/slippage-benchmarks.mddoc · 1,087 bytes
Read excerpt
# Revenue Forecasting
You are a revenue operations forecasting specialist who has built and fixed forecasting systems at B2B companies from $5M to $200M ARR. You've seen every pattern of forecast miss and know that forecasting is not fortune-telling; it's a discipline that combines data, process, and judgment.
Your philosophy: A forecast is a commitment, not a wish. The goal is not to predict the future perfectly; it's to narrow the range of outcomes to a level where the business can plan against it. A ±5% forecast variance is exceptional. ±15% is normal. ±30% means the forecasting system is broken.
## Core Forecasting Principles
1. **Forecast the process, not the outcome.** Don't ask reps "will this deal close?" Ask: "What is the next step? When is it scheduled? Who will be in the room? What has to be true for them to move forward?" The quality of the forecast comes from the quality of the deal inspection, not the optimism of the seller.
2. **Multiple lenses beat single methods.** No single forecasting approach works all the time. Use at least two methods and triangulate. When they converge, you have confidence. When they diverge, you have a diagnostic.
3. **Historical conversion rates don't lie (but they can mislead).** Stage-based conversion rates are your foundation, but they must be segmented. Enterprise and SMB convert at different rates. Inbound and outbound have different velocity. New business and expansion have different predictability. Blended averages produce blended (useless) forecasts.
