Back to Blog
AI Builds

Salesforce in Claude: All 37 Skills, Actually Verified

TS

Tushar Sharma

Chief Executive Officer

11 min read - Oct 12, 2026

The short version

  • Every announcement says the Salesforce in Claude plugin ships "37 skills." Nobody, including Salesforce, has published the full list in one place. So we verified it at the source: Salesforce’s public plugin repository, the same one the official docs point admins at.
  • The honest count: 34 skills verified by name and function from the repo, plus 4 more named on Salesforce’s own Claudeforce page that are not in the public repo. The full official roster of 37 has never been enumerated.
  • Two of the 34 shipped after launch (the configure and update skills, September 29), and the repo’s commit history shows exactly 32 at the September 15 open beta.
  • Requirements: any paid Claude plan on the Claude side; on the Salesforce side, the Help Center cites the latest Sales Cloud Enterprise edition plus beta approval through AgentExchange.
  • The promised "additional skills launching late 2026" had not landed as of October 12, but the Claudeforce page lists ten more product lines marked coming soon, from Service to MuleSoft to Headless 360.

The Number Nobody Can Source

"37 skills" is in the press release, the Claude blog, and every roundup of the Salesforce in Claude plugin. What no official source does is list them. Roundup posts handle this by padding plausible-sounding names; we handled it by going to the source: Salesforce’s public plugin repository, the same repo and release branch the official Claude documentation points enterprise admins at, which means it is the shipping plugin code rather than a mirror, plus the raw source of Salesforce’s own Claudeforce page.

The honest accounting, as of October 12, 2026: 34 skills verified by exact name and function in the repo, and 4 more named verbatim on the Claudeforce page that do not appear in the public repo (hosted-only or not yet released). The full official roster of 37 has never been published anywhere we can find, and we will not pretend to reconcile the arithmetic for it. What follows is the verified list.

The Verified List: Morning and Cadence

All 34 repo-verified skills follow, grouped the way sellers actually use them, each with its function condensed from its own definition file. First, the daily rhythm:

  • daily-briefing - today’s meetings, near-term and overdue deals, commitments, unread customer email
  • calendar-events - schedule view from Salesforce Event data with linked contacts, accounts, and deals
  • weekly-wrap - the weekly recap: wins, losses, deal activity, next week’s priorities
  • inbox-sweep - a prioritized response queue with email drafts from unread threads

Pipeline, Forecast, and Deal Strategy

  • pipeline-review - one rep’s pipeline: coverage, hygiene, risks
  • team-pipeline - the manager view: closed revenue, forecast, swing deals, coaching needs by rep
  • forecast-narrative - the forecast-call brief: the number, bucket movement, risks, asks
  • deal-signals - deal-risk digest: quiet or overdue deals, close-date danger, competitor mentions
  • deal-slip-scenario - models a deal slipping, shrinking, or dying: the gap and the substitutes against quota
  • deal-review - a scored deal-health assessment with evidence-backed risks
  • deal-advance-gap - the path to advance or close a stuck deal: blockers, owners, close-date credibility
  • close-plan - a customer-facing business case plus a dated mutual action plan
  • stakeholder-map - influence, stance, gaps, access paths, and the single-threading check
  • handle-objection - a grounded response to pricing, timing, trust, or competitive pushback
  • win-loss-review - win rates, loss stages, objections, and deal patterns from closed opportunities

Accounts and Growth

  • account-context - a 360 brief on an existing account across CRM, contacts, email, docs, and Slack
  • account-tiering - ranks an account list or book into action tiers by ICP fit and engagement
  • research-prospect - a net-new company or person brief from web research plus Salesforce
  • customer-health - health and risk assessment; business-review prep
  • renewal-radar - the renewal risk brief: timing, activity, uplift, next moves
  • expansion-whitespace - ranked upsell and whitespace plays for one customer
  • customer-voice - attributable customer quotes and themes from transcripts and email
  • lead-triage - inbound lead priority and a routing recommendation

Meetings, Outreach, and the Utility Layer

  • call-prep - the one-page call brief: attendees, deal history, open threads, discovery questions
  • call-follow-up - turns a transcript into the customer email, the internal recap, and proposed CRM updates
  • draft-outreach - a personalized single-prospect email draft
  • voice-profile - builds a reusable writing-voice profile from your sent mail
  • rep-context - manager prep for a 1:1 with a rep
  • salesforce-hygiene-check - audits open opportunities for missing fields, stale dates, weak next steps
  • query-activity-history - the interaction timeline from closed Tasks and Events on a record
  • find-internal-answer - finds the policy, approver, deck, or precedent across docs, Slack, email, and Salesforce
  • using-display-widget - internal support skill that renders results as styled widgets
  • configure - onboarding and setup: the daily refresh schedule and your intelligence view (added September 29)
  • update - version-aware plugin maintenance, run on the daily schedule (added September 29)

The Four Named but Not Public

