@salesforce/afv-skills 1.1.0 → 1.3.0

package/skills/agentforce-development/assets/metadata/basic-prompt-template.promptTemplate-meta.xml

@@ -0,0 +1,109 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    Prompt Template: Basic Template
+
+    Use Case: Create reusable prompts for Einstein/Agentforce
+    - Standardize prompt patterns across org
+    - Include variable bindings from records
+    - Use in agents, flows, or Apex
+
+    Template Types:
+    - salesGeneration: Generate content (emails, summaries)
+    - fieldCompletion: Suggest field values
+    - recordSummary: Summarize records
+    - flexPrompt: General purpose
+
+    Setup Steps:
+    1. Replace all {{placeholder}} values
+    2. Define input variables and their sources
+    3. Deploy to org
+    4. Use in Agent Actions or Flows
+
+    File Location: force-app/main/default/promptTemplates/{{TemplateName}}.promptTemplate-meta.xml
+-->
+<PromptTemplate xmlns="http://soap.sforce.com/2006/04/metadata">
+    <!-- API Name -->
+    <fullName>{{TemplateName}}</fullName>
+
+    <!-- Display name -->
+    <masterLabel>{{TemplateLabel}}</masterLabel>
+
+    <!-- Description of template purpose -->
+    <description>{{TemplateDescription}}</description>
+
+    <!--
+    Template Type:
+    - salesGeneration: Generate sales content
+    - fieldCompletion: Predict/suggest field values
+    - recordSummary: Summarize record data
+    - flexPrompt: General purpose (most flexible)
+    -->
+    <type>flexPrompt</type>
+
+    <!-- Active status -->
+    <isActive>true</isActive>
+
+    <!--
+    The Prompt Content:
+    Use {!variableName} for variable substitution.
+    Keep prompts clear, specific, and well-structured.
+    -->
+    <promptContent>
+You are an AI assistant helping with {{UseCaseDescription}}.
+
+Context:
+{!contextVariable}
+
+Task:
+{{TaskDescription}}
+
+Instructions:
+1. {{Instruction1}}
+2. {{Instruction2}}
+3. {{Instruction3}}
+
+Please provide a helpful response based on the context above.
+    </promptContent>
+
+    <!--
+    Input Variables:
+    Define variables that can be bound to record fields or runtime values.
+    -->
+    <promptTemplateVariables>
+        <developerName>contextVariable</developerName>
+        <promptTemplateVariableType>freeText</promptTemplateVariableType>
+        <isRequired>true</isRequired>
+    </promptTemplateVariables>
+
+    <!--
+    Variable Types:
+    - freeText: User-provided text input
+    - recordField: Bound to a specific field on a record
+    - relatedList: Data from related records
+    - resource: Static resource content
+
+    Example recordField variable:
+    <promptTemplateVariables>
+        <developerName>accountName</developerName>
+        <promptTemplateVariableType>recordField</promptTemplateVariableType>
+        <objectType>Account</objectType>
+        <fieldName>Name</fieldName>
+        <isRequired>true</isRequired>
+    </promptTemplateVariables>
+    -->
+
+    <!--
+    USAGE IN AGENT ACTIONS:
+
+    Option 1: Via GenAiFunction
+    Create GenAiFunction with invocationTargetType="prompt"
+    pointing to this template.
+
+    Option 2: Via Flow
+    Use "Prompt Template" action in Flow,
+    then wrap Flow in Agent Script action.
+
+    Option 3: Via Apex
+    Use ConnectApi.Einstein.evaluatePrompt() method.
+    -->
+</PromptTemplate>

package/skills/agentforce-development/assets/metadata/genai-function-apex.xml

