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.
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.
Readers will learn how to access the prebuilt Skills library in Agentforce Vibes and use them to inspect, modify, and deploy metadata changes through a plan and verify workflow.
Why read this
The guide demonstrates practical administration tasks like creating reports and Record-Triggered Flows without writing code.
The article introduces Agentforce Vibes as a browser-hosted Visual Studio Code instance configured specifically for Salesforce development and administration. Although it functions as a developer environment, the piece emphasizes its value for administrators by focusing on the Skills feature, which bundles instructions for distinct configuration actions into reusable packages.
Administrators can browse the preinstalled Skills library through the Toolkit menu after launching Vibes from Setup. The system automatically detects verbs in user prompts and maps them to the appropriate Skills, allowing the agent to execute tasks efficiently without manual selection. Users can also manually add new Skills to expand the toolkit over time.
Changes made through Vibes follow a strict plan, verify, and deploy sequence. Modifications are initially written to the virtualized local filesystem rather than directly to the connected org. Administrators review the generated change plan, approve it, and then trigger deployment using built-in commands or conversational prompts, with the agent handling connection tokens and API calls behind the scenes.
The author strongly recommends testing these workflows in trial environments such as Scratch Orgs, Developer Edition, or sandboxes. Example use cases include creating Custom Objects, adding fields, generating Permission Sets, running SOQL queries, and building Record-Triggered Flows. While early deployments may encounter errors or require multiple attempts, the structured approach provides a safe way to explore AI-assisted platform configuration.