@salesforce/afv-skills 1.1.0 → 1.2.0

package/skills/agentforce-development/assets/metadata/genai-plugin.xml

@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    GenAiPlugin Template: Agent Topic/Plugin Container
+
+    Use Case: Organize GenAiFunctions into logical groups (Topics)
+    - Groups related functions together
+    - Provides topic-level instructions
+    - Maps to Agent Script topic concepts
+
+    Note: GenAiPlugin is the metadata equivalent of a "topic" in Agent Script.
+    Use this when you want to organize functions deployed via metadata
+    rather than Agent Script.
+
+    Setup Steps:
+    1. Replace all {{placeholder}} values
+    2. Deploy GenAiFunctions first
+    3. Deploy this GenAiPlugin
+
+    File Location: force-app/main/default/genAiPlugins/{{PluginName}}.genAiPlugin-meta.xml
+-->
+<GenAiPlugin xmlns="http://soap.sforce.com/2006/04/metadata">
+    <!-- Display name for the topic/plugin -->
+    <masterLabel>{{PluginLabel}}</masterLabel>
+
+    <!-- Description shown in Agent Builder -->
+    <description>{{PluginDescription}}</description>
+
+    <!-- Developer name (API name) -->
+    <developerName>{{PluginDeveloperName}}</developerName>
+
+    <!--
+    Plugin Instructions:
+    Natural language instructions for how the agent should use
+    functions in this plugin. Similar to topic instructions in Agent Script.
+    -->
+    <pluginInstructions>
+        {{Instructions for the agent on how to use functions in this topic.
+        Include guidance on when to use specific functions,
+        how to handle edge cases, and any constraints.}}
+    </pluginInstructions>
+
+    <!--
+    Plugin Type:
+    - Standard: Regular function grouping
+    - Copilot: For Salesforce Copilot-specific plugins
+    -->
+    <pluginType>Standard</pluginType>
+
+    <!--
+    Associated Functions:
+    List the GenAiFunction developer names that belong to this plugin.
+    -->
+    <genAiFunctions>
+        <function>{{GenAiFunction1DeveloperName}}</function>
+    </genAiFunctions>
+    <genAiFunctions>
+        <function>{{GenAiFunction2DeveloperName}}</function>
+    </genAiFunctions>
+
+    <!--
+    AGENT BUILDER INTEGRATION:
+
+    After deploying GenAiPlugin:
+    1. Open Agent Builder in Setup
+    2. Navigate to Topics
+    3. Your plugin appears as a Topic
+    4. Associated functions are available as Actions
+
+    This provides an alternative to Agent Script for more
+    complex deployments or when you need metadata-level control.
+    -->
+</GenAiPlugin>

package/skills/agentforce-development/assets/metadata/http-callout-flow.flow-meta.xml

