The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

AI Skills let Agentforce Coworker run repeatable team tasks (opens in a new tab)

You will learn what AI Skills in Agentforce Coworker are, how they differ from Prompt Builder templates, and how sharing and permissions are meant to control them.

Why read this

The author notes that admin-level maintenance guidance is still missing.

AI Skills are reusable sets of instructions that tell Agentforce Coworker how to complete a repeatable task. The author compares them to skills in Claude: the task is defined once, and anyone with access can run it the same way each time. Salesforce says Coworker is the first Agentforce agent to include them. They were announced in pilot in September, with general availability planned for October, as part of a wider Coworker expansion covering Microsoft Teams, mobile and desktop apps, and an MCP server.

The article separates AI Skills from Prompt Builder. A Prompt Template gives a repeatable way to prompt an LLM for text output, such as a sales email or record summary. A skill describes a whole task so an agent can work through each step and take action, which the author says makes skills the more powerful of the two. Salesforce’s examples include account research, meeting prep, case classification, flagging renewal risk and case summaries, all work people repeat and often do slightly differently each time.

On governance, skills are private until the creator shares them, and sharing is controlled by the creator. A skill runs as the person using it, and Coworker respects existing permissions, so users should only see records and objects they already have access to. Coworker also pauses for approval before it creates or updates a record. The author argues this is powerful enough that admins need clearer guidance on maintaining skills across a team, and promises a deeper walkthrough later.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

AI Skills in Agentforce Coworker are now generally available (opens in a new tab)

You will learn what an AI Skill is, how users build, share and run one in Coworker, and how it differs from a Prompt Builder Prompt Template.

Why read this

You will also see how permissions and approval gates apply when a skill runs.

Prompt Template

  • Reusable prompt for an LLM
  • Produces text output
  • Example: a record summary

AI Skill

  • Describes an entire repeatable task
  • Agent works through each step
  • Can take action on records
A Prompt Template produces text, while a skill runs a whole task

AI Skills in Agentforce Coworker are now generally available. A skill is a reusable set of plain-language instructions that tells an agent how to complete a repeatable task. Unlike a Prompt Template, which produces text output such as an email or a record summary, a skill describes an entire task that the agent works through step by step and can act on.

Users build a skill by chatting with Coworker. They name it, say when to use it and list its steps, then refine the steps in Coworker or in Skill Builder. Skills are private by default and are shared with colleagues once they work. A skill is run by typing a forward slash, using the skills icon, or simply asking, and Coworker can select the matching skill from the user’s intent.

Skills respect the org’s existing controls. A skill runs as the invoking user with their row-level and object-level permissions, and Coworker asks for approval before creating or updating a record. The article suggests example uses such as account research, call prep, competitive battle cards, case summaries and campaign reporting.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Agentforce Coworker is switched on in some orgs, so check it before users ask (opens in a new tab)

The reader will learn what Agentforce Coworker does, how to find out whether it is already enabled in their org, and why sharing and permissions should be reviewed before rollout.

  1. Check whether Coworker is already on
  2. Review sharing and fix over-broad access
  3. Build a few focused agents
  4. Tell users what Coworker can do
A suggested order for rolling out Agentforce Coworker in an org

Agentforce Coworker is described as Salesforce’s AI assistant for employees, sitting in the search bar and routing user requests to specialist agents. Without well-built agents it can still answer questions from org data but can do little else. The article says it reached general availability at Dreamforce and that more than 185,000 people use it.

The article notes that from August 10, 2026, Salesforce automatically turned on Coworker for customers with unmetered user-based AI seats, which can be checked under Setup, Agentforce Coworker. HIPAA, health and life sciences, and government orgs were not auto-enabled, and Coworker is not covered by the HIPAA Business Associate Addendum. Pricing is said to depend on contract terms.

The main warning is that Coworker respects each user’s existing permissions and Sharing Rules, so it will surface any over-broad access quickly. The suggested rollout is to check the enablement setting, review sharing first, build a few focused agents for common requests such as renewal risk and case status, and tell users what the assistant can and cannot do.

Read the original at dev.to (opens in a new tab)

Worth reading?

Agentforce Coworker adds Teams, mobile and desktop access and a $50 per-user price (opens in a new tab)

You will learn what Agentforce Coworker now does across Microsoft Teams, mobile and desktop, what is available now versus later, and how it respects Salesforce permissions and governance.

  1. Employee delegates a job
  2. Coworker plans the steps
  3. Agents and flows run
  4. Results return for review
How Coworker handles a delegated job, as described in the article