Salesforce’s Claudeforce page names four more skills that are not in the public repo: account-plan, summarize-conversation-transcript, schedule-meeting, and log-activity. These are not vapor: the repo’s own query-activity-history skill instructs "to create an entry, use log-activity," so at least that one exists in the hosted plugin with its definition unpublished. The same page also lists "sfdc-hygiene-check," which is most likely the repo’s salesforce-hygiene-check wearing a marketing name, though nothing official confirms the equivalence, so we flag it rather than assert it.

What Changed Since Launch, Dated by Commit

The repo’s history answers the freshness question precisely: 32 skills at the September 15 open beta, the configure and update pair added on September 29, and an October 8 release that improved reliability (better rollups behind the pipeline and account skills) without adding skills. The press release’s promise of "additional skills launching late 2026" was unfulfilled as of October 12, but the roadmap is visible on the Claudeforce page: Service, Marketing, Commerce, Revenue, Field Service, Tableau, MuleSoft, Data 360, Headless 360, and Industries, all marked coming soon. When the first of those lands, this post gets its update.

One disambiguation, because coverage keeps conflating them: this seller plugin is a different product from the Salesforce Development plugin for Claude Code (40-plus developer skills, per Dreamforce coverage). The developer side of this story is our MCP servers map.

Who Can Run It, and the Principles Worth Stealing

Requirements, as the official docs state them: any paid Claude plan during the beta, working in chat and Claude Cowork, configured by a Claude org Owner. On the Salesforce side the Help Center cites the latest Sales Cloud Enterprise edition, with beta approval requested through the AgentExchange listing. The admin flow is unchanged since launch (we diffed the setup file to check) and our setup guide walks it end to end; the one piece of official guidance worth bolding is the recommendation to restrict the beta to read-only tools at first, which we second.

And the part worth stealing even if you never install it: the design principles in Salesforce’s own repo read like a checklist for any CRM-connected AI. *Use existing access; write only after approval. Draft before sending. Stay grounded in records.* At runtime that becomes an Allow once / Always allow / Deny prompt on every proposed write. If the agent you are building, on any platform, cannot pass those three tests, it is not ready for your org, and making it ready is precisely what our Claudeforce practice does, starting with a free 30-minute call.

Free 30-minute consultation

Want this working in your org?

Tell us where to send times and prep notes. You get a senior architect and an honest read on scope and cost, not a sales pitch.

No spam, no list. One architect, one email, that is it.

FAQ

Frequently Asked Questions

How many skills does Salesforce in Claude actually have?

37 is the official claim, repeated in the press release, the Claude blog, and the Help Center, but no official source lists them all. What is verifiable: 34 skills by exact name and function in Salesforce’s public plugin repository, and 4 more named verbatim on the Claudeforce marketing page that are not in the public repo. We publish the verified portions and flag the gap rather than padding the list, which is what most roundups quietly do.

Where is the full list of Salesforce in Claude skills?

The closest thing to an official list is the salesforce-skills repository on Salesforce’s GitHub, which contains the shipping plugin code: 34 skills, each with its own definition file. This post reproduces all 34 names with one-line functions, grouped the way sellers actually use them, plus the 4 hosted-only names from Salesforce’s Claudeforce page.

Have any skills been added since the September launch?

Yes, two, and the commit history dates them precisely: the plugin launched open beta with 32 skills on September 15, 2026, and a September 29 release added configure (onboarding and a daily refresh schedule) and update (version-aware plugin maintenance). An October 8 release improved reliability without adding skills. The press release promised additional skills "late 2026"; as of October 12 none of the ten coming-soon product lines had shipped.

What do I need to run Salesforce in Claude?

Claude side: any paid plan during the beta, in chat and Claude Cowork, with a Claude org Owner doing the configuration. Salesforce side: the Claude Help Center cites the latest Sales Cloud Enterprise edition, and the org must be approved through the beta sign-up on AgentExchange. The admin flow itself, MCP server, permission set, External Client App, connector, rollout, is unchanged since launch and covered step by step in our setup guide.

Can the plugin write to our Salesforce org?

Only with approval, twice over. The design principles in Salesforce’s own repo are explicit: use existing access, write only after approval, draft before sending, stay grounded in records. At runtime Claude shows each proposed write and asks Allow once, Always allow, or Deny, and the official setup guidance recommends admins restrict the beta to read-only tools, a recommendation we second for the first weeks of any rollout.

Is this the same as the Salesforce plugin for Claude Code?

No, and conflating them is the most common error in coverage. Salesforce in Claude is the seller-facing plugin for the Claude app with the 37 skills this post covers. Dreamforce coverage also mentioned a separate Salesforce Development plugin for Claude Code with 40-plus developer skills. Different product, different audience; our MCP servers map covers the developer side.

Want to see how this applies to your business?

Book a free 30-minute call. We will walk through your specific use case and show you what's possible.

Book Free Discovery Call
Ask me anything