@@ -0,0 +1,348 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    HTTP Callout Flow Template for Agent Actions
+
+    Use Case: Create Flow-based API actions for agents
+    - Enables external API calls from Agent Script
+    - Uses Named Credential for secure auth
+    - Works with flow:// target in Agent Script
+
+    Pattern:
+    Agent Script → flow://{{FlowName}} → HTTP Callout → External API
+
+    Prerequisites:
+    1. Named Credential configured for API auth
+    2. sf-integration skill used to create Named Credential
+
+    Setup Steps:
+    1. Replace all {{placeholder}} values
+    2. Deploy Named Credential first
+    3. Deploy this Flow
+    4. Reference in Agent Script: target: "flow://{{FlowApiName}}"
+
+    File Location: force-app/main/default/flows/{{FlowApiName}}.flow-meta.xml
+-->
+<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
+    <!-- API Name -->
+    <fullName>{{FlowApiName}}</fullName>
+
+    <!-- Display label -->
+    <label>{{FlowLabel}}</label>
+
+    <!-- Description -->
+    <description>HTTP callout to {{ExternalSystemName}} for agent actions</description>
+
+    <!-- Autolaunched Flow (required for agent actions) -->
+    <processType>AutoLaunchedFlow</processType>
+
+    <!-- API Version -->
+    <apiVersion>66.0</apiVersion>
+
+    <!-- Active status -->
+    <status>Active</status>
+
+    <!--
+    =========================================
+    INPUT VARIABLES
+    Must be marked "Available for Input"
+    =========================================
+    -->
+    <variables>
+        <name>input_param_1</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>true</isInput>
+        <isOutput>false</isOutput>
+        <value>
+            <stringValue></stringValue>
+        </value>
+    </variables>
+
+    <!-- Add more input variables as needed -->
+    <!--
+    <variables>
+        <name>input_param_2</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>true</isInput>
+        <isOutput>false</isOutput>
+    </variables>
+    -->
+
+    <!--
+    =========================================
+    OUTPUT VARIABLES
+    Must be marked "Available for Output"
+    =========================================
+    -->
+    <variables>
+        <name>output_result</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>false</isInput>
+        <isOutput>true</isOutput>
+    </variables>
+
+    <variables>
+        <name>output_status</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>false</isInput>
+        <isOutput>true</isOutput>
+    </variables>
+
+    <variables>
+        <name>output_error</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>false</isInput>
+        <isOutput>true</isOutput>
+    </variables>
+
+    <!--
+    =========================================
+    HTTP CALLOUT ACTION
+    Core Action for making HTTP requests
+    =========================================
+    -->
+    <actionCalls>
+        <name>HTTP_Callout</name>
+        <label>Call External API</label>
+        <locationX>176</locationX>
+        <locationY>158</locationY>
+
+        <!-- HTTP Callout Core Action -->
+        <actionType>httpCallout</actionType>
+
+        <!--
+        Named Credential for authentication
+        Format: callout:NamedCredentialName
+        -->
+        <actionName>callout:{{NamedCredentialName}}</actionName>
+
+        <!-- Continue on error to handle gracefully -->
+        <connector>
+            <targetReference>Check_Response</targetReference>
+        </connector>
+
+        <faultConnector>
+            <targetReference>Handle_Error</targetReference>
+        </faultConnector>
+
+        <!-- HTTP Method: GET, POST, PUT, PATCH, DELETE -->
+        <inputParameters>
+            <name>method</name>
+            <value>
+                <stringValue>{{GET|POST|PUT|PATCH|DELETE}}</stringValue>
+            </value>
+        </inputParameters>
+
+        <!-- API Endpoint path (appended to Named Credential base URL) -->
+        <inputParameters>
+            <name>url</name>
+            <value>
+                <elementReference>API_Endpoint</elementReference>
+            </value>
+        </inputParameters>
+
+        <!-- Request body (for POST/PUT/PATCH) -->
+        <inputParameters>
+            <name>body</name>
+            <value>
+                <elementReference>Request_Body</elementReference>
+            </value>
+        </inputParameters>
+
+        <!-- Response body -->
+        <outputParameters>
+            <assignToReference>Response_Body</assignToReference>
+            <name>responseBody</name>
+        </outputParameters>
+
+        <!-- Response status code -->
+        <outputParameters>
+            <assignToReference>Response_Status_Code</assignToReference>
+            <name>statusCode</name>
+        </outputParameters>
+    </actionCalls>
+
+    <!--
+    =========================================
+    FORMULAS
+    Build request URL and body
+    =========================================
+    -->
+    <formulas>
+        <name>API_Endpoint</name>
+        <dataType>String</dataType>
+        <!-- Build endpoint with input parameters -->
+        <expression>"/{{apiPath}}/" &amp; {!input_param_1}</expression>
+    </formulas>
+
+    <formulas>
+        <name>Request_Body</name>
+        <dataType>String</dataType>
+        <!-- Build JSON request body -->
+        <expression>'{"param1": "' &amp; {!input_param_1} &amp; '"}'</expression>
+    </formulas>
+
+    <!--
+    =========================================
+    PRIVATE VARIABLES
+    For internal flow processing
+    =========================================
+    -->
+    <variables>
+        <name>Response_Body</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>false</isInput>
+        <isOutput>false</isOutput>
+    </variables>
+
+    <variables>
+        <name>Response_Status_Code</name>
+        <dataType>Number</dataType>
+        <isCollection>false</isCollection>
+        <isInput>false</isInput>
+        <isOutput>false</isOutput>
+        <scale>0</scale>
+    </variables>
+
+    <!--
+    =========================================
+    DECISION: Check Response Status
+    =========================================
+    -->
+    <decisions>
+        <name>Check_Response</name>
+        <label>Check Response Status</label>
+        <locationX>176</locationX>
+        <locationY>278</locationY>
+
+        <defaultConnector>
+            <targetReference>Set_Error_Output</targetReference>
+        </defaultConnector>
+        <defaultConnectorLabel>Error</defaultConnectorLabel>
+
+        <rules>
+            <name>Success</name>
+            <conditionLogic>and</conditionLogic>
+            <conditions>
+                <leftValueReference>Response_Status_Code</leftValueReference>
+                <operator>GreaterThanOrEqualTo</operator>
+                <rightValue>
+                    <numberValue>200</numberValue>
+                </rightValue>
+            </conditions>
+            <conditions>
+                <leftValueReference>Response_Status_Code</leftValueReference>
+                <operator>LessThan</operator>
+                <rightValue>
+                    <numberValue>300</numberValue>
+                </rightValue>
+            </conditions>
+            <connector>
+                <targetReference>Set_Success_Output</targetReference>
+            </connector>
+            <label>Success (2xx)</label>
+        </rules>
+    </decisions>
+
+    <!--
+    =========================================
+    ASSIGNMENTS: Set Output Variables
+    =========================================
+    -->
+    <assignments>
+        <name>Set_Success_Output</name>
+        <label>Set Success Output</label>
+        <locationX>50</locationX>
+        <locationY>398</locationY>
+
+        <assignmentItems>
+            <assignToReference>output_result</assignToReference>
+            <operator>Assign</operator>
+            <value>
+                <elementReference>Response_Body</elementReference>
+            </value>
+        </assignmentItems>
+        <assignmentItems>
+            <assignToReference>output_status</assignToReference>
+            <operator>Assign</operator>
+            <value>
+                <stringValue>Success</stringValue>
+            </value>
+        </assignmentItems>
+    </assignments>
+
+    <assignments>
+        <name>Set_Error_Output</name>
+        <label>Set Error Output</label>
+        <locationX>302</locationX>
+        <locationY>398</locationY>
+
+        <assignmentItems>
+            <assignToReference>output_status</assignToReference>
+            <operator>Assign</operator>
+            <value>
+                <stringValue>Error</stringValue>
+            </value>
+        </assignmentItems>
+        <assignmentItems>
+            <assignToReference>output_error</assignToReference>
+            <operator>Assign</operator>
+            <value>
+                <elementReference>Response_Body</elementReference>
+            </value>
+        </assignmentItems>
+    </assignments>
+
+    <assignments>
+        <name>Handle_Error</name>
+        <label>Handle Callout Error</label>
+        <locationX>440</locationX>
+        <locationY>278</locationY>
+
+        <assignmentItems>
+            <assignToReference>output_status</assignToReference>
+            <operator>Assign</operator>
+            <value>
+                <stringValue>Error</stringValue>
+            </value>
+        </assignmentItems>
+        <assignmentItems>
+            <assignToReference>output_error</assignToReference>
+            <operator>Assign</operator>
+            <value>
+                <stringValue>HTTP callout failed</stringValue>
+            </value>
+        </assignmentItems>
+    </assignments>
+
+    <!-- Flow start -->
+    <start>
+        <locationX>50</locationX>
+        <locationY>0</locationY>
+        <connector>
+            <targetReference>HTTP_Callout</targetReference>
+        </connector>
+    </start>
+
+    <!--
+    AGENT SCRIPT USAGE:
+
+    actions:
+        call_api:
+            description: "Calls external API"
+            inputs:
+                param1: string
+                    description: "Input parameter"
+            outputs:
+                result: string
+                    description: "API response"
+                status: string
+                    description: "Success or Error"
+            target: "flow://{{FlowApiName}}"
+    -->
+</Flow>

