Salesforce in Claude: 37 Sales Skills Evaluation Guide
On this page
Quick answer
Salesforce says the initial Salesforce in Claude plugin contains 37 prebuilt sales skills, with meeting preparation, deal-health review, and pipeline review as named examples. The checked official pages do not itemize all 37 skills, so do not invent a complete list from the headline count.
For a real pilot, export or manually record the exact skill inventory visible in the tenant. For each skill, document its data reads, possible writes, connectors, permission behavior, approval point, output contract, failure modes, audit events, owner, and measurable sales outcome.
Build the skill register
| Field | What to capture |
|---|---|
| Identity | Exact skill name, description, version, availability, and owner |
| Trigger | User request, schedule, event, or dependent workflow |
| Reads | Salesforce objects and fields, Slack, email, and other Claude connectors |
| Reasoning | Rules, time window, calculations, missing-data behavior, and citations |
| Writes | Records, fields, workflows, messages, recipients, and external effects |
| Authority | User identity, permission sets, sharing, business rules, approvals, and denial |
| Evidence | Inputs, source links, proposal, confirmation, final action, and audit record |
| Outcome | Time saved, completeness, correctness, action acceptance, and sales result |
Repeat the register after every pilot update. A stable marketing name does not prove the underlying skill, connector, prompt, or action contract is unchanged.
Test the named skill examples
Meeting preparation
Define the exact account, meeting, attendee, opportunity, activity, email, and Slack scope. Require source links and timestamps. Test two people with similar names, multiple related accounts, confidential channels, missing activity, stale opportunities, and a seller who cannot see part of the account team.
The output should distinguish verified record facts, communication-derived context, and model inference. Never present a predicted concern as a customer statement.
Deal-health review
Write the health rubric before comparing results. Identify stage, age, amount, activity, stakeholders, next step, close-date movement, product, support, and qualification fields. Decide how missing or conflicting data affects the result.
Compare the Claude review with a saved dataset and an accountable manager. Measure false alarms, missed risks, unsupported explanations, and the actions users take—not just whether the narrative sounds plausible.
Pipeline review
Pin filters, hierarchy, currency conversion, fiscal period, stage mapping, forecast category, close-date window, record sharing, and excluded deals. Reconcile totals and samples against a saved Salesforce report.
Require preview and approval before bulk changes. Test partial completion, validation-rule failure, duplicate invocation, concurrent user edits, and rollback or correction.
Classify skills by action risk
| Class | Example | Minimum gate |
|---|---|---|
| Read and summarize | Meeting preparation | Source links, freshness, visibility, inference labels |
| Recommend | Deal-health analysis | Fixed rubric, evidence, reviewer, no silent write |
| Update internal record | Change a bounded field | Preview, confirmation, validation rule, before/after audit |
| Run workflow | Advance an approved process | Preconditions, idempotency, partial-failure handling, owner |
| Communicate externally | Send email or message | Recipient and content preview, explicit approval, delivery evidence |
Salesforce says customers can choose whether Claude asks before external email. Make that choice risk-based and test it. A pilot should begin with approval on every external send and material write.
Evaluation scorecard
For each skill, report:
- task success against a fixed case set;
- record and field precision, completeness, and freshness;
- denied-access and cross-user leakage results;
- unsupported claim and missing-source rate;
- write accuracy, duplicate rate, partial-failure recovery, and rollback effort;
- human review time, override rate, adoption, and downstream business outcome;
- incident, support, and operating cost.
Use the pilot guide for availability, the permissions guide for authorization tests, the Claudeforce versus Agentforce guide for product direction, and the readiness check for evidence completeness.
Frequently asked questions
Does Salesforce publish all 37 skill names?
The checked announcement confirms 37 prebuilt sales skills and names meeting preparation, deal-health review, and pipeline review as examples, but does not provide a complete itemized list. Inventory the exact skills shown in the pilot tenant.
Are the 37 skills generic CRM prompts?
Salesforce says the skills were built with Anthropic for Claude’s reasoning, tool use, and generative UI. That description still requires independent workflow, data, action, and outcome testing.
Should every skill be enabled for every seller?
No. Assign skills by role and workflow, preserve least privilege, test record visibility and actions, and require stronger approvals for external communication or material record changes.
Will the skill count stay at 37?
Not necessarily. Salesforce says more prebuilt skills will begin launching in late 2026.
Official sources
Source check: August 29, 2026. Recheck and version the live skill inventory, effects, permissions, connectors, packaging, and release notes before use.