Agentforce Builder metadata path for Builder-managed topics/actions, Prompt Builder templates, GenAiFunction/GenAiPlugin, Models API, and custom Lightning types. TRIGGER when: user maintains or configures Builder metadata agents, creates topics/actions, works with Prompt Builder templates, or touches .genAiFunction, .genAiPlugin, or .genAiPromptTemplate metadata XML files. DO NOT TRIGGER when: Agent Script DSL .agent files (use sf-ai-agentscript), agent testing (use sf-ai-agentforce-testing), or persona design (use sf-ai-agentforce-persona).
Agentforce Builder metadata path for Builder-managed topics/actions, Prompt Builder templates, GenAiFunction/GenAiPlugin, Models API, and custom Lightning types. TRIGGER when: user maintains or configures Builder metadata agents, creates topics/actions, works with Prompt Builder templates, or touches .genAiFunction, .genAiPlugin, or .genAiPromptTemplate metadata XML files. DO NOT TRIGGER when: Agent Script DSL .agent files (use sf-ai-agentscript), agent testing (use sf-ai-agentforce-testing), or persona design (use sf-ai-agentforce-persona).
license
MIT
compatibility
Requires API v66.0+ (Spring '26)
metadata
{"version":"2.2.0","author":"Jag Valaiyapathy"}
sf-ai-agentforce: Standard Agentforce Platform Development
Use this skill for the Setup UI / Agent Builder path: declarative topics, Builder-managed actions, GenAiFunction / GenAiPlugin metadata, Prompt Builder templates stored as GenAiPromptTemplate metadata, Models API usage from Apex, and custom Lightning types.
Topic descriptions are routing instructions for the planner. They must be:
specific
scenario-based
non-overlapping with sibling topics
Actions are wrappers around real targets
Target type
Typical use
Registered via
Flow
safest default for Builder actions
GenAiFunction
Apex
complex business logic via @InvocableMethod
GenAiFunction
Prompt Builder template
generated summaries / drafts / recommendations
GenAiFunction
Prompt Template vs GenAiPromptTemplate
Prompt Template is the plain-English / UI term used in Prompt Builder.
GenAiPromptTemplate is the current Metadata API type for source-driven template work.
Prefer current source format: genAiPromptTemplates/*.genAiPromptTemplate-meta.xml.
For flexible Prompt Builder templates, plan around the 5-input maximum and consolidate inputs when needed.
Prompt content should reference inputs with the current merge-field shape, e.g. {!$Input:TargetRecord} or {!$Input:AdditionalContext}.
Supporting metadata deploys first
Before publishing the agent itself, deploy the supporting stack:
metadata / fields if needed
Apex if needed
Flows if needed
GenAiPromptTemplate / GenAiFunction / GenAiPlugin
then publish the agent
Service Agent running user
For Service Agents, prefer the native GA command:
sf org create agent-user --target-org <alias> --json
Use the returned username in the running-user configuration.
Employee Agent visibility
For Employee Agents, ensure end users receive a Permission Set containing <agentAccesses>. Without this, the agent can be active but still invisible in Lightning Experience.
See ../sf-permissions/references/agent-access-guide.md.
Publish does not activate
After publish, run sf agent activate separately.
For automation, prefer sf agent activate --api-name <AgentName> --version <n> --target-org <alias> --json so the rollout is deterministic and machine-readable.
Metadata Guidance
GenAiFunction
Use when registering a single callable action. Validate:
target exists
target is active / deployable
input names match the target contract
output names match the target contract
capability text clearly says when the action should be used
GenAiPlugin
Use when grouping related functions into one logical package.
GenAiPromptTemplate
Use for generated content, not deterministic business rules.
Prefer the current metadata shape:
metadata type: GenAiPromptTemplate
folder: genAiPromptTemplates/
file suffix: .genAiPromptTemplate-meta.xml
content lives under templateVersions
use published template versions before wiring actions that depend on them
Models API
Use when the solution belongs in Apex-driven AI orchestration rather than Builder-only actions.
Custom Lightning Types
Use when the action needs richer structured input or output presentation.
