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/action-prompt-templates.md
View on GitHub# Prompt Template Actions
Invoking Salesforce Prompt Templates as actions within Agent Script.
> Specialized reference for `generatePromptResponse://` actions.
> For general action metadata and property rules, see `actions-reference.md`.
---
## Overview
Prompt Template Actions let agents invoke Salesforce Prompt Templates via the `generatePromptResponse://` protocol. The agent passes structured inputs to the template and receives a generated `promptResponse` output — keeping content generation in the template while the agent manages conversation flow.
**When to use**: Personalized responses, summarization, content generation, recommendations — anything where an LLM prompt template produces better output than static Flow logic.
---
## Action Definition (Agentforce Assets)
Define the action in **Setup > Agentforce > Action Definitions** (or via metadata API):
```agentscript
actions:
Generate_Personalized_Schedule:
description: "Generate a personalized schedule using a prompt template"
inputs:
"Input:email": string
description: "User's email address"
is_required: True
"Input:preferences": string
description: "User's scheduling preferences"
is_required: False
outputs:
promptResponse: string
description: "The personalized schedule generated by the template"
is_used_by_planner: True
target: "generatePromptResponse://Generate_Personalized_Schedule"
```
### Critical syntax rules
| Rule | Example |
|------|---------|
| Target protocol | `"generatePromptResponse://TemplateName"` |
| Input names **must be quoted** | `"Input:email"` not `Input:email` |
| Input prefix is `Input:` | Matches the template's input field API name |
| Output field is always `promptResponse` | Single string output from the template |
---
## Agent Script Invocation
Reference the action definition in your `.agent` file:
```agentscript
subagent schedule_generation:
reasoning:
actions:
generate_schedule: @actions.Generate_Personalized_Schedule
with "Input:email"=@variables.user_email
"Input:preferences"=...
set @variables.schedule = @outputs.promptResponse
```
**Input binding patterns** (same as regular actions):
- `@variables.user_email` — variable binding (data from prior turns)
- `...` — LLM slot-filling (extract from conversation)
- `"professional"` — fixed value (business rule constant)
---
## Grounded Data Integration
Templates can include **data providers** (Apex classes, Flows) that supply contextual data for personalized responses. The grounding happens inside the template — Agent Script only needs to pass the lookup key:
```agentscript
actions:
Get_Product_Recommendations:
description: "Generate personalized product recommendations based on purchase history"
inputs:
"Input:customerId": string
description: "Customer ID for personalization"
is_required: True
outputs:
promptResponse: string
description: "Personalized recommendations grounded in customer data"
target: "generatePromptResponse://Product_Recommender"
```
The template itself (configured in Prompt Builder) includes:
- **Data Provider**: Apex class fetching customer purchase history
- **Grounding**: Recent orders, preferences, browsing history
- **Template instructions**: How to format recommendations using the grounded data
---
## Common Patterns
### Pattern 1: Content Generation
```agentscript
generate_email: @actions.Generate_Email_Response
with "Input:customerMessage"=@variables.user_message
"Input:tone"="professional"
"Input:context"=@variables.case_context
set @variables.email_draft = @outputs.promptResponse
```
### Pattern 2: Summarization
```agentscript
summarize: @actions.Summarize_Conversation
with "Input:conversationHistory"=@variables.chat_history
"Input:maxLength"="500"
set @variables.summary = @outputs.promptResponse
```
### Pattern 3: Personalized Recommendations
```agentscript
recommend: @actions.Get_Product_Recommendations
with "Input:customerId"=@variables.customer_id
"Input:category"=...
set @variables.recommendations = @outputs.promptResponse
```
---
## Known Limitation: `run` Keyword with Prompt Templates
Chained actions using `run` may not properly map `"Input:X"` parameters:
```agentscript
# ❌ MAY NOT WORK — run + prompt template input binding:
process: @actions.create_order
with customer_id=@variables.customer_id
run @actions.Generate_Order_Summary
with "Input:orderId"=@variables.order_id # Input binding may fail
# ✅ WORKAROUND — call as primary action instead:
generate_summary: @actions.Generate_Order_Summary
with "Input:orderId"=@variables.order_id # Works as primary action
set @variables.summary = @outputs.promptResponse
```
---
## Common Errors
| Error | Cause | Fix |
|-------|-------|-----|
| `SyntaxError` on input binding | Missing quotes on parameter name | Use `"Input:email"` not `Input:email` |
| Template not found | Wrong protocol or template name | Verify `generatePromptResponse://ExactTemplateName` |
| Empty `promptResponse` | Template inactive or missing required inputs | Activate template in Setup, check all `is_required: True` inputs are bound |
| Input not mapped | API name mismatch | Input field name after `Input:` must exactly match template's input API name |
---
## Checklist
- [ ] Template exists in org and is **active**
- [ ] Input field API names match template configuration exactly
- [ ] All `is_required: True` inputs are bound (via `...`, `@variables`, or fixed)
- [ ] `promptResponse` output is captured with `set`
- [ ] Template response quality tested with representative inputs
- [ ] If using grounded data: data provider returns expected records
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: 472k | 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: 472k | 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: 472k | 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 |