package/skills/agentforce-development/assets/metadata/record-grounded-prompt.promptTemplate-meta.xml

@@ -0,0 +1,136 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    Prompt Template: Record-Grounded Template
+
+    Use Case: Prompts that use Salesforce record data for context
+    - Ground responses in actual CRM data
+    - Summarize records intelligently
+    - Generate record-specific content
+
+    Key Feature: Variables bound to record fields provide real data
+    to the prompt, ensuring accuracy and relevance.
+
+    Setup Steps:
+    1. Replace all {{placeholder}} values
+    2. Configure record field bindings
+    3. Deploy to org
+
+    File Location: force-app/main/default/promptTemplates/{{TemplateName}}.promptTemplate-meta.xml
+-->
+<PromptTemplate xmlns="http://soap.sforce.com/2006/04/metadata">
+    <fullName>{{TemplateName}}</fullName>
+    <masterLabel>{{TemplateLabel}}</masterLabel>
+    <description>{{TemplateDescription}}</description>
+
+    <!-- Record summary type for record-grounded prompts -->
+    <type>recordSummary</type>
+
+    <isActive>true</isActive>
+
+    <!--
+    Primary Object:
+    The main object this template operates on.
+    -->
+    <objectType>{{ObjectApiName}}</objectType>
+
+    <!--
+    Prompt with record field references:
+    Use {!variableName} syntax for bound fields.
+    -->
+    <promptContent>
+You are summarizing a {{ObjectLabel}} record for a sales representative.
+
+Record Information:
+- Name: {!recordName}
+- Status: {!recordStatus}
+- Owner: {!ownerName}
+- Created Date: {!createdDate}
+- Last Activity: {!lastActivityDate}
+
+Additional Context:
+{!additionalNotes}
+
+Related Information:
+{!relatedRecords}
+
+Please provide a concise summary that highlights:
+1. Current status and recent activity
+2. Key metrics or important values
+3. Recommended next steps
+4. Any risks or concerns
+
+Keep the summary under 200 words and focus on actionable insights.
+    </promptContent>
+
+    <!-- Record Name Field -->
+    <promptTemplateVariables>
+        <developerName>recordName</developerName>
+        <promptTemplateVariableType>recordField</promptTemplateVariableType>
+        <objectType>{{ObjectApiName}}</objectType>
+        <fieldName>Name</fieldName>
+        <isRequired>true</isRequired>
+    </promptTemplateVariables>
+
+    <!-- Status Field -->
+    <promptTemplateVariables>
+        <developerName>recordStatus</developerName>
+        <promptTemplateVariableType>recordField</promptTemplateVariableType>
+        <objectType>{{ObjectApiName}}</objectType>
+        <fieldName>{{StatusFieldApiName}}</fieldName>
+        <isRequired>false</isRequired>
+    </promptTemplateVariables>
+
+    <!-- Owner Name -->
+    <promptTemplateVariables>
+        <developerName>ownerName</developerName>
+        <promptTemplateVariableType>recordField</promptTemplateVariableType>
+        <objectType>{{ObjectApiName}}</objectType>
+        <fieldName>Owner.Name</fieldName>
+        <isRequired>false</isRequired>
+    </promptTemplateVariables>
+
+    <!-- Created Date -->
+    <promptTemplateVariables>
+        <developerName>createdDate</developerName>
+        <promptTemplateVariableType>recordField</promptTemplateVariableType>
+        <objectType>{{ObjectApiName}}</objectType>
+        <fieldName>CreatedDate</fieldName>
+        <isRequired>false</isRequired>
+    </promptTemplateVariables>
+
+    <!-- Last Activity Date -->
+    <promptTemplateVariables>
+        <developerName>lastActivityDate</developerName>
+        <promptTemplateVariableType>recordField</promptTemplateVariableType>
+        <objectType>{{ObjectApiName}}</objectType>
+        <fieldName>LastActivityDate</fieldName>
+        <isRequired>false</isRequired>
+    </promptTemplateVariables>
+
+    <!-- Free text for additional context -->
+    <promptTemplateVariables>
+        <developerName>additionalNotes</developerName>
+        <promptTemplateVariableType>freeText</promptTemplateVariableType>
+        <isRequired>false</isRequired>
+    </promptTemplateVariables>
+
+    <!-- Related records (could be from related list) -->
+    <promptTemplateVariables>
+        <developerName>relatedRecords</developerName>
+        <promptTemplateVariableType>freeText</promptTemplateVariableType>
+        <isRequired>false</isRequired>
+    </promptTemplateVariables>
+
+    <!--
+    DATA CLOUD GROUNDING (Optional):
+
+    For Data Cloud integration, add:
+    <dataCloudConfig>
+        <dataCloudObjectName>{{DataCloudObjectName}}</dataCloudObjectName>
+        <retrievalStrategy>semantic</retrievalStrategy>
+    </dataCloudConfig>
+
+    This enables RAG (Retrieval Augmented Generation) with
+    Data Cloud data for more contextual responses.
+    -->
+</PromptTemplate>

