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, PromptTemplate integration, Models API usage from Apex, and custom Lightning types.

For new code-first agent development, prefer sf-ai-agentscript.

When This Skill Owns the Task

Use sf-ai-agentforce when the user is:

• maintaining existing Builder-based agents
• working in Setup → Agentforce → Agents
• creating or fixing GenAiFunction, GenAiPlugin, or PromptTemplate metadata
• wiring Builder topics to Flow / Apex / Prompt Template actions
• using Models API or LightningTypeBundle in the context of Builder-based agents

Do not use it for:

• .agent files or deterministic FSM design → sf-ai-agentscript
• agent test suites and coverage loops → sf-ai-agentforce-testing
• persona / voice design → sf-ai-agentforce-persona

Required Context to Gather First

Ask for or infer:

• whether this is a Builder / Setup UI project or a code-first Agent Script project
• agent type: Service Agent or Employee Agent
• whether the work targets topics, actions, PromptTemplates, Models API, or custom Lightning types
• what supporting Flow / Apex / metadata dependencies already exist
• whether the user needs authoring help, publish help, or troubleshooting

Two Agentforce Paths

If the user is starting from scratch and wants strong control over flow/state, route to Agent Script.

Recommended Workflow

Builder Workflow Summary

1. Confirm this is a Builder / Setup UI project
2. Pick Service Agent vs Employee Agent
3. Define topics with strong descriptions, scope, and instructions
4. Prepare supporting actions (Flow, Apex, PromptTemplate)
5. Configure inputs / outputs carefully
6. Validate dependencies
7. Publish, then activate

Expanded workflow: references/builder-workflow.md

Key Platform Rules

Topic quality matters

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

Supporting metadata deploys first

Before publishing the agent itself, deploy the supporting stack:

1. metadata / fields if needed
2. Apex if needed
3. Flows if needed
4. PromptTemplate / GenAiFunction / GenAiPlugin
5. then publish the agent

Publish does not activate

After publish, run sf agent activate separately.

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.

PromptTemplate

Use for generated content, not deterministic business rules.

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.

Expanded reference: references/metadata-reference.md

Cross-Skill Integration

Recommended Orchestration Order

sf-metadata → sf-apex → sf-flow → sf-ai-agentforce → sf-deploy

Required delegations

High-Signal Failure Patterns

Reference Map

Start here

• references/builder-workflow.md
• references/metadata-reference.md
• references/cli-commands.md

Deep technical docs

• references/prompt-templates.md
• references/models-api.md
• references/custom-lightning-types.md

Rubric

• references/scoring-rubric.md

Cross-skill reads

• sf-ai-agentscript
• sf-ai-agentforce-testing
• sf-flow
• sf-apex
• sf-deploy

Score Guide

Full rubric: references/scoring-rubric.md