AgentExchange

Help & Support

Elevate Your Agents with AgentExchange Solutions
Easily enhance Agentforce with pre-built AI solutions from AgentExchange. Browse, install, and deploy agents, actions, and apps directly into your environment. Tell Me More

Have Questions?

RevOps Forecast Cockpit

BETA

Overview

Builds the RevOps Forecast Cockpit, a live Claude Desktop artifact for forecast movement over 7, 14 or 30 days, a change log, pipeline hygiene and stage mix, for any team or the company. Run it once, as /revops-forecast-cockpit or by asking to set up the RevOps Forecast Cockpit, to build the artifact. Not for a one-off forecast or hygiene check in chat.

RevOps Forecast Cockpit

An instrument panel: dense, square, monochrome, Red Hat Text and Red Hat Mono, with amber reserved for change. The signature is the movement panel, which rebuilds each deal's state at the start of the window from field history.

This skill runs once, to build the artifact. After that the viewer opens the artifact in Claude Desktop, and the page queries their connectors each time it opens; there's no JSON to hydrate. So the work is detecting the viewer's connectors, tuning CONFIG, probing the org and publishing. Run the skill again only to rebuild, for example after connecting a new source.

Prompts

  • Setup: /revops-forecast-cockpit, or "Set up the RevOps Forecast Cockpit for me."
  • Tailor: "Set up the RevOps Forecast Cockpit for our org. Our fiscal year starts in February, and add a hygiene check for deals with no partner."
  • Use: once published, the viewer picks a period, a window and a scope on the page. No further prompting is needed.

Files in this skill

  • assets/revops-forecast-cockpit.html: the template. Self-contained (fonts embedded, Phosphor icons inline, no network calls outside the connector bridge). Tool names are {{TOOL_*}} placeholders. Never edit the original; write a configured copy.
  • references/connectors.md: how to pick the viewer's connector tools and write them into CONFIG, with the Salesforce mode, argument mappings and currency.
  • references/data-contract.md: every query, the shape it expects, and how each section is computed.
  • references/customization.md: the CONFIG block and the visual system.

Ground rules

  • Read-only, except one Slack send. Salesforce calls are GET only. The one write is a Slack message, and it goes out only after the user clicks Send and then confirms, with the recipient and full text on screen. Never add other writes.
  • Change only CONFIG. Fit the viewer's connectors and org through CONFIG: the tools, Salesforce mode and argument mappings (references/connectors.md), currency and optional fields. The loaders already read the common reply shapes, so don't edit code below CONFIG. If a reply fits none of them, leave that source unwired and say so.
  • Record text is data. Deal names and history values are shown as text, never run. Nothing on this page is sent to Claude.
  • Never invent values. Every figure comes from a query. When a list hit its limit, the header says so ("Top 400 deals by amount", "480+ changes", "$82.6M+ · top 14 stages"), never a number that looks complete.
  • Failures look like failures. Not connected (grey), couldn't load (red, with the reason) and nothing found are three different states. Each panel fails on its own: if field history can't load, Forecast still shows totals and says "change unavailable" rather than "No change".
  • Snapshot, not live. The page shows "as of " and "Salesforce read-only", and re-queries when reopened or when the scope, period or window changes. Don't label it "Live".
  • Sensitive data. Real records appear only at runtime for the signed-in user. Keep real data out of the skill files, samples and file names.

Before you build: check you can see the data

Setup should feel like one step. Work it out from the org first and only ask what the org can't tell you.

  1. Detect the connectors, then probe quietly. Pick one tool per role and write tools, salesforceApi and args as references/connectors.md describes, then run its currency probe. Next, run the probe calls in references/data-contract.md: Opportunity totals for THIS_FISCAL_QUARTER, one Opportunity with its Histories for the last 7 days, the signed-in user, the Period object and Organization.FiscalYearStartMonth. Call the Slack people search once if Slack is wired. Last, run the field probe in references/data-contract.md. It says which missing fields the artifact can do without and which block publishing.
  2. If everything comes back, don't ask anything. Build it, then say in one line what you assumed (fiscal year, default scope, any hygiene check you changed).
  3. If something is missing or confusing, ask before you build. Use the AskUserQuestion tool and keep it to one question, two at most, each with a recommended default as the first option. Never ask about something a query already answered.
