Localized reading guide

forecastPurpose, usage and source

Generate the commit / best-case / pipeline narrative for a forecast call or a 1:1 with your manager - what's closing, what's at risk, what changed since last time. Use when the user asks "write my forecast", "forecast narrative", "prep for forecast call", "prep for my quarterly forecast call", "which deals should I commit vs. call upside", "forecast from this pipeline export", or "prep for my 1:1 with my manager".

Source retrieved: 2026-10-29

Source repository: anthropics/knowledge-work-plugins
SKILL.md: sales/skills/forecast/SKILL.md
Repository stars: 34,049
Repository updated: 2026-10-30
Categories: Business
Last collected: 2026-10-31 10:38 UTC+08:00

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

How the upstream workflow works

Step 1 - Ground

Check which tools are connected (plus any org facts the user or the project instructions already gave). Ground the stage-to-bucket mapping (which stages count as Commit vs Best Case vs Pipeline) and field names from the live crm schema and org context (inferred from what is connected or uploaded; if the answer depends on a fact no one has given, ask ONE question, use the answer for this conversation and suggest adding it to the project instructions; otherwise use a clearly labeled default and continue). If the schema carries a native forecast-category field, prefer it over stage inference. Every deal named links to its record.

Upstream passage · L36 ↗

Step 2 - Pull and bucket opportunities

From the CRM: open opps in scope closing this period (stage, forecast category, amount, close date, next step, last activity, owner), plus closed-won this period for the "in the bank" number. Bucket into Closed Won / Commit / Best Case / Pipeline.

Upstream passage · L44 ↗

Step 3 - Detect changes

If a prior snapshot was provided, diff it: deals that moved up, slipped out, were added, or were lost. Otherwise query opportunity history if the CRM exposes it, or skip this section and say so.

Upstream passage · L51 ↗

Upstream passage · ↗

tiers:
  files-only:   full narrative from an uploaded pipeline export; delta vs a pasted
                prior snapshot or the prior export (an opp missing from the newer
                export is "closed or removed - outcome not in the upload" unless a
                closed-opps export says won or lost - never assume won)
  read-only:    live crm pull + history-based deltas; category
                changes as checklist
  gated-writes: forecast-category updates via update-opportunity, as
                the user accepts, within connector permissions, verified
                per deal

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Pinned source: Read the original ↗
Source retrieved: 2026-10-29T09:32:23Z
Source commit: 2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256: 23b355ac3f994c729bf6271b7e0533dcf1ae2f4bd51104696624ef009cace37e

Back to the full Skill catalog