forecast
Skill0 starsChanged 7 months agoMITView on GitHub
Generate a weighted sales forecast with best/likely/worst scenarios, commit vs. upside breakdown, and gap analysis. Use when preparing a quarterly forecast call, assessing gap-to-quota from a pipeline CSV, deciding which deals to commit vs. call upside, or checking pipeline coverage against your number.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- mkaavish/forecastClaudeSkilltheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- skyf0xx/gambittheir own version, first seen Sep 30, 2026
- ai-analyst-lab/ai-analysttheir own version, first seen Sep 10, 2026
- mbwsims/claude-universetheir own version, first seen Apr 14, 2026
- KevinReactiv8/claude-skillsword for word, first seen Mar 30, 2026
Other versions7 projects use a version of this.
Word for word · 1
- KevinReactiv8/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 6
- anthropics/knowledge-work-plugins★ 35ksame name
- ai-analyst-lab/ai-analyst★ 304same name
- mbwsims/claude-universe★ 71same name
- microsoft/dataverse-business-skills★ 51same name
- skyf0xx/gambit★ 29same name
- mkaavish/forecastClaudeSkill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository91 other files it gives its agents.
- ab-testSkill
- adsSkill
- analyzeSkill
- brand-contextSkill
- brand-memorySkill
- brand-storySkill
- briefSkill
- campaignSkill
- communitySkill
- competeSkill
- contentSkill
- docxSkill
- pdfSkill
- pptxSkill
- scheduleSkill
- setup-coworkSkill
- skill-creatorSkill
- xlsxSkill
- cowork-plugin-customizerSkill
- create-cowork-pluginSkill
- croSkill
- emailSkill
- funnelSkill
- gtm-engineSkill
- gtmSkill
- hookSkill
- landingSkill
- brand-voiceSkill
- campaign-planningSkill
- competitive-analysisSkill
- content-creationSkill
- performance-analyticsSkill
- ab-test-setupSkill
- ad-creativeSkill
- ai-seoSkill
- analytics-trackingSkill
- churn-preventionSkill
- cold-emailSkill
- competitor-alternativesSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- email-sequenceSkill
- form-croSkill
- free-tool-strategySkill
- launch-strategySkill
- marketing-ideasSkill
- marketing-psychologySkill
- onboarding-croSkill
- page-croSkill
- paid-adsSkill
- paywall-upgrade-croSkill
- popup-croSkill
- pricing-strategySkill
- product-marketing-contextSkill
- programmatic-seoSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- schema-markupSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If a file is referenced: @$1
- Distinctive: line 80
Timeline: When does the period end? (e.g., "Q1 ends March 31")
- Distinctive: line 184
If you don't provide custom probabilities, I'll use:
- Distinctive: line 202
Use your actual historical win rates
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/forecast
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Generate a weighted sales forecast with risk analysis and commit recommendations.
Usage
/forecast [period]Generate a forecast for: $ARGUMENTS
If a file is referenced: @$1
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ FORECAST │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Upload CSV export from your CRM │
│ ✓ Or paste/describe your pipeline deals │
│ ✓ Set your quota and timeline │
│ ✓ Get weighted forecast with stage probabilities │
│ ✓ Risk-adjusted projections (best/likely/worst case) │
│ ✓ Commit vs. upside breakdown │
│ ✓ Gap analysis and recommendations │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: Pull pipeline automatically, real-time data │
│ + Historical win rates by stage, segment, deal size │
│ + Activity signals for risk scoring │
│ + Automatic refresh and tracking over time │
└─────────────────────────────────────────────────────────────────┘What I Need From You
Step 1: Your Pipeline Data
Option A: Upload a CSV Export your pipeline from your CRM (e.g. Salesforce, HubSpot). I need at minimum:
- Deal/Opportunity name
- Amount
- Stage
- Close date
Helpful if you have:
- Owner (if team forecast)
- Last activity date
- Created date
- Account name
Option B: Paste your deals
Acme Corp - $50K - Negotiation - closes Jan 31
TechStart - $25K - Demo scheduled - closes Feb 15
BigCo - $100K - Discovery - closes Mar 30Option C: Describe your territory "I have 8 deals in pipeline totaling $400K. Two are in negotiation ($120K), three in evaluation ($180K), three in discovery ($100K)."
Step 2: Your Targets
- Quota: What's your number? (e.g., "$500K this quarter")
- Timeline: When does the period end? (e.g., "Q1 ends March 31")
- Already closed: How much have you already booked this period?
Output
# Sales Forecast: [Period]
**Generated:** [Date]
**Data Source:** [CSV upload / Manual input / CRM]
---
## Summary
| Metric | Value |
|--------|-------|
| **Quota** | $[X] |
| **Closed to Date** | $[X] ([X]% of quota) |
| **Open Pipeline** | $[X] |
| **Weighted Forecast** | $[X] |
| **Gap to Quota** | $[X] |
| **Coverage Ratio** | [X]x |
---
## Forecast Scenarios
| Scenario | Amount | % of Quota | Assumptions |
|----------|--------|------------|-------------|
| **Best Case** | $[X] | [X]% | All deals close as expected |
| **Likely Case** | $[X] | [X]% | Stage-weighted probabilities |
| **Worst Case** | $[X] | [X]% | Only commit deals close |
---
## Pipeline by Stage
| Stage | # Deals | Total Value | Probability | Weighted Value |
|-------|---------|-------------|-------------|----------------|
| Negotiation | [X] | $[X] | 80% | $[X] |
| Proposal | [X] | $[X] | 60% | $[X] |
| Evaluation | [X] | $[X] | 40% | $[X] |
| Discovery | [X] | $[X] | 20% | $[X] |
| **Total** | [X] | $[X] | — | $[X] |
---
## Commit vs. Upside
### Commit (High Confidence)
Deals you'd stake your forecast on:
| Deal | Amount | Stage | Close Date | Why Commit |
|------|--------|-------|------------|------------|
| [Deal] | $[X] | [Stage] | [Date] | [Reason] |
**Total Commit:** $[X]
### Upside (Lower Confidence)
Deals that could close but have risk:
| Deal | Amount | Stage | Close Date | Risk Factor |
|------|--------|-------|------------|-------------|
| [Deal] | $[X] | [Stage] | [Date] | [Risk] |
**Total Upside:** $[X]
---
## Risk Flags
| Deal | Amount | Risk | Recommendation |
|------|--------|------|----------------|
| [Deal] | $[X] | Close date passed | Update close date or move to lost |
| [Deal] | $[X] | No activity in 14+ days | Re-engage or downgrade stage |
| [Deal] | $[X] | Close date this week, still in discovery | Unlikely to close — push out |
---
## Gap Analysis
**To hit quota, you need:** $[X] more
**Options to close the gap:**
1. **Accelerate [Deal]** — Currently [stage], worth $[X]. If you can close by [date], you're at [X]% of quota.
2. **Revive [Stalled Deal]** — Last active [date]. Worth $[X]. Reach out to [contact].
3. **New pipeline needed** — You need $[X] in new opportunities at [X]x coverage to be safe.
---
## Recommendations
1. [ ] [Specific action for highest-impact deal]
2. [ ] [Action for at-risk deal]
3. [ ] [Pipeline generation recommendation if gap exists]Stage Probabilities (Default)
If you don't provide custom probabilities, I'll use:
| Stage | Default Probability |
| Closed Won | 100% |
| Negotiation / Contract | 80% |
| Proposal / Quote | 60% |
| Evaluation / Demo | 40% |
| Discovery / Qualification | 20% |
| Prospecting / Lead | 10% |
Tell me if your stages or probabilities are different.
If CRM Connected
- I'll pull your pipeline automatically
- Use your actual historical win rates
- Factor in activity recency for risk scoring
- Track forecast changes over time
- Compare to previous forecasts
Tips
- Be honest about commit — Only commit deals you'd bet on. Upside is for everything else.
- Update close dates — Stale close dates kill forecast accuracy. Push out deals that won't close in time.
- Coverage matters — 3x pipeline coverage is healthy. Below 2x is risky.
- Activity = signal — Deals with no recent activity are at higher risk than stage suggests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