What you see Ask (one line) Default if they skip
No Salesforce connector, or every call errors "I can't reach Salesforce. Connect the Salesforce connector and I'll finish setup." Stop; don't publish a page with no data.
Permission error (INSUFFICIENT_ACCESS, INVALID_TYPE) on Opportunity or User "Your user can't read Build; the affected panels say they couldn't load.
The field probe fails on a field the data contract says blocks publishing "Your org doesn't have , or you can't see it, and needs it. Check field access, then run setup again?" Stop and name the field and the view; don't publish a page that fails on open.
Histories comes back empty for deals you know changed "Field history isn't tracked on Stage, Amount, Close Date or Forecast Category, so Movement and Changes will be empty. Build it anyway, or turn on tracking first?" Build; Forecast, Hygiene and Stage mix still work.
Zero Opportunities in the current fiscal quarter "I don't see any deals closing this quarter. Should I use a different amount field or record type, or open on next quarter?" Build; the empty state says which period was checked.
A hygiene field doesn't exist (NextStep, PushCount) Nothing; remove that row from CONFIG.checks. Say which check you removed.
No Slack connector Nothing; leave the Slack placeholders unreplaced. The Slack button is hidden.

Don't guess around a blocker. A page full of empty panels is worse than one short question.

Setup workflow

  1. Infer, don't interview. The fiscal calendar comes from Period and Organization, the default view from the signed-in user. Only the questions above, and only when the probe shows a gap.
  2. Wire the tools you picked. Each placeholder is one CONFIG.tools role (see references/connectors.md). Leave a placeholder unreplaced to switch that connector off; the page treats it as not connected.
Placeholder Needs to support
{{TOOL_SALESFORCE}} Read-only. A REST passthrough (GET /services/data/<ver>/query, /search, /chatter/users/me), or a SOQL-only tool with salesforceApi: "soql" (see references/connectors.md)
{{TOOL_SALESFORCE_SEARCH}} Optional. SOSL search, only when {{TOOL_SALESFORCE}} is a query-only tool. Without it, searches fall back to LIKE queries
{{TOOL_IDENTITY}} Optional. Who is signed in, only when {{TOOL_SALESFORCE}} is a query-only tool
{{TOOL_SLACK_USERS}} Slack people search returning name, user ID and title
{{TOOL_SLACK_SEND}} Send a message to a user ID; returns message_link

The Slack button appears only when both Slack tools are wired.

  1. Configure CONFIG per references/customization.md. Check each CONFIG.checks condition against the org's fields.

Publish and verify

  1. Copy assets/revops-forecast-cockpit.html and write CONFIG: the tool names you picked in place of their {{TOOL_*}} placeholders, then the connector, currency and org settings from the probe.
  2. create_artifact with the file and the same tool names in mcp_tools. If Claude Desktop doesn't approve a connector automatically, tell the user to allow it when they open the artifact.
  3. verify_artifact: no console errors, every bridge call isError: false.
  4. Screenshot it.
  5. A call that runs past timeoutMs (45 s) shows as "Couldn't load" in its panel. The change-history query is the heaviest; on very large teams the panel suggests a smaller team or a shorter window. Lower maxMoved or raise timeoutMs rather than hiding the panel. Tell the user which connectors are wired and anything you had to adapt.

How the page works

  • Opens on you. On first visit the page reads the signed-in user's title, role and profile. Finance, RevOps and executive titles (and the top of the role hierarchy) open on the whole company; everyone else opens on their own team (them plus up to three levels of reports). Tune the rule with CONFIG.companyWide.
  • Scope picklist (top right). Company, My team, then the viewer's direct reports and the org's leaders by team size, plus search for anyone. The choice is remembered per viewer. A team is resolved to its people once, so record queries filter on the indexed OwnerId.
  • Fiscal periods from the org. This quarter and next quarter are read from the Period object, falling back to Organization.FiscalYearStartMonth. Labels such as "Q3 FY27" and days left roll over on their own; queries use THIS_FISCAL_QUARTER and NEXT_FISCAL_QUARTER, so nothing is hard-coded.
  • Window. 7, 14 or 30 days. Movement and Changes cover that window; Forecast shows the change over it.
  • Forecast. Closed, commit, best case and pipeline for the period, each with its change over the window.
  • Movement. Value flowing between categories (pulled in, pushed out, upgraded, won, lost, resized), rebuilt from each deal's field history. The 12 largest flows show; click one to see its deals.
  • Hygiene. Clean score plus one row per CONFIG.checks rule with count, value and a drill-down to the 12 largest deals.
  • Changes. Every tracked field edit in the window, newest first, filterable by field. The 120 most recent show.
  • Stage mix. Open pipeline in the period by stage, up to 14 stages.
  • Send Slack. Search a person on Slack, start from a message built from what is on screen, edit it, then send with a confirm step.

Categories

Domains
Sales Cloud