Salesforce reports that more than 185,000 users are working with Agentforce Coworker, with usage up 21x in three months. The release adds Conversation History, reusable Skills and scheduled tasks, plus connections to Google Workspace and Microsoft 365 so that email, calendar and file data can sit alongside Salesforce records. Coworker can be used from Microsoft Teams and new iOS, Mac and Windows apps.

Coworker plans multi-step jobs, coordinates Agentforce agents, flows and business actions, and returns results for review. It is described as working within existing Sharing Rules, permissions and configured access controls, with approval and audit capabilities for supported operations. A new $50 per-user, per-month option is offered for predictable budgeting.

Availability is staged: Google Workspace and Microsoft 365 connectivity, Conversation History, Skills and the per-user SKU are available now; the Teams, iOS and desktop apps and a Coworker MCP server are slated for November 2026; Daily Digest, scheduled tasks and mobile apps for Field Service, Consumer Goods Cloud and Life Sciences Cloud are expected in December 2026. The article notes pricing and features may change, and much of the piece is customer testimony and marketing framing.

Read the original at Salesforce News (opens in a new tab)

Also told by dev.to (opens in a new tab)

Worth reading?

Salesforce unveils AIforce apps linking platform data to Claude and Slack (opens in a new tab)

You will learn what the three AIforce applications are, what each does with Salesforce data, and what the Claude Code plug-in adds for developers.

Why read this

The piece is a brief overview without implementation detail.

AIforce initial release

  • Claudeforce
  • Slackforce
  • Agentforce Coworker
The initial AIforce release is made up of three applications

Salesforce announced AIforce at Dreamforce, a set of applications that connect platform data and workflows to Claude and Slack. The initial release has three parts: Claudeforce, Slackforce and Agentforce Coworker. Claudeforce comes out of an expanded partnership with Anthropic and ships with 37 pre-installed sales capabilities, from prospecting to opportunity management, plus a Claude Code development add-on with more than 40 further tools. Deloitte, GitLab and Legora piloted it, and it is now in beta for all customers.

Slackforce brings Salesforce data into Slack conversations, letting teams combine information from different sources, apply filters and take actions through interactive surfaces. The upgraded Slackbot assistant and Slack CRM feature can update files and create records from simple text commands.

Agentforce Coworker works inside Salesforce’s internal Lightning environment as a digital assistant that uses customer history and activity. According to the company, it needs no data migration or new permission settings, and it recorded 100,000 activations in its first 35 days.

Read the original at dev.to (opens in a new tab)

Worth reading?

Agentforce Coworker setup, security and routing within AIforce (opens in a new tab)

It explains how Agentforce Coworker fits into the AIforce stack, how its routing and security model work, and gives a concrete setup path via Data 360 and Salesforce Go.

Agentforce Coworker is presented as one of three main pillars of AIforce, Salesforce’s interface layer announced at Dreamforce ’26. Its purpose is to bring Salesforce data and agents to where users already work, such as Lightning Experience, Slack, Microsoft Teams or AI tools, instead of making them switch between applications. It targets two problems: tab-switching between many tools, and users struggling to know which agent to use for a task as agentic workforces grow. It acts as a router agent, the front door to an org’s agents, sending queries to the right one. Its foundations are Agentforce (the digital workforce layer it orchestrates), Customer 360 (CRM as the unification point for customer data) and Data 360 (the grounding layer that indexes and governs data for AI).

The piece describes three interaction modes. Find lets users ask questions in plain language and get contextualized answers drawn from CRM data, Slack, files, knowledge bases and other connected sources. Catch Up proactively surfaces changes in the user’s scoped workspace, such as what they missed while in meetings. Plan and Act takes outcome-level instructions and routes the work to the appropriate agent. Security relies on the existing Salesforce model: profiles, Permission Sets and Sharing Rules still apply, so Coworker only sees what the user is allowed to see, following least privilege.

The author’s hands-on setup path begins with confirming Data 360 is enabled, checked under Data Cloud Setup Home, and assigning the Agentforce Coworker Admin Permission Set to administrators. Coworker is then switched on through Salesforce Go by searching for it in Setup. Administrators choose data sources under Manage Data, with CRM data enabled by default. Finally, users need the Agentforce Coworker User Permission Set, which can be assigned via Manage Access to Agentforce Coworker in Manage Users. In use, the Ask button beside global search opens the Ask: Home tab, and the author recommends starting a fresh session for unrelated prompts to avoid carrying over context.

The article closes with caveats. Data 360 must be enabled before Coworker works, though not every data set must be shared with it. Coworker is available in Enterprise, Unlimited and Agentforce 1 Editions. Billing is either consumption-based through Flex Credits or seat-based with usage caps, so costs can rise quickly and the author suggests monitoring value with tools such as Agentforce Grid and Agentforce Observability. The author also advises planning and cleaning data and permissions before rollout.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?