Claude Skills for sales teams

A skill is a set of written instructions Claude loads when your request matches its description. You write it once, and Claude follows the same steps every Monday instead of improvising. The format is plain Markdown with a short header, so anyone on your team can read and edit it.

A skill needs tools to act on. SalesCrew exposes 140+ MCP tools, and every tool has a twin in the app with the same effect. That means a skill can say "call stalled_deals" and get the list your manager would see on the pipeline screen. You can check the full tool list on the SalesCrew MCP server page.

Your tokens are scoped like your users. An MCP token carries the same channel, profile and area limits as the person who issued it, and every call lands in the audit log with the actor named.

Use this one at the start of the week. It finds deals that have gone quiet, reads the last touch on each, and proposes one next step per deal. You pick which steps become tasks.

---
name: pipeline-review
description: Weekly pipeline review. Use when the user asks which deals are stuck,
  what to do next on open deals, or for a Monday pipeline check.
---

# Pipeline review

1. Call stalled_deals to get open deals that have gone quiet.
2. For each deal, call deal_get and record_summary to read the last touch.
3. Call next_actions_list and compare it with what you found.
4. Write one line per deal: deal name, days idle, the last touch, one next step.
5. For every next step the user accepts, call task_create with a due date.

Rules:
- Never call deal_update_stage. Suggest stage changes; the user makes them.
- Never send email from this skill. Drafts belong to the reply-triage skill.
- Sort the list by deal value, largest first.

Reply triage is where most sales time goes. This skill sorts new replies into five groups, stops the cadence for anyone who opted out, and writes drafts for the rest. The drafts land in the SalesCrew inbox composer, where you edit and send them.

---
name: reply-triage
description: Triage new replies to outbound email. Use when the user asks to go
  through the inbox, sort replies, or draft answers to prospects.
---

# Reply triage

1. Call inbox_threads for unread threads from the last 24 hours.
2. Open each with inbox_thread. Call inbox_classify if it has no label yet.
3. Group the threads: interested, not now, wrong person, unsubscribe, out of office.
4. Unsubscribe: confirm the contact is on the suppression list with suppression_list.
   If it is missing, call suppression_add. Then call cadence_stop_contact.
5. Interested, not now, wrong person: call inbox_draft_reply for each thread.
   Keep drafts under 90 words and answer the prospect's actual sentence.
6. Report back with a count per group and the drafts you wrote.

Rules:
- Draft only. Every external send goes through the approval queue.
- Never call inbox_reply_send.
- Out of office: add a note with note_add giving the return date, and move on.

The reply wording itself lives on the reply-handling templates page, and you can paste those into the skill as examples.

Duplicates creep in from imports, forms and people typing fast. This skill lists the pairs, tells you which record should survive and why, and merges only the pairs you approve. For a full set of cleanup prompts, see AI prompts for cleaning a messy CRM.

---
name: crm-hygiene
description: Clean up duplicate and incomplete contact records. Use when the user
  asks to tidy the CRM, find duplicates or fix missing fields.
---

# CRM hygiene

1. Call duplicates_list and group the pairs by match reason (email, name + company).
2. Show the user each pair side by side: email, company, last activity, open deals.
3. Recommend which record survives: the one with open deals, then the newest activity.
4. Call duplicates_merge only for pairs the user approves in this conversation.
5. Call contact_search for contacts with no company or no job title.
   Suggest values from the email domain and the signature in record_emails.
6. Apply accepted fixes with contact_update, one call per contact.

Rules:
- Merges and deletes wait for the user's yes. Never batch them silently.
- Never overwrite a field that already holds a value. Fill blanks only.

A good brief takes a rep ten minutes of clicking. This skill does the reading and quotes the prospect's own words, so you walk in knowing what they asked for last time.

---
name: meeting-prep
description: Prepare a one-page brief before a sales call. Use when the user names a
  meeting, a contact or a company they are about to speak with.
---

# Meeting prep

1. Call meeting_list for today and tomorrow and find the meeting the user means.
2. Call contact_search, then record_summary for the contact and their company.
3. Call record_emails for the last five threads with this person.
4. Call kb_search with the prospect's industry to pull your own positioning notes.
5. Write the brief:
   - Who they are and how they reached us (source, first touch date)
   - What they said, quoted from the threads
   - Open deal, stage and value, if one exists
   - Three questions to ask, based on what is missing from the record

Rules:
- Quote the prospect's words; never paraphrase a commitment.
- Add the brief to the contact with note_add when the user says so.

Building a list is a query over the Data Bank plus the suppression list. The skill reports how many rows the suppression pass removes before you commit, and it stops at a saved segment. You freeze the segment into a cadence yourself.

---
name: audience-build
description: Build an outbound audience from the Data Bank. Use when the user asks
  for a list, a segment, or who to email next.
---

# Audience build

1. Call icp_list and ask the user which ICP this audience serves.
2. Call data_bank_query with the ICP filters and report the row count.
3. Call suppression_list and tell the user how many rows it will remove.
4. On the user's yes, call segment_create with a name that states the ICP and the month.
5. Hand back the segment name and count. Freezing it into a cadence is the user's step.

Rules:
- Never enroll contacts in a cadence from this skill.
- Suppression runs again at freeze and at send; say so when you report counts.

The weekly report pulls from four tools and writes the numbers in a fixed order. Channel cost sits in the same database as your deals, so cost per meeting by channel is a tool call, not a spreadsheet. The lead gen client report template uses the same numbers for a client-facing version.

---
name: weekly-report
description: Write the weekly sales report. Use on Fridays or when the user asks how
  the week went, which channel worked, or for numbers to share.
---

# Weekly report

1. Call weekly_report for the headline numbers.
2. Call channel_economics for meetings, deals and cost by channel.
3. Call campaign_reply_stats for each active campaign.
4. Call team_kpis for activity per person.
5. Write the report in this order:
   - Meetings booked and deals created, against last week
   - The channel with the lowest cost per meeting, with its figure
   - The campaign with the highest reply rate, and the one to pause
   - One decision the user should make on Monday

Rules:
- Every number comes from a tool call in this run. Never estimate.
- Name the tool behind each figure in a footnote line.

Save each block as SKILL.md inside a folder named after the skill, for example pipeline-review/SKILL.md. In Claude Code, put the folders under .claude/skills in your project. In the Claude app, zip each folder and upload it in the Skills section of your settings.

Then connect Claude to SalesCrew. Issue an MCP token in SalesCrew Settings, add the server URL and token to Claude, and ask "run the pipeline review". The step-by-step version is in the guide to getting an MCP token and adding it to Claude.