afv-library/skills/developing-agentforce/assets/prompt-rag-search.agent
Willie Ruemmele 261abd679a
chore: rename topic to subagent for Agent Script v2 @W-21955450@ (#193)
* @W-21955450@ Rename topic to subagent for Agent Script v2

Aligns with Agent Script v2 naming standards where `topic` is renamed
to `subagent` across all skill documentation and templates.

Changes:
- Agent Script templates: topic keyword → subagent keyword
- References: @topic.* → @subagent.*
- Documentation: Updated all skill references and guides
- Natural language references preserved in comments/descriptions

* Rename start_agent topic_selector to agent_router

Completes the topic → subagent terminology alignment by:

1. Renaming start_agent from topic_selector to agent_router (15 agent files)
2. Updating template topic declarations: topic {{placeholder}} → subagent {{placeholder}} (5 files)
3. Updating all @subagent.topic_selector references to @subagent.agent_router (35 occurrences)
4. Updating documentation: prose, examples, and diagrams (10 markdown files)
5. Updating comments to use agent_router terminology

Files affected:
- 22 agent template files
- 10 documentation/reference markdown files
- Template component files

The agent_router name is more descriptive of its actual function
(routing to different subagents) and completes the Agent Script v2
terminology standardization.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* Rename files with "topic" to use "subagent" terminology

Completes the topic → subagent terminology alignment by renaming
files and updating all references:

**Files renamed (5):**
- multi-topic.agent → multi-subagent.agent
- template-single-topic.agent → template-single-subagent.agent
- template-multi-topic.agent → template-multi-subagent.agent
- topic-with-actions.agent → subagent-with-actions.agent
- agent-topic-map-diagrams.md → agent-subagent-map-diagrams.md

**References updated (6 docs):**
- Updated all filename references to point to new filenames
- Updated "Topic Map" → "Subagent Map" throughout documentation
- Updated "multi-topic"/"single-topic" → "multi-subagent"/"single-subagent"

Files modified:
- README.md, SKILL.md, agent-spec-template.md
- assets/agents/README.md, assets/README-legacy.md
- references/agent-design-and-spec-creation.md

This ensures consistent "subagent" terminology across filenames,
file content, and all documentation references.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* Complete topic-to-subagent terminology update across skills

Comprehensive update replacing "topic" with "subagent" terminology throughout
the developing-agentforce and testing-agentforce skills to align with Agent
Script's `subagent` block naming.

Key changes:
- "Topic Selector" → "Subagent Router" in all agent templates and docs
- "Topic/action" → "Subagent/action" in documentation
- "Topic map" → "Subagent map" in diagram references
- Updated all architecture documentation to use "subagent" terminology
- Updated 19 .agent template files with new labels and comments
- Updated 8 reference documentation files with consistent terminology

API contract preservation:
- Test spec YAML files preserve "topic" terminology to match Testing Center API
- Added clarifying comments explaining topic/subagent equivalence in YAML files
- Field names like `expectedTopic` unchanged (Salesforce API requirement)

Preserved terms:
- "off-topic" (standard phrase for out-of-scope)
- "expectedTopic" field (Testing Center API)
- "platform topics" (Salesforce guardrail features)

32 files changed, 379 insertions(+), 366 deletions(-)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* Complete comprehensive topic-to-subagent terminology update

Thorough update replacing all remaining "topic" references with "subagent"
terminology across developing-agentforce, testing-agentforce, and
observing-agentforce skills to fully align with Agent Script's `subagent`
block naming.

Key changes:
- Agent Script syntax: @topic.<name> → @subagent.<name>
- Agent Script syntax: topic.actions → subagent.actions
- Shell script patterns: ^topic → ^subagent
- Documentation: "topic instructions" → "subagent instructions"
- observing-agentforce skill: Updated all agent architecture references
- Template files: Updated all inline comments and descriptions
- Variable names in scripts: TOPIC → SUBAGENT

Specific updates:
- 45 files changed, 294 insertions, 294 deletions
- Updated all Agent Script code examples to use @subagent syntax
- Updated observing-agentforce issue classification guide
- Updated shell script patterns in diagnostic tools
- Updated Apex comments to clarify topic field maps to subagents

Preserved (as required):
- "off-topic" and "off_topic" (standard out-of-scope phrase)
- Testing Center API fields: expectedTopic, topic: in YAML
- API response fields: .topic, generatedData.topic, topic_assertion
- STDM field names: ssot__TopicApiName__c (with clarifying docs)
- Template placeholders in test specs (API values)
- "Topic hash drift" (API field behavior)
- "Email topic/purpose" (means email subject)
- Explanatory comments about API field mapping

All Agent Script syntax and documentation now consistently uses "subagent"
while preserving backward compatibility with platform API field names.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

* a few more topic -> subagent replacements

---------

Co-authored-by: Steve Hetzel <shetzel@salesforce.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-04-27 12:42:18 -06:00

132 lines
5.5 KiB
Plaintext

# Prompt Template with RAG Search Template
# =========================================
#
# This template demonstrates the pattern for combining Prompt Templates
# with Data Cloud RAG (Retrieval Augmented Generation) for grounded responses.
#
# Pattern: Knowledge search + grounded response generation
# Use when: FAQ bots, product knowledge agents, documentation assistants
#
# CREDIT CONSUMPTION:
# - Prompt Templates: 2-16 credits per invocation
# - Retriever actions: 20 credits per search
# - TIP: Cache retriever results in variables, reuse across subagents
system:
messages:
welcome: "Hello! I can help answer questions about our products and services."
error: "I apologize, I couldn't find the information you need."
instructions: "You are a helpful knowledge assistant. Always provide grounded answers based on retrieved knowledge."
config:
agent_name: "RAGSearchAgent"
agent_label: "Knowledge Assistant"
description: "Agent demonstrating Prompt Template with Data Cloud RAG pattern"
default_agent_user: "agent@yourorg.com" # REQUIRED: Change to valid Einstein Agent User
variables:
# Search state
search_query: mutable string = ""
description: "User's current search query"
search_results: mutable string = ""
description: "Retrieved knowledge chunks (cached for reuse)"
has_results: mutable boolean = False
description: "Whether search returned results"
# Response tracking
response_generated: mutable boolean = False
description: "Whether a response has been generated for current query"
start_agent entry:
description: "Entry point - welcome and route to knowledge search"
reasoning:
instructions: |
Welcome the user and offer to help with questions.
actions:
go_search: @utils.transition to @subagent.knowledge_search
description: "Start knowledge search"
# ============================================================
# KNOWLEDGE SEARCH SUBAGENT (RAG Pattern)
# ============================================================
subagent knowledge_search:
description: "Search knowledge base and generate grounded responses"
reasoning:
instructions: ->
# POST-ACTION: Generate response after retrieval
if @variables.has_results == True and @variables.response_generated == False:
# Use Prompt Template to generate grounded response
run @actions.Generate_Grounded_Response
with query = @variables.search_query
with context = @variables.search_results
set @variables.response_generated = True
# NO RESULTS: Escalate or try different search
if @variables.has_results == False and @variables.search_query != "":
| I couldn't find information about that subject.
| Would you like to try a different search, or speak with a human agent?
# INITIAL STATE: Ask for question
if @variables.search_query == "":
| What would you like to know? I can help with:
| - Product information
| - Pricing and plans
| - Technical specifications
| - Troubleshooting guides
actions:
# Retriever action for RAG search
# This searches Data Cloud knowledge base
search_knowledge: @actions.Search_Knowledge_Base
description: "Search for relevant information"
with query = ... # LLM extracts user's question
include_in_progress_indicator: True
progress_indicator_message: "Searching our knowledge base..."
set @variables.search_query = @outputs.original_query
set @variables.search_results = @outputs.retrieved_chunks
set @variables.has_results = @outputs.has_results
set @variables.response_generated = False # Reset for new search
# Prompt Template for grounded response
# Configure in Agentforce Assets with:
# - Template instructions referencing retrieved context
# - Set output is_displayable: True (response shown to user)
generate_answer: @actions.Generate_Grounded_Response
description: "Generate answer from retrieved knowledge"
available when @variables.has_results == True
with query = @variables.search_query
with context = @variables.search_results
# New search
new_search: @utils.setVariables
description: "Search for something else"
with search_query = ""
with search_results = ""
with has_results = False
with response_generated = False
escalate_now: @utils.escalate
description: "Transfer to human agent"
# ============================================================
# FOLLOW-UP QUESTIONS SUBAGENT
# ============================================================
subagent follow_up:
description: "Handle follow-up questions using cached context"
reasoning:
instructions: ->
# COST OPTIMIZATION: Reuse cached search_results instead of re-searching
if @variables.search_results != "":
| Based on what we discussed:
run @actions.Generate_Grounded_Response
with query = ... # Follow-up question extracted by LLM
with context = @variables.search_results # Reuse cached results!
else:
transition to @subagent.knowledge_search
actions:
back_to_search: @utils.transition to @subagent.knowledge_search
description: "Start a new search"