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?

Connecting Data Cloud to Agentforce Studio to build an agentic RAG pipeline (opens in a new tab)

Readers will learn how to configure a custom retriever in Agentforce Studio, create a Flex Prompt Template in Prompt Builder, and deploy a subagent that grounds responses in live Data Cloud vector data.

The article explains how to configure a custom retriever in Agentforce Studio to fetch vectorized chunks from a Data Cloud data model object. It details setting result limits, mapping target fields, and activating the retriever so it can be referenced elsewhere.

Next, it walks through creating a Flex Prompt Template in Prompt Builder by modifying a standard knowledge template. The author shows how to add the retriever as an action, bind the query parameter, and write strict instructions that force verbatim source extraction and handle missing data gracefully.

Finally, the piece covers assembling an Agentforce Service Agent, keeping only essential routing subagents, and linking the custom Prompt Template as an action. The author validates the workflow by testing destination queries and confirming the agent returns accurate, grounded answers sourced directly from the live Data Cloud index.

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

Worth reading?

Must-read

Using Prompt Builder and generative AI to manage requirements and prevent scope creep (opens in a new tab)

Readers will learn how to structure discovery notes, audit meeting transcripts, and build low-fidelity prototypes using Prompt Builder to catch vague requirements early.

Why read this

The piece also outlines practical safeguards against AI hallucinations when reviewing change requests.

  1. Extract requirements from raw discovery notes
  2. Flag scope deviations in meeting transcripts
  3. Build quick prototypes to catch edge cases
  4. Ground change requests with Prompt Builder
  5. Keep final approval with human project managers
A five-step AI workflow to structure requirements, audit meetings, prototype solutions, and maintain human oversight

Scope creep often stems from unclear requirements and unapproved changes during Salesforce implementations. The article proposes using generative artificial intelligence as a systematic reviewer to compare stakeholder requests against signed-off project charters before development begins.

Practitioners can feed raw discovery notes into large language models to extract structured acceptance criteria, dependencies, and open questions. Meeting transcripts should be processed to flag deviations from the approved scope, creating a verifiable audit trail without relying on human memory.

Interactive prototypes generated quickly with AI help align stakeholder expectations with technical deliverables, exposing edge cases that text documents miss. For teams already tracking requirements inside the platform, Prompt Builder can ground automated prompts to evaluate change requests against existing records.

Despite these advantages, the author warns that AI systems frequently struggle with reproducibility and hallucination. The guidance emphasizes keeping final approval authority with human project managers while using AI strictly as an early warning and documentation assistant.

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

Worth reading?

Must-read

Configuring permissions and security guardrails for Agentforce and Prompt Builder (opens in a new tab)

Readers will learn how to structure Permission Sets and groups for different AI roles, understand how field-level security applies at runtime, and implement human-in-the-loop controls for autonomous agents.

Generative AI Security Setup

  • License and Permission Set Allocation
  • Field-Level Security Inheritance
  • Agentforce Action Boundaries
Breakdown of the three core pillars for AI governance

The article outlines a structured approach to managing generative AI access by separating feature availability through Permission Set Licenses from functional capabilities via Permission Sets and Permission Set Groups. It defines four core roles, including an AI System Administrator, Prompt Template Author, Standard End-User, and Agentforce Runtime User, emphasizing that bundling permissions into groups prevents security drift when users change departments.

When prompts execute on record pages, Prompt Builder enforces security before data reaches the large language model. The system validates object read access, applies field-level security by nullifying restricted merge fields, and respects Sharing Rules. A practical example shows how a customer support representative without access to a profit margin field receives a blank value, ensuring sensitive financial data never leaves the organization or enters the model cache.

For autonomous execution, Agentforce supports three action modes ranging from full autonomy to requiring explicit user approval. The piece recommends starting with safe defaults that allow read-only lookups while triggering human confirmation for write operations. It demonstrates a human-in-the-loop pattern where an agent drafts an email via a flow, leaving the final review and send capability restricted to a human user.

Finally, the guide provides a deployment checklist covering permission group assembly, field security verification, action boundary configuration, and Einstein Trust Layer settings like zero data retention and data masking to ensure compliance before production rollout.

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

Worth reading?

Configure Prompt Builder to ground Flex templates with Salesforce Files (opens in a new tab)

Readers will learn how to configure a Flex Prompt Template in Prompt Builder to automatically pass Salesforce Files attached to a record as context for an AI model.

Why read this

The guide covers prerequisites, step-by-step setup, sample prompt syntax, and security best practices.

Prompt Builder now allows administrators and developers to attach Salesforce Files from a record Related List directly into a Flex Prompt Template. This grounds artificial intelligence models with actual document content instead of relying solely on record fields, reducing manual review time for tasks like vendor evaluation or contract analysis.

The setup requires three main actions inside Prompt Builder. First, create a Flex Prompt Template to define custom inputs. Second, add an Object type input pointing to the target record, such as Account. Third, insert the Notes and Attachments Related List as a resource within the prompt workspace so the system can resolve the attached files during execution.

Only Salesforce Files are supported, meaning legacy classic attachments must be converted before testing. Builders must assign the Prompt Template Manager Permission Set or Customize Application permission, and select an artificial intelligence model that accepts file inputs. The article recommends previewing templates with representative records, screening documents for sensitive data, and maintaining human oversight for generated summaries.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Recommended

Salesforce engineers use Agent Graph to keep AI-drafted Prompt Templates reliable (opens in a new tab)

This explains how Salesforce keeps LLM-assisted prompt creation deterministic: graph-controlled routing, server-side record identity mapping, and sentinel-tagged structured output.

Why read this

It is useful if you are designing any AI feature where model output must remain safe and schema-valid.

Salesforce engineers describe building Assistive Authoring for Prompt Builder, which turns a plain-English requirement into a working Prompt Template in under a minute instead of the roughly 25 minutes an experienced admin needs today. The core risk they targeted was not obviously bad output but plausible-looking templates that break at runtime because the model invented a field, corrupted a record ID, or returned malformed metadata.

The solution uses Agent Graph to split the work into a router node and three specialized sub-agents for generating, refining, and clarifying requests. State variables carry client-supplied and runtime context, bound inputs pass only what each tool needs, and four backend tools run in a fixed sequence with a beforeReasoning hook that fetches grounding before the model loop starts, cutting latency by removing a model decision from the critical path.

Deterministic boundaries protect the three failure points. The model can signal intent through a state variable, but the graph evaluates guards before changing nodes. The model never touches record IDs; it writes stable developer names and a server-side transpose layer maps them back to real records and IDs. Template metadata is wrapped in sentinel tags, the client extracts and parses only that payload, and parse failures return errors rather than guesses.

Grounding is handled by a discovery service that normalizes SObject fields, flows, Apex-backed providers, and search retrievers into one consistent shape, runs in the current user’s context with field-level readability filtering, and reduces the result to an allowlist the model must select from. Safety is enforced by making output a draft only: the agent has no tool to save, publish, or execute, content becomes typed editor blocks with escaped interpolation, and the admin accepts or rejects a diff before anything is saved.

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

Worth reading?