forecast

A monday.com dashboard that groups sales opportunities by stage and expected closing month into committed, best-case, pipeline, and closed-won views.

In plain words
What is it for?
Use it to review a sales forecast for a chosen period, such as a quarter or the next 90 days, and optionally share the dashboard or flag missing deal information.
Why use it?
It replaces the manual process of exporting sales data and building a new spreadsheet summary for each forecast review.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/mondaycom/mcp/forecast
Any agent
npx skills add mondaycom/mcp --skill forecast
Clone the repo
git clone --depth 1 https://github.com/mondaycom/mcp

Made for: Claude Code, Codex.

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00102 $0.03545
Opus 5 $0.00051 $0.01773
Sonnet 5 $0.00020 $0.00709
Haiku 4.5 $0.00010 $0.00354

Measured 2d ago against content hash 6b3531b18408, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

forecast scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/monday-crm/skills/forecast/SKILL.md · 278 lines

How it starts

The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Forecast Dashboard

Builds a native monday dashboard that renders the pipeline as a forecast — committed / best-case / pipeline / closed-won, grouped by stage × close month. Replaces the "export to CSV and pivot it" pattern that sales ops leaders do manually every Monday.

Flow: Trigger → Gather → Synthesize → Publish (α, default) → Share (β, opt-in) → Proactive extension (opt-in, hygiene fix).

Input

  • Optional: board name / ID + forecast period (e.g., "Q2 2026", "next 90 days").
  • Optional: pre-declared mode (Default / Silent / Proactive).

Output

  • α (default): A native monday create_dashboard with widgets per bucket + URL.
  • β (Share): Viewer-permission grant to sales leader via all_monday_api + create_notification.
  • Proactive extension: Hygiene fix — if a non-closed deal is missing close date, change_item_column_values (with batched user confirm) to set a placeholder OR post a prompt update asking the owner to fill it. Missing-amount items are flagged in the dashboard description and a hygiene update is posted on the item, but the amount column itself is never written (forecast integrity rail).

Knowledge

  • Bucket definitions: closed-won / committed / best-case / pipeline (§ Step 5).
  • Shared artifact conventions (see Shared patterns section below).

Tools (MCP)

  • get_user_context, list_workspaces, search — board resolution.
  • get_board_info, get_column_type_info — schema + column types (stage/amount/close-date/forecast-category).
  • get_board_items_page — paginated pull.
  • board_insights — aggregate fallback.
  • create_dashboard, create_widget — α publish.
  • create_doc — fallback for non-admins (see Error handling).
  • create_notification, list_users_and_teams — β share.
  • create_column — add a forecast-category column only if required to render the dashboard.
  • change_item_column_values — proactive hygiene fix.
  • all_monday_api — escape hatch for dashboard permissions, idempotency GraphQL query, and doc updates.

Read the full file on GitHub · 278 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 278 lines · 102 tokens per session scan A 6b3531b18408

Subscribe to this mod's changes

forecast is a skill published in the GitHub repository mondaycom/mcp (421 stars, last pushed 7d ago), licensed MIT. It adds 102 tokens to every session and 3,545 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

paseo

Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.

getpaseo/paseo · 26 tokens

github-fix-issue

Analyze and fix GitHub issues in the current repository, including issue research, scoped implementation, and testing. Use when the user asks to fix, investigate, or work on a GitHub issue by number or URL. Create branches, commits, pushes, or pull requests only when the user explicitly requests those delivery actions.

feiskyer/codex-settings · 69 tokens

backlog

Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…

sammcj/agentic-coding · 182 tokens

skill-intake

Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted.

nyldn/claude-octopus · 34 tokens

goal-loop

Bootstrap a goal-driven self-improving AutoNudge loop. Give it a goal + anchor directory; it generates LOOP.md + GOAL.md + kanban board, then you write the Definition of Done and arm the loop. The running agent manages the board autonomously: finds issues, adds cards, resolves them, handoffs to Review, repeats until…

kirodotdev/KiroCrew · 144 tokens

agents-sdk-dotnet-otel

Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in C# / .NET. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed tracing…

microsoft/Agents · 86 tokens