A prebuilt skill is a workflow somebody else wrote
Salesforce in Claude, the plugin at the centre of the Claudeforce announcement Salesforce and Anthropic published on August 27, 2026, ships with 37 prebuilt sales skills. The release names three of them: meeting prep, deal health review, and pipeline review. It says sellers can reason over live revenue context, automate pipeline updates, and take governed action from inside Claude, with actions routed through Salesforce so business rules are enforced.
A skill in this sense is a packaged piece of sales process: what to read, how to weigh it, what to say back, and sometimes what to write. Somebody at Salesforce or Anthropic decided what a deal health review looks like before your org connected the plugin. The governance claim in the source announcement covers the moment a write reaches Salesforce. Everything the skill decides before that moment is our subject.
Deal health is an opinion your org already holds
Most sales orgs have a written definition of a healthy deal, even if it lives in a slide from the last kickoff. It might be stage exit criteria, a set of MEDDIC fields on the Opportunity layout, or a rule that nothing sits in Proposal for more than thirty days. That definition was argued over, and the people who argued over it still work there.
A prebuilt deal health review carries its own definition. The release does not say what signals the skill weighs, whether an admin can point it at custom fields, or whether it can be told that a missing economic buyer counts heavily against a deal while a missing champion counts a little less. Our guess is that some of this is configurable and some is fixed, and we would want to know which before a rep sees the first score.
Pipeline review used to happen in a room
In most orgs pipeline review is a meeting. The manager opens the same forecast report the reps see, walks down the list, and asks about the deals that moved or should have. When someone disputes a number, the argument is about a field on a record everyone can open.
A pipeline review skill in Claude gives each seller a private version of that meeting, built from live revenue context and the Slack threads the plugin can reach. It also means the seller walks into the real review holding a summary the manager has never seen, built on a reading of the pipeline the manager did not choose. We have argued before that who owns the definition of revenue is a governance question, and a prebuilt skill answers it quietly, per seller, with no meeting.
The update skills are the ones your validation rules will meet
The release names automating pipeline updates as one thing the skills do. Our sibling piece on the read path and the write path covers what happens when that write lands on a validation rule, so we will stay on the skill side. A prebuilt update skill decides which fields to change from its own reading of the deal. Your validation rule decides whether the resulting record is complete. Nothing in the release says those two definitions were written together.
A rep asks Claude to move a deal to Negotiation. The skill updates Stage and Close Date. Your org requires a populated Decision Criteria field before Negotiation, a rule added after a bad quarter two years ago. The write is rejected, business rules enforced, exactly as promised. Whether the skill then asks the rep for the missing field or reports a failure is the workflow question, and it sits with the skill rather than the platform.
Day one for every seller means day one for every team
The release says an admin connects the plugin once, with authentication and permissions managed centrally, and every seller gets access from day one with no per-user setup. Our sibling on where the permission boundary should sit covers the identity side. One connection means one set of skills for the enterprise team that runs nine-month cycles through a deal desk, the velocity team that closes in a fortnight, and the renewals team that never touches Stage.
Those teams run different record types, required fields, and page layouts, and that difference is the process. A prebuilt meeting prep skill does not know that the renewals team cares about usage data while the enterprise team cares about the procurement contact. If the skills can be scoped by profile or record type, the release does not mention it, so that is our second question for the account team.
Write your definition down before the skill supplies one
Salesforce says the plugin is with select pilot customers now, expects an open beta in September 2026, and plans additional prebuilt skills in the third quarter of 2026. The best use of those weeks has nothing to do with the plugin. Take the three named skills and write one page for each. What meeting prep should read in your org and what it must never surface. What deal health means in your stage exit criteria, field by field. What a pipeline review should output and who sees it before the manager does.
When the beta opens, pick one live opportunity, run the three skills against it, and put the output next to what the rep's manager would have said. Where the two disagree, you have found the process the prebuilt skill is carrying, and you can decide whether to adopt it, configure it out, or keep the skill off for that team. That decision needs a named owner, which is why an agent readiness check belongs before the beta, alongside what a Salesforce team should settle before September. Invite the sales manager who wrote the stage exit criteria to the comparison. They will know within a minute whether the skill agrees with them.