@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    GenAiFunction Template: Apex Invocation (Agent Builder UI / GenAiPlannerBundle ONLY)
+
+    ⚠️ NOT NEEDED for AiAuthoringBundle (Agent Script).
+    If using Agent Script (.agent files), use `target: "apex://ClassName"` directly
+    in your topic's actions block. See SKILL.md for details.
+
+    Use Case: Register Apex @InvocableMethod as an agent action in Agent Builder UI
+    - Required ONLY for GenAiPlannerBundle / Agent Builder UI path
+    - Works with GenAiPlugin (Topic) for organization
+
+    Prerequisites:
+    1. Apex class with @InvocableMethod annotation must be deployed first
+    2. GenAiPlugin (Topic) to organize functions (optional but recommended)
+
+    Setup Steps:
+    1. Replace all {{placeholder}} values
+    2. Deploy Apex class first
+    3. Create input/schema.json and output/schema.json (see below)
+    4. Deploy this GenAiFunction bundle
+    5. Optionally deploy GenAiPlugin to group functions
+
+    Bundle Structure:
+    force-app/main/default/genAiFunctions/
+    └── {{FunctionName}}/
+        ├── {{FunctionName}}.genAiFunction-meta.xml   (this file)
+        ├── input/
+        │   └── schema.json                           (input parameters)
+        └── output/
+            └── schema.json                           (output parameters)
+
+    IMPORTANT (API v66.0):
+    - Only these XML elements are valid: description, invocationTarget,
+      invocationTargetType, isConfirmationRequired, masterLabel
+    - Do NOT use: <capability>, <genAiFunctionParameters>,
+      <genAiFunctionInputs>, <genAiFunctionOutputs>, <developerName>
+    - Input/output schemas go in schema.json files, NOT inline XML
+-->
+<GenAiFunction xmlns="http://soap.sforce.com/2006/04/metadata">
+    <description>{{FunctionDescription}}</description>
+    <invocationTarget>{{ApexClassName}}</invocationTarget>
+    <invocationTargetType>apex</invocationTargetType>
+    <isConfirmationRequired>{{true|false}}</isConfirmationRequired>
+    <masterLabel>{{FunctionLabel}}</masterLabel>
+</GenAiFunction>
+
+<!--
+    input/schema.json example:
+    {
+        "required": ["{{inputParam1}}"],
+        "properties": {
+            "{{inputParam1}}": {
+                "title": "{{Input Param 1 Label}}",
+                "description": "{{Input Param 1 Description}}",
+                "lightning:type": "lightning__textType",
+                "lightning:isPII": false,
+                "copilotAction:isUserInput": true
+            }
+        },
+        "lightning:type": "lightning__objectType"
+    }
+
+    output/schema.json example:
+    {
+        "properties": {
+            "{{outputParam1}}": {
+                "title": "{{Output Param 1 Label}}",
+                "description": "{{Output Param 1 Description}}",
+                "lightning:type": "lightning__textType",
+                "lightning:isPII": false,
+                "copilotAction:isDisplayable": true,
+                "copilotAction:isUsedByPlanner": true
+            }
+        },
+        "lightning:type": "lightning__objectType"
+    }
+
+    Lightning types:
+    - lightning__textType           (String)
+    - lightning__numberType         (Number/Decimal)
+    - lightning__booleanType        (Boolean)
+    - lightning__dateType           (Date)
+    - lightning__dateTimeStringType (DateTime — TDD validated v2.1.0)
+    - lightning__currencyType       (Currency)
+
+    APEX CLASS REQUIREMENTS:
+    - Must be global or public with sharing
+    - Method must have @InvocableMethod annotation
+    - Input/output use @InvocableVariable wrapper classes
+    - Parameter names in schema.json must match @InvocableVariable field names
+-->

package/skills/agentforce-development/assets/metadata/genai-function-flow.xml

@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    GenAiFunction Template: Flow Invocation (Agent Builder UI / GenAiPlannerBundle ONLY)
+
+    ⚠️ NOT NEEDED for AiAuthoringBundle (Agent Script).
+    If using Agent Script (.agent files), use `target: "flow://FlowApiName"` directly
+    in your topic's actions block. See SKILL.md for details.
+
+    Use Case: Register Autolaunched Flow as an agent action in Agent Builder UI
+    - Required ONLY for GenAiPlannerBundle / Agent Builder UI path
+    - Supports HTTP callouts via Flow HTTP actions
+    - Works well with External Services
+
+    Prerequisites:
+    1. Autolaunched Flow must be deployed and active first
+    2. Flow must have defined input/output variables
+
+    Setup Steps:
+    1. Replace all {{placeholder}} values
+    2. Deploy Autolaunched Flow first
+    3. Create input/schema.json and output/schema.json (see genai-function-apex.xml for format)
+    4. Deploy this GenAiFunction bundle
+
+    Bundle Structure:
+    force-app/main/default/genAiFunctions/
+    └── {{FunctionName}}/
+        ├── {{FunctionName}}.genAiFunction-meta.xml   (this file)
+        ├── input/
+        │   └── schema.json                           (input parameters)
+        └── output/
+            └── schema.json                           (output parameters)
+
+    IMPORTANT (API v66.0):
+    - Only these XML elements are valid: description, invocationTarget,
+      invocationTargetType, isConfirmationRequired, masterLabel
+    - Do NOT use: <capability>, <genAiFunctionParameters>,
+      <genAiFunctionInputs>, <genAiFunctionOutputs>, <developerName>
+    - Input/output schemas go in schema.json files, NOT inline XML
+-->
+<GenAiFunction xmlns="http://soap.sforce.com/2006/04/metadata">
+    <description>{{FunctionDescription}}</description>
+    <invocationTarget>{{FlowApiName}}</invocationTarget>
+    <invocationTargetType>flow</invocationTargetType>
+    <isConfirmationRequired>{{true|false}}</isConfirmationRequired>
+    <masterLabel>{{FunctionLabel}}</masterLabel>
+</GenAiFunction>
+
+<!--
+    FLOW REQUIREMENTS:
+    1. Flow Type: Autolaunched Flow (NOT Screen Flow)
+    2. Input Variables: Must be marked "Available for input"
+    3. Output Variables: Must be marked "Available for output"
+    4. Variable names in schema.json must match Flow variable names exactly
+    5. Flow must be Active
+
+    See genai-function-apex.xml for input/schema.json and output/schema.json format examples.
+-->

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>