add-deal
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.
What this skill does
## 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:
```
mcp__carta_crm__get_deal_pipelines_with_stages()
```
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)
```
mcp__carta_crm__get_deal_custom_fields()
```
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:
```
mcp__carta_crm__create_deal({
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]"
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.