Anthropic and Salesforce say Salesforce in Claude ships with 37 prebuilt sales skills, but neither company has published all 37 names in one place. Salesforce’s public GitHub repository for the plugin, salesforce/salesforce-skills, contains 32 named skill folders:
- 30 seller and manager workflows, such as daily-briefing, call-prep, deal-review and forecast-narrative.
- 2 support skills: one renders visual widgets, and one learns a seller’s writing voice.
The remaining skills are not public. Salesforce’s own materials mention at least two names, account-plan and log-activity, that do not appear as folders in the repository.
Below is every verified skill, grouped by workflow, with what it does and an example of how a seller would ask for it. After the list, two worked examples show the skills in a real sales week: one for an account executive and one for a sales manager.
Key takeaways
- 32 skills are verified by name in Salesforce’s public repository. The other skills behind the “37” figure have not been published.
- Skills cover the whole sales cycle: daily planning, account research, calls, deals, pipeline, forecasting, renewals and data hygiene.
- Sellers can ask in plain language or call a skill directly, for example /salesforce-for-sales:daily-briefing.
- Read-only skills never change Salesforce. Write steps need a write-capable connection, and by default Claude asks the seller to approve each change.
- All skills are sales-focused at launch. Salesforce says skills for service, marketing, commerce and industries are coming.
What a “skill” is
A skill is a packaged set of instructions that tells Claude how to do one job: which Salesforce data to pull, which other sources to check, how to structure the output and what to avoid. Salesforce’s plugin documentation describes them as ready-to-use skills for account executives and sales leaders that follow how sales teams already work in Salesforce.
Three things make skills different from typing a prompt:
- They carry the method. Patrick Stokes, Salesforce’s president of applications, has explained how this works. When a seller makes a request, Claude first looks for a skill with specific guidance for the task, then follows it against Salesforce’s MCP server.
- They use your org’s configuration. Salesforce says skills work with your schema, field names, stages and permissions. Teams can add context such as ideal customer profile, qualification framework, competitors and writing style through Claude’s instructions.
- They are personalized. A setup skill runs the first time a seller opens the plugin, learns their role and book of business, and tailors the other skills to them. Anthropic’s Help Center lists this setup skill separately from the 37 sales skills.
Example: prompt versus skill. Ask a general AI assistant to “review my pipeline” and you get a generic checklist. Ask Salesforce in Claude the same thing and the pipeline-review skill takes over. It pulls your open opportunities by stage, compares them with your closed-deal history, checks coverage against your target, and flags hygiene problems such as missing next steps. The skill knows which Salesforce objects matter and what a pipeline review should contain. That is the difference between asking a question and running a method. If you want a refresher on how those opportunity stages and pipeline records work in Sales Cloud, see our guide to how Sales Cloud helps sales teams manage leads and opportunities.
The 32 verified skills
The descriptions below summarize each skill’s published description in Salesforce’s repository. The example prompts are our own, written to show how a seller would naturally trigger each one.
Daily rhythm (4 skills)
Skill | What it does | Example prompt |
daily-briefing | Builds today’s sales briefing from Salesforce meetings, deals closing soon or overdue, account context, commitments and unread customer email | “What needs my attention today?” |
calendar-events | Shows a schedule from Salesforce Event data, with local times, locations and linked contacts, accounts or deals | “What meetings do I have tomorrow?” |
inbox-sweep | Creates a prioritized reply queue and email drafts from unread threads, the seller’s sent-mail style, and account and deal context | “Go through my unread customer emails and draft replies.” |
weekly-wrap | Builds a weekly recap of wins, losses, deal activity and next week’s priorities from Salesforce, calendar, email, documents and Slack | “Wrap up my week and draft an update for my manager.” |
Anthropic’s launch announcement says the morning brief can be scheduled to run in the background. On Fridays, it wraps the week and drafts an update for the seller’s manager.
Account and prospect research (5 skills)
Skill | What it does | Example prompt |
account-context | Builds a 360-degree brief on an existing account: CRM state, key contacts, recent email, documents and internal Slack | “Catch me up on Northwind before I reach out.” |
research-prospect | Builds a brief on a net-new company or person from web research and Salesforce: company facts, recent signals, likely priorities, contacts and ICP fit | “Research Brightline Logistics before my first call.” |
account-tiering | Ranks an account list or full book into action tiers using ICP fit, engagement, activity, contact and opportunity data | “Tier my accounts and tell me which to prioritize this quarter.” |
stakeholder-map | Maps stakeholders from Salesforce contacts and roles plus email, calendar, calls and Slack, showing influence, stance, gaps and access paths | “Who are the decision makers at Acme, and where are we single-threaded?” |
expansion-whitespace | Identifies ranked expansion plays for one customer from contacts, owned products, opportunities and recent activity | “Where can we expand at Contoso?” |
Customer health and renewals (3 skills)
Skill | What it does | Example prompt |
customer-health | Assesses customer health from account, renewal, case, task and health data plus email, calendar, documents and Slack; also used to prepare business reviews | “How healthy is the Globex account ahead of our QBR?” |
renewal-radar | Builds a renewal risk brief covering timing, activity, uplift and next moves, for one renewal or all upcoming ones | “Which renewals in the next 90 days are at risk?” |
customer-voice | Compiles attributable customer quotes and themes from call transcripts and email threads across accounts | “What are customers saying about our reporting feature?” |
Calls and outreach (4 skills)
Skill | What it does | Example prompt |
call-prep | Builds a call brief from meeting, account, opportunity, contact and activity data plus email, documents and Slack: attendees, deal history, open threads and discovery needs | “Prep me for my renewal call with Initech.” |
call-follow-up | Turns a transcript and Salesforce history into a customer follow-up email and internal recap, with decisions, commitments, objections, next steps and proposed CRM updates | “Turn this morning’s call into a follow-up email and a note for the team.” |
draft-outreach | Drafts a personalized email to one prospect or customer from contact, account, opportunity and activity data plus prior email | “Write a follow-up to the team I met with on Tuesday.” |
handle-objection | Builds a grounded response to pricing, timing, trust or competitive pushback from the current deal, win-loss history, customer evidence and approved internal documents | “They say our price is 20% higher than the competitor. How should I respond?” |
Anthropic’s launch post adds detail on call prep: if Claude finds stakeholders in email or Slack threads who are not yet in Salesforce, it adds them as contacts on the account.
Deals (6 skills)
Skill | What it does | Example prompt |
deal-review | Builds a scored deal-health assessment with evidence-backed risks, to judge whether one deal will close | “Will the Acme deal close this quarter?” |
deal-advance-gap | Maps a deal’s path to advance or close from stage, stakeholder, activity, qualification and risk data, identifying blockers and owners | “This deal has been stuck in evaluation for six weeks. What’s blocking it?” |
deal-signals | Builds a deal-risk digest: quiet or overdue deals, close-date danger, renewal windows and competitor mentions | “Which of my deals moved close dates this week?” |
deal-slip-scenario | Models the impact of a deal slipping, shrinking or being lost against quota, including the gap and substitutes | “If the Globex deal slips to next quarter, can I still hit my number?” |
close-plan | Builds a customer-facing business case and dated mutual action plan from opportunity data, transcripts, email, documents and Slack | “Build a mutual close plan for Initech with a signature date of December 15.” |
win-loss-review | Analyzes closed opportunities, stage history, transcripts and email for win rates, loss stages, objections and patterns | “Why did we lose deals to our main competitor this year?” |
Anthropic describes how deal review and close plan work together. Claude scores a deal against the team’s methodology, looking at qualification gaps, stakeholders not yet met and close-date risks. It then drafts the business case and mutual close plan, fills in qualification fields and adds missing stakeholders as contact roles, saving to the opportunity once approved.
Pipeline, forecast and coaching (5 skills)
Skill | What it does | Example prompt |
pipeline-review | Assesses one seller’s current pipeline from stage aggregates, deal samples and closed-deal history: coverage, hygiene and risks | “Review my pipeline against my coverage target.” |
team-pipeline | Builds a manager’s team brief: closed revenue, forecast, swing deals and coaching needs by rep | “Prepare my team pipeline review for Monday.” |
forecast-narrative | Builds a forecast-call brief from opportunity aggregates, top deals and field history: the number, bucket movement, risks and asks | “How am I tracking against quota this quarter?” |
rep-context | Catches a manager up on one rep before a 1:1: pipeline, recent activity, focus areas, where they need help, and suggested questions | “Prep me for my 1:1 with Priya.” |
lead-triage | Produces an inbound-lead priority and routing recommendation from Lead and Account data, research and email engagement | “Should we fast-track this inbound lead from Northwind, and who should own it?” |
Anthropic says pipeline review produces an interactive dashboard showing coverage by stage, the deals most likely to slip and why, and drill-down by account. The dashboard can be shared with leadership, and from it a seller can ask Claude to move a close date or change a stage. If your pipeline problems run deeper than a weekly review can fix, our Salesforce sales pipeline acceleration service looks at stage design, conversion and forecasting together.
Data and knowledge (3 skills)
Skill | What it does | Example prompt |
salesforce-hygiene-check | Audits open opportunities for missing fields, stale dates, weak next steps, stage mismatches and single-threading, and lists prioritized fixes without changing records | “Check my pipeline for data problems.” |
query-activity-history | Builds an interaction timeline from closed Tasks and Events on one account, contact, lead or opportunity | “What’s happened on the Contoso opportunity since August?” |
find-internal-answer | Finds a sourced answer from internal documents, Slack, email and Salesforce: a policy, an approver, a deck, a security document or a colleague with relevant experience | “Who approves discounts over 25%, and where’s the latest security questionnaire?” |
Support skills (2 skills)
Skill | What it does |
using-display-widget | Renders assembled Salesforce data as a styled visual widget; other skills call it when they need a dashboard or visual layout |
voice-profile | Builds a reusable profile of the seller’s email style (greetings, sign-offs, length, structure, tone and recurring phrases) from recent sent mail, so drafts sound like them; used during setup and requires access to sent mail |
Example: one account executive’s day with the skills
The list above shows what each skill does on its own. This illustrative day shows how they chain together. Maya is an account executive at a software company. Her biggest open deal is a renewal with Initech, due to close in nine days.
8:00 a.m. – daily-briefing. Maya’s morning brief has already run on a schedule. It shows three meetings today and two unread emails from customers. It also flags the Initech renewal: nine days to close, and no logged activity in twelve days. Without the brief, she might not have noticed the gap until the forecast call.
8:15 a.m. – inbox-sweep. She asks Claude to go through her unread customer email. Claude puts the two customer threads at the top of a reply queue and drafts responses in her usual style. The voice profile learned that style during setup: short paragraphs, first names, a one-line sign-off. She edits one draft and sends both from her own inbox.
9:30 a.m. – call-prep. Before the Initech call, she asks Claude to prep her. The brief lists the attendees, the account’s history and the open renewal opportunity. It also finds a new VP of Finance copied on a recent email thread who is not yet in Salesforce, and proposes adding her as a contact. Maya approves the change once.
10:30 a.m. – call-follow-up. After the call, Maya pastes her notes. Claude drafts two things:
- a customer recap email covering the decisions made and next steps
- an internal note flagging that Initech’s VP of Finance wants a multi-year pricing option
Claude also proposes CRM updates: a new next step, and a close date moved back one week. Maya reviews each update and approves.
1:00 p.m. – handle-objection. Initech’s procurement lead emails that a competitor quoted 20% less. Maya asks Claude how to respond. The answer draws on the deal’s history, the team’s win-loss record against that competitor, and the approved pricing guidance in the company’s internal documents. It suggests leading with implementation time and support rather than matching the price.
3:00 p.m. – deal-review and close-plan. Maya asks whether Initech will close this quarter. The deal review scores the renewal and flags the main risk: nobody has met the new VP of Finance. She then asks for a close plan. Claude drafts a mutual action plan with dated steps back from the signature date, including a pricing review with the VP of Finance next week.
Friday, 4:00 p.m. – weekly-wrap. Claude builds her weekly recap: wins, deals that moved, the Initech risk and her priorities for next week. It drafts the update to her manager.
In one ordinary day Maya used seven skills, plus the voice profile running in the background, without opening a Salesforce report. Every record change went through an approval prompt, and every email was a draft until she sent it.
Example: a sales manager’s Monday
Managers get the most from the pipeline and forecast skills. Here is an illustrative Monday for Daniel, who manages eight account executives.
- Before the team pipeline meeting, Daniel asks Claude to prepare his team pipeline review. The team-pipeline brief shows closed revenue for the quarter, the current forecast, four swing deals and two reps whose pipeline coverage is under target.
- During the meeting, a rep says the Globex deal might slip. Daniel asks what happens to the team’s number if it moves to next quarter. The deal-slip-scenario skill shows the gap and suggests which deals could cover it.
- Before his leadership forecast call, he runs forecast-narrative. It gives him the number, what moved between forecast categories since last week, the top risks, and the help he needs from leadership.
- Before a 1:1 with Priya, he runs rep-context. It summarizes her pipeline, recent activity and where she seems stuck, with three suggested coaching questions.
- Midweek, he checks deal-signals for quiet deals and moved close dates across the team.
Each of those briefs used to take a manager an hour or more in reports and spreadsheets. With the skills, preparation becomes a set of short requests, and the manager’s time goes to the conversations instead.
What about the other five?
The public repository has 32 folders; the official count is 37. We have not found an official list of the difference, so here is only what the sources show:
- account-plan. Salesforce’s Trailhead module on Sales Cloud in Claude lists account-plan as one of five featured skills, describing a formal plan built from live CRM records and web research. No folder with that name is in the public repository; close-plan is the closest match.
- log-activity. The query-activity-history skill’s own description points sellers to a skill called log-activity for creating an entry. We confirmed on September 28, 2026 that the reference is still there and that no log-activity folder exists in the repository.
- Write workflows. Anthropic’s launch post describes Claude logging calls, creating follow-up tasks, updating opportunities, and adding contacts and contact roles. Some of these may be separate skills in the production plugin rather than steps inside the published ones.
We checked the repository’s main and claude-prod branches on September 28, 2026, and both contained the same 32 skill folders. We will update this list when Salesforce publishes more skill folders or an official list.
Which skills read and which write
Salesforce’s design principles for the plugin say read-only skills do not create or modify Salesforce records. Skills that propose updates, such as call-follow-up, close-plan or anything that logs activity, need a write-capable connection. With a read-only connection, those skills still run their analysis, and the write steps provide manual guidance instead.
When writes are enabled, Claude shows each proposed change and asks the seller to allow it once, always allow it, or deny it. Anthropic’s Help Center guide to using Salesforce in Claude describes this approval flow. Outreach and follow-up emails are created as drafts for review, not sent automatically. Slack content stays a draft until the seller approves the exact message and channel.
Example: the same skill, two connection settings. Maya runs call-follow-up after her Initech call.
- Read-only connection: Claude drafts the recap email and internal note as usual, then lists the updates she should make herself, such as “Move close date to October 16 and set next step to pricing review with the VP of Finance.” She makes those changes in Salesforce.
- Write-enabled connection: Claude presents the same updates as proposed changes with an approval prompt. When she approves, they are written to the opportunity.
The analysis is identical either way; only the final step changes.
Salesforce’s setup notes recommend keeping the beta read-only at first. If you follow that advice, sellers get full value from research, prep and pipeline skills, and manual guidance from skills that would normally update records.
Skills by role
Role | Most useful skills |
Account executive | daily-briefing, call-prep, call-follow-up, draft-outreach, deal-review, close-plan, handle-objection, pipeline-review |
Sales development rep | research-prospect, lead-triage, draft-outreach, account-tiering, inbox-sweep |
Account manager or customer success | account-context, customer-health, renewal-radar, expansion-whitespace, stakeholder-map |
Sales manager | team-pipeline, forecast-narrative, rep-context, deal-signals, deal-slip-scenario, win-loss-review |
Sales operations | salesforce-hygiene-check, query-activity-history, win-loss-review, account-tiering |
Marketing (with Sales Cloud access) | customer-voice, win-loss-review, account-tiering, research-prospect |
Where the skills get their data
- Salesforce: through the Headless 360 MCP server, under the signed-in seller’s permissions. Salesforce’s repository configuration describes read support, plus guided create and update support, on Accounts, Contacts, Opportunities, Leads and activities.
- Slack: the one non-Salesforce connector bundled with the plugin, used for deal-channel summaries and account-team threads.
- Optional sources: email, calendar and document connectors such as Gmail, Google Calendar and Google Drive, connected separately. Several skills use them for richer context.
- Transcripts and notes: call-follow-up, customer-voice and win-loss-review work best with call transcripts.
- The web: research-prospect adds public web research for net-new companies.
If an optional source is missing, Salesforce says the skill either asks for the input or continues with the Salesforce context it has and names the limitation. For example, suppose Maya has not connected her calendar and her team does not log meetings in Salesforce. Her daily briefing would then show no meetings. The briefing would say so, rather than inventing a schedule.
How to get more from the skills
- Run the hygiene check first. Skills that score deals and forecasts are only as good as the fields they read. If the hygiene check turns up hundreds of stale close dates and empty next steps, a one-time Salesforce CRM cleanup is faster than fixing records one at a time.
- Write your sales context into Claude’s instructions. Your ICP, qualification framework, stage definitions and competitors turn generic deal reviews into ones that match how your team sells.
- Let the voice profile run. Drafts that sound like the seller get sent; drafts that sound generic get rewritten.
- Connect calendar and email where policy allows. Daily briefings and call prep are much stronger with them.
- Use slash commands for repeatable routines. A manager who runs /salesforce-for-sales:team-pipeline every Monday gets the same format week to week, which makes changes easier to spot.
- Tailor skills if you need to. Salesforce’s documentation says teams can add organization-specific context and adapt individual skill files.
Example: a sales context instruction. Here is the kind of short, specific context that sharpens deal reviews and outreach. Adapt it to your own business:
“We sell workflow software to logistics and manufacturing companies with 200 to 2,000 employees in North America. Disqualify companies under 100 employees. We qualify deals with MEDDICC; the Economic Buyer and Champion fields on the opportunity must be filled before Stage 3. Our stages are Discovery, Qualified, Solution, Proposal, Negotiation and Closed. Our main competitors are Competitor A (usually cheaper, weaker on integrations) and Competitor B (strong in enterprise, slow to implement). Customer emails should be short, plain and signed with the seller’s first name.”
With that context, deal-review can flag that a Stage 4 deal has no Economic Buyer. Handle-objection also knows which strengths to lead with against each competitor.
What is coming next
Salesforce’s AIforce announcement says Salesforce in Claude will add analytics with Tableau, and skills for service, marketing, commerce and industries, in the near future. VentureBeat reported at launch that skills for other business functions would begin rolling out later in 2026. For developers, a separate Salesforce Development plugin for Claude Code already includes more than 40 skills.
Frequently asked questions
How many skills does Salesforce in Claude have?
Anthropic and Salesforce say Salesforce in Claude ships with 37 prebuilt sales skills. Neither company has published all 37 names in one place. Salesforce’s public GitHub repository for the plugin, salesforce/salesforce-skills at version 1.0.0-beta.1.2, contains 32 named skill folders: 30 seller and manager workflows plus two support skills for visual widgets and writing voice. Salesforce’s own materials also mention account-plan and log-activity, which are not in the public repository. The remaining skills therefore likely ship only in the product itself.
What are the sales skills in Salesforce in Claude?
The 32 verified skills fall into seven groups:
- Daily rhythm: daily-briefing, calendar-events, inbox-sweep and weekly-wrap.
- Research: account-context, research-prospect, account-tiering, stakeholder-map and expansion-whitespace.
- Renewals: customer-health, renewal-radar and customer-voice.
- Calls: call-prep, call-follow-up, draft-outreach and handle-objection.
- Deals: deal-review, deal-advance-gap, deal-signals, deal-slip-scenario, close-plan and win-loss-review.
- Pipeline: pipeline-review, team-pipeline, forecast-narrative, rep-context and lead-triage.
- Data: salesforce-hygiene-check, query-activity-history and find-internal-answer.
Two support skills, using-display-widget and voice-profile, sit alongside them.
Can I see the Salesforce in Claude skills myself?
Yes. Salesforce publishes the plugin in its salesforce/salesforce-skills repository on GitHub, under the salesforce-for-sales folder. Each skill has its own folder with a SKILL.md file describing what it does, which data it uses and how its output is structured. As of September 28, 2026, the repository shows version 1.0.0-beta.1.2, with 32 skill folders on both its main and claude-prod branches. Admins can read the files to understand exactly what each skill will do before rolling the plugin out to sellers.
How do I use a specific skill in Salesforce in Claude?
Ask Claude in plain language, such as “Prep me for my call with Initech,” and Claude picks the matching skill. Salesforce’s president of applications has described Claude as first looking for a skill with specific guidance for the task, then following it against Salesforce’s MCP server. You can also call a skill directly with a slash command, for example /salesforce-for-sales:call-prep or /salesforce-for-sales:team-pipeline. Slash commands are useful for repeatable routines, because they produce the same format every time you run them.
Do Salesforce in Claude skills change Salesforce data?
Read-only skills never do; Salesforce’s design principles for the plugin say they do not create or modify records. Skills that propose updates, such as call-follow-up or close-plan, need a write-capable connection. Even then, by default Claude shows each proposed change and asks the seller to allow it once, always allow it, or deny it. Emails are created as drafts, not sent. With a read-only connection, which Salesforce recommends during the beta, write steps give manual guidance instead of updating records.
Which Salesforce in Claude skills are best for sales managers?
Six skills are especially useful for managers:
- team-pipeline prepares a team brief covering closed revenue, forecast, swing deals and coaching needs by rep.
- forecast-narrative builds the forecast-call brief from opportunity aggregates and field history.
- rep-context catches a manager up on one rep before a 1:1, with suggested questions.
- deal-signals flags quiet deals, slipping close dates and competitor mentions.
- deal-slip-scenario models what happens to the number if a big deal slips, shrinks or is lost.
- win-loss-review adds pattern analysis across closed deals.
Can marketing or service teams use Salesforce in Claude skills?
Not with dedicated skills yet. Every skill at launch is built for sales. Salesforce says skills for service, marketing, commerce and industries, plus Tableau analytics, will follow in the near future. Some sales skills still help adjacent teams today:
- Marketers with Sales Cloud access can use customer-voice for messaging research, win-loss-review for positioning and account-tiering for account-based marketing lists.
- Customer success teams can use customer-health, renewal-radar and expansion-whitespace.
All of them run under each user’s own Salesforce permissions.
Can we customize the skills in Salesforce in Claude?
Yes, in two ways. First, add your sales context through Claude’s instructions: ideal customer profile, qualification framework, stage definitions, competitors and writing style. Salesforce says the skills use this context alongside your org’s schema, fields and stages, which turns generic outputs into ones that match how your team sells. Second, Salesforce’s documentation says teams can tailor individual skill files. Start with context, since it is easier to maintain. Only change skill files once you understand how the default versions behave with your data.
What data do Salesforce in Claude skills use?
Every skill reads Salesforce through the Headless 360 MCP server, under the signed-in seller’s permissions, covering accounts, contacts, opportunities, leads and activities. Slack is the one non-Salesforce connector bundled with the plugin, used for deal channels and account-team threads. Several skills get richer results with optional connectors such as Gmail, Google Calendar and Google Drive, connected separately. Call-follow-up, customer-voice and win-loss-review work best with call transcripts, and research-prospect adds public web research. If a source is missing, the skill works with what it has and names the gap.
Is the setup skill one of the 37 sales skills?
No. Anthropic’s Help Center lists the setup skill separately from the 37 sales skills. It runs the first time a seller opens Salesforce in Claude, asks about their role and book of business, and personalizes the other skills around that. Anthropic says it also creates a Claude artifact tailored to the seller. The voice-profile skill, which learns a seller’s email style from recent sent mail, is also used during setup. Running setup properly is the quickest way to make every other skill more relevant.
Put the skills to work
HyphenX Solutions helps sales teams set up Salesforce in Claude, prepare their data, and write the sales context that makes the skills useful from day one. Talk to our Salesforce Sales Cloud services team to get your sellers started.