package/skills/agentforce-development/assets/minimal-starter.agent

@@ -0,0 +1,42 @@
+# Minimal Agent Script Starter Template
+# =====================================
+#
+# This template provides the minimum required structure for an Agent Script.
+# Use this as a starting point for simple, single-purpose agents.
+#
+# Required blocks: system, config, topic, start_agent
+# File extension: .agent
+
+system:
+   messages:
+      welcome: "Hello! How can I help you today?"
+      error: "I apologize, but something went wrong. Let me try again."
+   instructions: "You are a helpful assistant."
+
+config:
+   agent_name: "MinimalAgent"
+   agent_label: "Minimal Agent"
+   description: "A minimal agent template to get started"
+   default_agent_user: "agent@yourorg.com"  # REQUIRED: Change to valid Einstein Agent User
+
+# Optional: Add variables for state tracking
+# variables:
+#    counter: mutable number = 0
+#    session_id: linked string
+#       source: @session.sessionID
+
+topic main:
+   description: "Main conversation handler"
+   reasoning:
+      instructions: |
+         Help the user with their request.
+         Be friendly and helpful.
+
+start_agent entry:
+   description: "Entry point for all conversations"
+   reasoning:
+      instructions: |
+         Greet the user and route to the main topic.
+      actions:
+         begin: @utils.transition to @topic.main
+            description: "Start the main conversation"