ClaudeSuperPower
SubmitLog in

meeting-to-deal

Skill

Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "

0Productivity

Install

git clone https://github.com/mondaycom/mcp.git ~/.claude/skills/meeting-to-deal

What is meeting-to-deal?

Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting", "I just had a call with [company]", "what did I promise in that meeting", "add notes from today's calls", or "update the deal after my call".

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Read files only

Read-only tools

~115 tokens of context used while enabled, before you invoke anything

All declared tools (16)
AskUserQuestionReadmcp__monday__all_monday_apimcp__monday__change_item_column_valuesmcp__monday__create_docmcp__monday__create_itemmcp__monday__create_notificationmcp__monday__create_updatemcp__monday__get_board_infomcp__monday__get_board_items_pagemcp__monday__get_column_type_infomcp__monday__get_notetaker_meetingsmcp__monday__get_user_contextmcp__monday__list_users_and_teamsmcp__monday__list_workspacesmcp__monday__search

Documentation

README · ~15 min read

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

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

obsidian-skills

Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.

43.6K stars

command-development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs gu

32.8K stars

plugin-settings

This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin

32.8K stars