Slack Makes Slackbot Skills Shareable Across Organizations
Users can send a Slackbot skill to another organization through a revocable external link, while administrators control outbound and inbound sharing separately.
Edited by Tyronne Panaino
Slack announced on October 8 that Slackbot skills can now be shared outside the organization where they were created. A skill author can generate an external link, and a recipient in another Slack organization can open the link, make a copy and save it to their own Slackbot.
The release matters to Slackbot users and administrators because it turns a recurring AI workflow into something that can move between organizations instead of being rebuilt from scratch. Slack says links can be revoked and gives administrators separate controls for allowing skills to be shared out of an organization or accepted into one.
A saved workflow becomes a portable asset
Slack describes a skill as a saved, repeatable AI workflow. According to the official Slack announcement, a skill can do more than preserve a prompt: it may run on a schedule, read channels and build on information from earlier work. Sharing therefore moves a reusable operating pattern, not just a block of text.
The recipient does not join the author's original skill in place. Slack says the recipient makes a copy and saves that copy to their own Slackbot. That distinction is useful for understanding the product boundary: the announcement establishes portability, but it does not say that later edits by the author automatically update copies that have already been imported.
For teams that repeatedly exchange operating playbooks with partners, customers or sister organizations, copying can reduce setup work. It also creates a new review point. A workflow that is sensible in one organization may rely on channels, connected systems, terminology or approval practices that do not exist in another. Recipients still need to inspect and adapt what they import before treating it as a production process.
Administrators get separate inbound and outbound controls
Slack says authors can revoke the external links they create. It also documents separate administrator toggles for sharing skills out and accepting skills in. Those controls let an organization distinguish between distribution and intake rather than treating cross-organization sharing as a single switch.
The announcement does not explain what revoking a link does to a copy that a recipient has already saved. It also does not publish a version history, a provenance record for imported skills or a technical security evaluation of the sharing flow. Administrators should therefore read the documented controls as availability and access boundaries, not as evidence that every copied workflow remains current, trustworthy or suitable for the recipient's data.
A practical deployment policy would review the skill's instructions, connected data and possible state-changing actions before wider use. That recommendation is an operational implication of portable workflows; Slack's page confirms the sharing mechanics but does not claim that imported skills have been centrally approved for every workspace.
Slack is also publishing a skill repository
Alongside link sharing, Slack has assembled a repository of example skills contributed from across Salesforce. The collection spans internal communications, incident management, support, document and presentation work, process automation, sales, research and personal productivity. A user can add a listed skill by copying it into Slackbot.
The repository gives prospective users concrete starting points instead of asking them to design every workflow from a blank page. It also broadens the audience for skill authors: a workflow can be shared directly with a known recipient or surfaced through a public collection. The source does not provide adoption figures, quality measurements or independent evidence that the listed workflows improve business outcomes.
What teams should verify next
The confirmed change is that Slackbot skills can cross organization boundaries through copyable links, with link revocation and separate inbound and outbound administration controls. Internal confidence is medium because the evidence is one official Slack product announcement and the sharing behavior was not independently tested in this run.
Useful next checkpoints are documentation for plan and regional availability, permission behavior for connected systems, audit records for imported skills, version and update semantics, and the treatment of saved copies after a sharing link is revoked. Those details will determine whether portable skills function mainly as convenient templates or as governed components in larger agent workflows.
Status
Confirmed. Slack has made Slackbot skills shareable across organizations and published a repository of examples. Security, reliability, adoption and outcome claims beyond the documented product behavior remain unverified.
Sources
Update note: Last reviewed 2026-10-09. We will revise this post if Slack publishes fuller availability, provenance, versioning, permission or revocation documentation.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.