forcedotcom/sf-skills / plugins/builder/agentforce-adlc/skills/agentforce-generate
agentforce-generate
FlaggedBuild, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, reviews, or changes .agent files or aiAuthoringBundle metadata; asks to fix AgentScript, audit an existing agent, run an AgentScript health check, common-pitfall review, or baseline-versus-candidate repair loop; changes a response, action, subagent, route, state flow, or Agent Spec; migrates or upgrades a legacy GenAiPlannerBundle Agentforce agent (NOT an Einstein Bot) to an aiAuthoringBundle (Agent Script) agent; previews, debugs, deploys, publishes, or tests agents; uses sf agent generate/preview/publish/test; or manages Agentforce MCP servers, tools, assets, or authentication. DO NOT TRIGGER when: Apex, Flow, Prompt Template, Experience Cloud, or general Salesforce CLI work is unrelated to Agent Script; the source is an Einstein Bot (BotDefinition/BotVersion) — use agentforce-bot-upgrade; or the primary input is a production session or trace ID rather than an agent artifact.
references/examples.md
View on GitHub# Complete Agent Examples
> Long-form walkthrough examples.
> For copy/paste-ready starter templates, use `assets/agents/` first.
## How to Use This File
- Use `assets/agents/hello-world.agent` or `assets/agents/template-*.agent` to start quickly.
- Use this file when you want richer, end-to-end examples with commentary.
- Keep this file and `assets/agents/` aligned.
## Minimal Service Agent
This is the absolute minimum for a deployable service agent:
```agentscript
system:
instructions: "You are a helpful customer service agent."
messages:
welcome: "Hello! How can I help you today?"
error: "Something went wrong. Please try again."
access:
default_agent_user: "agent@00dxx000001234.ext"
config:
developer_name: "MinimalAgent"
agent_label: "Minimal Agent"
description: "A minimal service agent"
variables:
EndUserId: linked string
source: @MessagingSession.MessagingEndUserId
description: "Messaging End User ID"
RoutableId: linked string
source: @MessagingSession.Id
description: "Messaging Session ID"
ContactId: linked string
source: @MessagingEndUser.ContactId
description: "Contact ID"
language:
default_locale: "en_US"
additional_locales: ""
all_additional_locales: False
start_agent agent_router:
description: "Begin the onboarding flow"
subagent greeting:
label: "Greeting"
description: "Greet users and provide help"
reasoning:
instructions: ->
| Welcome the user warmly.
Ask how you can help them today.
```
Companion `bundle-meta.xml` (MUST be this exact content -- no extra fields):
```xml
<?xml version="1.0" encoding="UTF-8"?>
<AiAuthoringBundle xmlns="http://soap.sforce.com/2006/04/metadata">
<bundleType>AGENT</bundleType>
</AiAuthoringBundle>
```
---
## Minimal Employee Agent
Employee agents differ from service agents in their config, variables, and connection blocks. This example shows a 2-subagent IT Knowledge agent deployed to internal employees.
```agentscript
system:
instructions: |
You are an AI-powered IT assistant for Acme Corp employees.
Help employees find answers to common IT questions and
look up knowledge articles.
You are an AI assistant, not a human.
messages:
welcome: "Hi! I'm the IT Help assistant. What can I help you with?"
error: "Something went wrong. Please try again."
config:
developer_name: "IT_Knowledge_Agent"
agent_label: "IT Knowledge Agent"
description: "Internal IT knowledge base assistant for employees"
agent_type: "AgentforceEmployeeAgent"
# NOTE: No default_agent_user — employee agents run as the logged-in user.
# No connection messaging: block — employee agents have no messaging channel.
# No MessagingSession linked variables — those are service-agent-only.
variables:
search_query: mutable string = ""
description: "Current search query"
article_id: mutable string = ""
description: "Selected knowledge article ID"
language:
default_locale: "en_US"
additional_locales: ""
all_additional_locales: False
start_agent agent_router:
description: "Route employees to the right IT support subagent"
reasoning:
instructions: |
You are a router only. Do NOT answer questions directly.
Always use a transition action to route immediately.
- IT questions, troubleshooting, how-to -> use to_knowledge
- Password reset, account access -> use to_account
actions:
to_knowledge: @utils.transition to @subagent.knowledge_search
description: "Search IT knowledge base"
to_account: @utils.transition to @subagent.account_support
description: "Account and password help"
subagent knowledge_search:
label: "Knowledge Search"
description: "Search and retrieve IT knowledge articles"
actions:
search_articles:
description: "Search knowledge base for articles"
target: "apex://ITKnowledgeSearchArticles"
inputs:
query: string
description: "Search query"
outputs:
articles: string
description: "Matching articles as JSON"
is_displayable: True
reasoning:
instructions: ->
if @variables.article_id != "":
| Found article {!@variables.article_id}. Here are the details.
| Search the knowledge base using the search_articles action.
Present results clearly. Do not fabricate article content.
actions:
search: @actions.search_articles
description: "Search knowledge base"
with query = ...
set @variables.search_query = @outputs.articles
back: @utils.transition to @subagent.agent_router
description: "Route to a different subagent"
subagent account_support:
label: "Account Support"
description: "Help with password resets and account access"
actions:
reset_password:
description: "Initiate password reset for employee"
target: "flow://IT_Password_Reset"
inputs:
employee_email: string
description: "Employee email address"
outputs:
status: string
description: "Reset status"
is_displayable: True
reasoning:
instructions: ->
| Explain that you can help with password resets and account access.
Ask for the employee's email, then use the reset_password action.
actions:
reset: @actions.reset_password
description: "Reset employee password"
with employee_email = ...
# NOTE: No @utils.escalate — employee agents cannot escalate to
# human agents via messaging. Use a transition or case-creation
# action instead.
back: @utils.transition to @subagent.agent_router
description: "Route to a different subagent"
```
**What's deliberately absent (vs. service agents):**
- No `access.default_agent_user` (agent runs as the logged-in employee)
- No `connection messaging:` block (no messaging channel)
- No `EndUserId`/`RoutableId`/`ContactId` linked variables (no `@MessagingSession`)
- No `@utils.escalate` action (requires `connection messaging:`)
---
## Multi-Subagent Agent with Actions
```agentscript
system:
instructions: |
You are a customer service agent for TechCorp.
Be professional, concise, and solution-oriented.
Always verify the customer before sensitive operations.
messages:
welcome: "Welcome to TechCorp Support! How can I assist you?"
error: "I apologize for the issue. Please try again."
access:
default_agent_user: "einstein@00dxx000001234.ext"
config:
developer_name: "TechCorpAgent"
agent_label: "TechCorp Support Agent"
description: "Handles order inquiries, returns, and general support"
variables:
EndUserId: linked string
source: @MessagingSession.MessagingEndUserId
description: "Messaging End User ID"
RoutableId: linked string
source: @MessagingSession.Id
description: "Messaging Session ID"
ContactId: linked string
source: @MessagingEndUser.ContactId
description: "Contact ID"
order_id: mutable string = ""
description: "Current order being discussed"
order_status: mutable string = ""
description: "Status of the current order"
is_verified: mutable boolean = False
description: "Customer verification status"
case_id: mutable string = ""
description: "Created case ID"
language:
default_locale: "en_US"
additional_locales: ""
all_additional_locales: False
start_agent agent_router:
description: "Route customers to the right support subagent"
reasoning:
instructions: |
You are a router only. Do NOT answer questions or provide help directly.
Always use a transition action to route to the correct subagent immediately.
- Order status or tracking -> use to_orders
- Returns or refunds -> use to_returns
- General questions -> use to_general
Never attempt to help the customer yourself. Always route.
actions:
to_orders: @utils.transition to @subagent.order_support
description: "Check order status or tracking"
to_returns: @utils.transition to @subagent.return_support
description: "Process a return or refund"
to_general: @utils.transition to @subagent.general_support
description: "General questions and support"
subagent order_support:
label: "Order Support"
description: "Handle order status and tracking inquiries"
actions:
get_order:
description: "Look up order by ID"
target: "flow://Get_Order_Status"
inputs:
order_id: string
description: "Order ID"
outputs:
status: string
description: "Order status"
is_displayable: True
tracking_url: string
description: "Tracking URL"
is_displayable: True
reasoning:
instructions: ->
if @variables.order_status != "":
| Report order {!@variables.order_id} with exact status
{!@variables.order_status}. Do not guess or paraphrase it.
else:
| Ask for the order number, then use the get_order action to
retrieve the details.
actions:
lookup: @actions.get_order
description: "Look up order"
with order_id = ...
set @variables.order_id = @outputs.order_id
set @variables.order_status = @outputs.status
back: @utils.transition to @subagent.agent_router
description: "Route to a different subagent"
subagent return_support:
label: "Return Support"
description: "Handle returns and refund requests"
actions:
initiate_return:
description: "Start a return process"
target: "flow://Initiate_Return"
inputs:
order_id: string
description: "Order ID for the return"
reason: string
description: "Reason for return"
outputs:
return_id: string
description: "Return authorization ID"
is_displayable: True
reasoning:
instructions: ->
| Explain that you can help with the return. Ask for the order
number and reason.
Use the initiate_return action to start the process -- do not fabricate return IDs.
actions:
start_return: @actions.initiate_return
description: "Start a return"
with order_id = ...
with reason = ...
set @variables.case_id = @outputs.return_id
back: @utils.transition to @subagent.agent_router
description: "Route to a different subagent"
after_reasoning:
if @variables.case_id != "":
transition to @subagent.confirmation
subagent general_support:
label: "General Support"
description: "Handle general support questions"
reasoning:
instructions: |
Help the customer with general questions.
If the question is about orders or returns, route appropriately.
actions:
escalate_now: @utils.escalate
description: "Transfer to human agent"
back: @utils.transition to @subagent.agent_router
description: "Route to a different subagent"
subagent confirmation:
label: "Confirmation"
description: "Confirm the completed action"
reasoning:
instructions: ->
| Confirm that the request was processed, provide exact reference
{!@variables.case_id}, and ask whether the user needs anything else.
actions:
new_request: @utils.transition to @subagent.agent_router
description: "Start a new request"
end_chat: @actions.end_conversation
description: "End the conversation"
```
---
## Minimal Syntax Example
A compact, syntax-focused example for quick orientation:
```agentscript
system:
messages:
welcome: "Hello! How can I help you today?"
error: "Sorry, something went wrong."
instructions: "You are a helpful customer service agent."
access:
default_agent_user: "agent_user@yourorg.com"
config:
developer_name: "simple_agent"
description: "A minimal working agent example"
agent_type: "AgentforceServiceAgent"
variables:
customer_verified: mutable boolean = False
start_agent entry:
description: "Entry point for all conversations"
reasoning:
instructions: |
Greet the customer and route to the main subagent.
actions:
go_main: @utils.transition to @subagent.main
description: "Navigate to main conversation"
subagent main:
description: "Main conversation handler"
reasoning:
instructions: ->
if @variables.customer_verified == True:
| You are speaking with a verified customer.
Help them with their request.
else:
| Please verify the customer's identity first.
actions:
verify: @actions.verify_customer
description: "Verify customer identity"
set @variables.customer_verified = @outputs.verified
actions:
verify_customer: apex://VerifyCustomerAction
description: "Verify customer identity"
inputs:
customer_id: string
label: "Customer ID"
outputs:
verified: boolean
label: "Verified"
```
### Minimal Example Notes
- `config.developer_name` must match the bundle folder name (case-sensitive).
- `default_agent_user` must be a valid Einstein Agent User in target orgs.
- `instructions: ->` enables conditionals and deterministic directives.
- `instructions: |` is for literal static instruction text.
- `set @variables.X = @outputs.Y` persists action outputs in state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |