Skip to content
Back to skills

Source 9a18c181a721a737cade9294

ASecurity

Creates one or more deal records in the Carta CRM via the Carta CRM MCP Server. Use this skill when the user says things like "add a deal", "create a deal", "log a deal", "add deal to CRM", "add deal to Carta CRM", or "/add-deal". Collects deal information conversationally, then creates it via the MCP server.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agents

Works with

  • mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add gutsofpratik/OpenClaude-Skills --skill source-9a18c181a721a737cade9294 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Source 9a18c181a721a737cade9294?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Source 9a18c181a721a737cade9294
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gutsofpratik-source-9a18c181a721a737cade9294/badge)](https://www.skillsdirectory.com/skills/gutsofpratik-source-9a18c181a721a737cade9294)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: add-deal
description: >
  Creates one or more deal records in the Carta CRM via the Carta CRM MCP Server.
  Use this skill when the user says things like "add a deal", "create a deal",
  "log a deal", "add deal to CRM", "add deal to Carta CRM", or "/add-deal".
  Collects deal information conversationally, then creates it via the MCP server.
allowed-tools:
  - mcp__carta__crm_call_tool
  - mcp__claude_ai_Carta__crm_call_tool
  - mcp__2827383e-1775-4df3-b6ff-04d5392f6d18__crm_call_tool
version: 1.0.0
model: haiku
---

<!-- carta:plugin-version -->
<carta-plugin>carta-crm:1.15.0</carta-plugin>

## Overview

Help the user create one or more deal records in the Carta CRM. First fetch available
pipelines and custom fields, then collect deal details conversationally, then call
`create_deal`.

## Step 1 — Fetch available pipelines and stages

Call the pipelines tool so the user can pick a pipeline and stage by name:

```
crm_call_tool({ "name": "crm:get_deal_pipelines_with_stages", "arguments": {} })
```

Present the pipeline and stage names to the user. If the call fails, proceed without
it — pipeline and stage default to the organization's defaults if omitted.

## Step 2 — Discover available custom fields (optional)

```
crm_call_tool({ "name": "crm:get_deal_custom_fields", "arguments": {} })
```

Use returned field IDs and labels as hints when collecting deal data.
If the call fails, proceed without it.

## Step 3 — Collect deal information

Ask the user for:
- **Pipeline** (optional) — which pipeline this deal belongs to (from Step 1)
- **Stage** (optional) — which stage within the pipeline (from Step 1)
- **Company name** (optional) — the company associated with the deal
- **Company URL** (optional) — company website (used for auto-enrichment)
- **Comment** (optional) — notes or comments about the deal
- **Tags** (optional) — array of tag strings
- **Deal lead** (optional) — user ID to assign as deal lead
- **Added at** (optional) — ISO 8601 date the deal was added
- **People** (optional) — contact IDs for advisers, introducers, management
- **Custom fields** (optional) — any fields returned in Step 2

If the user has already provided details in their message, extract them directly
without re-asking.

## Step 4 — Create the deal

Call:

```
crm_call_tool({
  "name": "crm:create_deal",
  "arguments": {
    pipelineId: "<pipeline id>",
    stageId: "<stage id>",
    company: {
      name: "<company name>",
      url: "<company url>"
    },
    comment: "<comment>",
    tags: ["<tag1>", "<tag2>"],
    dealLead: "<user id>",
    addedAt: "<ISO 8601 date>",
    people: {
      advisers: ["<contact id>"],
      introducer: ["<contact id>"],
      management: ["<contact id>"]
    },
    fields: {
      "<field_id>": "<value>"
    }
  }
})
```

Omit any key the user did not provide. Omit `company` if neither name nor URL was given.

## Step 5 — Report result

On success, respond with:
> "Deal for **{company name}** created successfully (ID: `{id}`)."

On error, show the error message and suggest:
- Verify pipeline and stage IDs — run `get_deal_pipelines_with_stages` to list valid options
- Check that custom field IDs are valid

## Adding multiple deals

If the user wants to add multiple deals at once, repeat Steps 3–5 for each one.
After all are done, summarize:
> "Created N deals: [list of company names with IDs]"

Files in this skill

  • PROVENANCE.json196 B
  • SKILL.md3.3 KB
  • UPSTREAM-LICENSE.txt11 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.