AI Skills in Agentforce Coworker are GA. Learn how to turn your team’s best workflows into reusable skills that run with each user’s permissions.
Your Best Rep’s Call Prep Lives in One Person’s Head. Coworker AI Skills Gets It Out.
AI Skills in Agentforce Coworker went generally available on November 10. Describe a workflow once in plain language, share it, and anyone on your team can run it the same way under their own permissions. Here is how to build skills people keep using after week one.
AI Skills turn a repeatable workflow into plain-language instructions that Agentforce Coworker runs the same way every time. Skills stay private until you share them, run with each user’s own CRM permissions, and pause for approval before changing records. Start with one weekly workflow your best person already does well, write it the way you would explain it to a new hire, and share it once it works.
In This Article
Every sales team has one rep whose first calls just go better. She checks the account’s open cases before she dials. She reads the last few opportunity notes, looks for a competitor name, and shows up with two questions nobody else thought to ask. Ask her to write it down and you get a bulleted list that captures maybe half of what she actually does.
Then she takes two weeks off. Or gets promoted. The playbook leaves with her.
That is the problem Salesforce points at with AI Skills in Agentforce Coworker. As of November 10, 2026, skills are generally available, and Coworker is the first Agentforce agent to include them. You describe a task once, in plain language, and anyone you share it with can run it the same way. New hire, teammate, the person covering your accounts while you’re out.
The timing makes sense. On November 4, Salesforce reported that Coworker usage grew 21x in three months and passed 185,000 users. Once that many people ask the same AI teammate for help every day, the next obvious move is letting the best answers get reused instead of rebuilt from scratch each morning.
Coworker already sits behind the Ask button next to Salesforce global search, and it routes requests to specialized Agentforce agents for you. Skills give that front door a memory for how your team likes the work done.
If you’ve built anything in Prompt Builder, your first question is probably fair: isn’t this a prompt template with a friendlier front end? Salesforce draws the line clearly. A prompt template asks a model for text, grounded in your Salesforce data. A skill describes a whole task, so Coworker works through each step and can take actions along the way.
The way I explain it to a steering committee: a template hands you a paragraph, and a skill hands you a finished job. A custom Agentforce agent sits one level up again. It owns an entire domain or channel and gets designed, tested, and deployed by your admins and developers.
| Prompt Template | AI Skill in Coworker | Custom Agentforce Agent | |
|---|---|---|---|
| Who builds it | Admins in Prompt Builder | Any Coworker user, by chatting | Admins and developers in Agentforce Builder |
| What it delivers | Grounded text output | A completed multi-step task | Ongoing handling of a domain |
| How it runs | Called from Flow, Apex, or agent actions | Slash command, skills icon, or a plain request | Deployed to a channel or called by other agents |
| Best fit | Consistent summaries and drafts | Personal and team workflows | Customer and employee processes at scale |
These three don’t compete. A well-run org will use all of them, and the healthy pattern is upward movement: a skill that half the company runs every day is a strong candidate for your admins to turn into a properly governed agent or Flow later.
An AI teammate that coordinates Agentforce agents to get work done in Salesforce, Microsoft Teams, and on mobile.
A reusable set of plain-language instructions that tells Coworker how to complete a repeatable task.
The editor where you can change a skill’s steps directly instead of refining them through chat.
Lets users pick up a Coworker conversation where they left off, across Salesforce, Teams, and the new apps.
Here’s the part I like most. Nobody opens Setup. A skill starts as a conversation: you open Coworker from the Ask button at the end of the search bar, go to Skills in the left sidebar, and click New. Coworker then interviews you.
Coworker asks what the skill should be called, when it should be used, and what the steps are. Answer the way you’d brief a sharp new hire.
Run it against a real account and tighten what came back. Keep refining in chat, or open the steps in Skill Builder and edit them directly.
Skills are private by default. Yours stays private until you share it with the people who need it, so you can iterate without an audience.
What a good skill sounds like
Below is the content I’d give Coworker for a first-call prep skill. It isn’t a file format, and you don’t write it in one go. Coworker shapes it with you during the build chat. What matters is the specificity: named objects, time windows, and an output someone can use in thirty seconds.
Skill · Plain LanguageName: First Call Prep Use when: A rep asks to prepare for a first meeting with an account Steps: 1. Pull the account's open opportunities and the last three activity notes. 2. List open cases from the past 90 days with their status. 3. Find competitor mentions in notes and summarize each in one line. 4. Suggest two discovery questions based on what we still don't know. 5. Draft a one-page brief and offer to log it as a task on the account. // Step 5 proposes a record change, so Coworker asks before writing.
What happens when someone runs it
That “use when” line does more work than it looks. Coworker can select a skill on its own based on what the user asks, so a clear trigger description is what turns “prep me for Acme tomorrow” into your First Call Prep skill instead of a generic answer.
Salesforce’s own launch examples cover account research, call preparation with record updates, competitive battle cards, case summaries with draft replies, and campaign performance reports. I’d add one for customer success. Here’s how I’d frame each so it lands with the team that will run it.
Pulls CRM history, recent activity, and connected sources into a short snapshot before any account conversation.
The brief from Section 3, plus an approved task logged on the account so the prep is visible to the whole team.
Gathers what your org already knows about a competitor and formats it the way product marketing wants it read.
Summarizes a case thread and drafts a reply in your support voice. The agent reviews and sends.
Produces the same weekly campaign readout every time, with the metrics your marketing leader actually asks about.
Checks upcoming renewals for quiet accounts, open escalations, and stalled opportunities, then lists the ones to call first.
How to pick which workflow goes first
Not every task deserves to be a skill. The ones that pay off fastest share a few traits, and you can score candidates in a ten-minute team meeting.
A workflow someone runs every week returns the build time quickly. A quarterly task can wait.
This is where a skill earns its keep. It lifts the average toward the best without a training program.
A brief, a reply draft, a ranked list. If people argue about what a good result looks like, settle that first.
Start with skills that gather and summarize. Add record updates once the team trusts the output.
The build experience is simple on purpose, and that’s exactly why it spreads. It also means the design thinking moves out of Setup and into a chat window, where anyone on the team can do it. Two platform behaviors shape how I’d plan a rollout to a few hundred users.
- Each run uses that person’s row-level and object-level CRM permissions
- A manager and a rep running the same skill can get different results
- Coworker never bypasses your existing security model
- Design tip: tell the skill what to say when a record isn’t visible
- People can experiment freely before anyone else sees the skill
- Shared skills become part of how a team works, fast
- Popular skills deserve the same care as any shared asset
- Design tip: give every shared skill one named owner
Before you share a skill with your team
The GA launch focuses on the person building and running skills, which is the right place to start. For a larger rollout, pair it with a light operating model of your own: a naming convention, an owner per shared skill, and a quarterly review. That’s what lets the library grow to fifty skills without becoming a junk drawer.
A call prep skill that reads activity notes is only as sharp as the notes reps log. Skills reward teams that already keep clean records, and they give everyone else a very practical reason to start.
Skills arrive as part of a wider Coworker expansion, and the surface area is growing quickly. A skill your team builds in Lightning today gets more places to live over the next few weeks.
Salesforce introduces Agentforce Coworker as an AI teammate inside Salesforce global search.
Usage up 21x to 185,000+ users. Google Workspace and Microsoft 365 connectivity, Conversation History, and the $50 per-user, per-month option are available.
Coworker becomes the first Agentforce agent with reusable skills.
Coworker in Microsoft Teams, an iOS app, Mac and Windows desktop apps, the Coworker MCP server, and a free trial for Flex Credits customers.
Recurring work runs on a schedule, and a morning digest greets users with their top priorities.
The Ask button next to global search, where most teams will build their first skills.
Hand work to Coworker from the chat app many employees already keep open all day.
Native apps for iPhone, Mac, and Windows, with Conversation History carrying context across them.
Model Context Protocol connectivity, so Coworker’s Salesforce context can reach tools like Claude and ChatGPT.
Connected sources give skills more to work with, from calendar context to shared documents.
Recurring work that runs without someone typing a request first. The Monday morning prep problem, finally handled.
December is the release I’m watching. Today a person still decides when to run a skill. Scheduled tasks and the Daily Digest move Coworker toward work that’s ready before anyone asks. Combine that with a library of well-built skills and the Monday pipeline review prep could be sitting in your inbox before the meeting starts.
So here’s the exercise for this week. Name the one person on your team whose work you’d most like everyone to copy. Book twenty minutes with them, open Coworker together, and turn what they do into a skill.
The official walkthrough of building, sharing, and running skills in Agentforce Coworker, including the demo video.