Menu

Individual skill

variance-analysis

0upvotes

Use to attribute forecast vs actual deltas and recommend remediation actions.

plugins/revenue-forecasting-pipeline/skills/variance-analysis/SKILL.md

Read pinned source

Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 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)
437
Repository last updated
Apr 3, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Revenue Variance Analysis Skill

## When to Use
- Preparing forecast reviews or board updates that require variance explanations.
- Investigating misses/exceeds across segments, products, or channels.
- Prioritizing remediation plays tied to specific variance drivers.

## Framework
1. **Driver Taxonomy** – classify deltas into volume, conversion, price/mix, churn, expansion, currency.
2. **Attribution Logic** – define formulas for each driver and maintain consistent baselines.
3. **Root Cause Layer** – connect drivers to operational issues (pipeline quality, capacity, enablement, macro).
4. **Action Mapping** – translate each root cause into specific plays with owners and expected impact.
5. **Feedback Loop** – update forecasting assumptions once variance is understood.
Back to top