Slackbot Skills: What to Verify, What to Assign, and What to Lock Down

Somewhere on your sales team, there's a rep whose follow-up emails actually get replies. Ask how, and you'll probably get a shrug and a prompt pasted from a notes app. Slackbot skills are Slack's answer to that. The instructions get saved once, and anyone on the team can run them.
It's a good idea, and setting one up takes minutes, which is exactly why admins should slow down for a moment. A skill isn't a document sitting in a folder. It runs with the permissions of whoever uses it, it can reach into the apps you've connected, and on most Slack plans every run draws on a limited allowance. Govern skills the way you'd govern a template library and you'll spend your attention in the wrong place.
In Slack's own words, skills are step-by-step instructions that tell Slackbot how to handle a specific task. Any member can create one. Owners, admins and Skill Managers can verify skills and switch them on for whole groups.
This is more pressing now than it was in the summer. Salesforce's Core, Advanced and Max editions, launched in September, include Slack and Slackbot, and Slack's pricing page says ongoing Slackbot access is coming for Salesforce customers who connect their CRM. Plenty of admins are about to inherit skills before anyone has written down how they should work.
Most of the risk sits in one place
It helps to think of a skill as moving through three stages. It starts out existing: somebody built it, or a colleague shared it with them. It becomes findable once an owner, admin or Skill Manager publishes it to the catalog. And it starts running for a group when one of those same people auto-enables it for a user group or the whole company.
The first stage is personal productivity. Policing it mostly pushes good prompts back into notes apps, where nobody can see them at all. The second looks like approval even when nobody approved anything. The third is where the stakes jump, because an edit to an auto-enabled skill reaches everyone in that group at once. Slack's developer docs draw the same line: a published skill reaches nobody until someone adds it to their library or an admin auto-enables it.
So our advice is to leave creation alone and put your rules on publishing and assignment.
The purple badge isn't a lock
Verification is available on paid plans, and a verified skill gets a purple badge. When there are five follow-up skills floating around, that badge is how people find the one leadership actually trusts.
What it doesn't do, as far as Slack's documentation goes, is freeze the skill. Slack does say that updates to an assigned skill apply right away. Put those two facts together and a verified skill can change underneath everyone who relies on it.
We'd treat the badge as a promise about the process behind a skill rather than the words in it today. Before giving it out, check that the skill has an owner who sits on the team that uses it, that someone has run it against a handful of real requests (including at least one messy one with half the inputs missing), and that there's an agreed way to handle edits. That last part is the one teams skip, and it's the one that matters most once a skill is switched on for a group.
How skills spread without anyone deciding
Auto-enable is the obvious control. Two others move skills just as far with far less ceremony.
The first is skill sets. A set holds up to 25 skills, and anyone with access to it can use everything inside, including skills added later, according to Slack's skills guide. Drop a skill into a popular set and you've effectively assigned it without ever touching auto-enable.
The second is external links. By default, members can create a link to a skill and send it to someone outside the company, who then saves their own copy. Revoking the link later stops new copies but does nothing about the ones already saved.
Think about what a good sales skill contains: discovery questions, objection handling, pricing guardrails, your tone of voice. A useful test is whether you'd mind a competitor's rep having it. If you would, change the setting before the first link goes out. Owners and admins will find Allow members to share skills with other organizations and Allow members to add skills shared from other organizations under Admin, Workspace settings, Settings, Slackbot on Free, Pro and Business+. On Enterprise plans they live under Tools & settings, Organization settings, Settings, Slackbot.
Skills that write to Salesforce deserve a stricter bar
When you build a skill, you can name the apps and MCP servers it should use. Separately, Slackbot can create and update Salesforce records by default, within each person's Salesforce permissions, and the person always reviews and approves the change before it happens. Record actions need Business+ or Enterprise, and admins can narrow them to certain objects or switch them off.
The approval step is a real safeguard. The weakness is human. A prompt someone sees twenty times a day stops being a decision and turns into a reflex. A skill that makes a record update a one-click habit therefore deserves more scrutiny than one that drafts a paragraph, especially for reps who already work deals in Salesforce channels, where the record sits right next to the conversation.
In practice, we'd give write-capable skills a named data owner, a sandbox test and a narrower assignment, and we'd label them clearly in the spec so nobody has to guess which kind they're looking at.
What a skill costs to run
Building a skill costs nothing. Running one uses Slackbot, and Slack's pricing page sets Slackbot usage by plan:
Slack plan | Slackbot usage (as of November 15, 2026) |
Free and Pro | Consumption-based |
Business+ | 15 messages per user each week. Invoice customers can buy Flex Credits through Salesforce for higher limits |
Enterprise+ | Unlimited |
That Business+ limit changes how you should design skills. If a skill needs three rounds of back-and-forth before it produces something usable, it isn't just slow. It has used up a fifth of that rep's week. The better skills ask for every input up front so the first answer lands, and if the limit itself becomes the bottleneck, it's worth comparing what each Slack plan gives you before you assign skills to large groups.
Where Flex Credits apply, Salesforce's rate card from November 3 lists a Slackbot standard action at 40 credits and an advanced action at 200. At the US list price of $500 per 100,000 credits, that comes to $0.20 and $1.00 per action by our arithmetic. Slack doesn't publish which requests count as advanced, so ask your account team before you auto-enable a heavy skill for a big group.
A one-page spec before anyone builds
Ten minutes on this settles most arguments before they start.
Field | Example |
Purpose | Draft a first-touch email from the approved template |
Owner | Sales enablement lead, on the sales team |
Inputs required up front | Lead name, company, product interest |
Apps and access | Salesforce, read only |
Never | Quote pricing or discounts |
Assigned to | SDR team only, and not in any skill set |
Edits | Owner only, announced in the team channel first |
Twenty minutes a month
Slack's skills dashboard shows who created each skill, which groups it's assigned to, how often people use it, and how many have added it. That's enough for a short monthly look at a few questions. Which heavily used skills still aren't verified? Which ones do the same job and should be merged? Which predate your latest template or price change? Which have lost their owner, and which have quietly been shared outside the company?
On an Enterprise organization, you can go a step further. Slack's Skills API lets you keep skill instructions in source control, deploy them from CI, publish with admin.slackbot.skills.publish and auto-enable with admin.slackbot.skills.setAutoEnabled. Every change then has an author, a date and a reason, which is the edit rule from earlier, enforced by default.
FAQ's
Who can create Slackbot skills?
Any member. Owners, admins and Skill Managers are the ones who publish skills to the catalog, verify them and auto-enable them for groups.
Does verifying a skill stop people from changing it?
Slack's documentation doesn't describe verification as a lock, and it says updates to an assigned skill apply right away. Pair the badge with a clear rule for who edits.
Can I take back a skill someone shared outside the company?
Only partly. Revoking the external link stops new copies, but anyone who already saved one keeps it.
If you only do one thing this week
Check the two external sharing settings. They take a minute to change, and they guard the only risk on this list you can't clean up afterwards.
After that, the real work is deciding what runs for whom, with which permissions and on which plan. That's what our Slack services team spends most of its time on when Slackbot and Salesforce roll out together.
.png)




Comments