meeting-to-deal

meeting-to-deal is a skill for Claude Code from mondaycom/mcp. It costs 107 tokens per session (5,590 once invoked), scanned A, original, MIT.

A workflow that turns meeting transcripts into updates on the matching customer deals in a CRM (customer relationship management system). It can also create contacts for new attendees when enabled.

In plain words
What is it for?
Logging meeting recaps to deals, recording commitments and follow-up tasks, matching calls to customers, and adding new meeting attendees as contacts.
Why use it?
It removes the need to reread calls and copy key points, promises, and next steps into deal records by hand.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the monday-crm plugin — 9 skills shipped together

Good fit Logging meeting recaps to deals, recording commitments and follow-up tasks, matching calls to customers, and adding new meeting attendees as contacts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mondaycom/mcp/meeting-to-deal
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.

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

Made for: Claude Code.

Or install monday-crm, the plugin that ships this one along with the rest of its 9 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for meeting-to-deal

README.md
[![agentmods](https://agentmods.dev/badge/skills/mondaycom/mcp/meeting-to-deal/github.svg)](https://agentmods.dev/skills/mondaycom/mcp/meeting-to-deal)
Your own site
<a href="https://agentmods.dev/skills/mondaycom/mcp/meeting-to-deal"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/meeting-to-deal/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meeting-to-deal

Your own site · 80×15
<a href="https://agentmods.dev/skills/mondaycom/mcp/meeting-to-deal"><img src="https://agentmods.dev/badge/skills/mondaycom/mcp/meeting-to-deal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,590 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 18
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Prompt Injection · line 173
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Prompt Injection · line 198
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Prompt Injection · line 322
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
How audits are shown
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.1 $0.00107 $0.05590
Opus 5 $0.00053 $0.02795
Sonnet 5 $0.00021 $0.01118
Haiku 4.5 $0.00011 $0.00559

Measured 11d ago against content hash ef4eb9491279, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

meeting-to-deal 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 11d 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/meeting-to-deal/SKILL.md · 382 lines

How it starts

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

Meeting to Opportunity

Flow: Trigger → Pull meetings → Match → Synthesize → Publish (α) → Auto-contact (β, opt-in) → Proactive next-step nudges (opt-in).

Input

  • Optional: time window via argument (default = last 24h).
  • Optional: pre-declared mode (Default / Silent / Proactive).

Output

  • α (default): One Meeting recap update per matched deal, summarizing key points + commitments + next steps. Body carries the Generated by Claude · <ISO timestamp> footer + <!-- claude-skill-id: meeting-to-deal --><!-- meeting-id: <id> --> comments. A Meeting sync — <Mon DD> doc lists what was matched, what wasn't, and unresolved attendees.
  • β (Auto-contact, opt-in): New items on the Contacts board for meeting attendees not already in CRM, linked back to the matched deal. Each new contact carries Source = Claude on a status column.
  • Proactive extension: create_notification to deal owner for commitments due this week. Stage column edits and last-touch updates are also OK in Proactive (or in Default with batched confirm) when a clear transition phrase is present in the transcript ("we agreed to move to procurement review", "they signed today"). Surfaced as a single batched plan: " stage transitions detected. Apply all / review each / skip stage edits?". Amount-column writes still forbidden.

Knowledge

  • Meeting → deal matching heuristic (§ Step 4).
  • Update body convention (§ Step 6).
  • Shared artifact conventions (§ Shared patterns).

Tools (MCP)

  • get_user_context — user identity + email domain for filtering meetings and extracting internal_domain.
  • get_notetaker_meetings — recent meetings + transcripts.
  • search / list_workspaces / get_board_info — locate Deals + Contacts boards.
  • get_board_items_page — fetch active deals to match against.
  • get_column_type_info — resolve email/company columns by type.
  • create_update — write the recap onto the matched deal.
  • create_item — β auto-contact on the Contacts board.
  • change_item_column_values — populate the new contact's email + company columns, write Source = Claude on contacts, and apply confirmed stage / last-touch edits on matched deals. Never for amount columns.
  • create_notification — proactive next-step nudges.
  • create_doc — sync summary doc.
  • all_monday_api — escape hatch for connect-board column writes (linking contact ↔ deal). Note: connect-board writes via all_monday_api may fail silently — see Error handling reference.

Read the full file on GitHub · 382 lines

Files

What ships with it

4 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. 11d ago First seen · 382 lines · 107 tokens per session scan A ef4eb9491279

Subscribe to this mod's changes

meeting-to-deal is a skill published in the GitHub repository mondaycom/mcp (424 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 5,590 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.