Skip to content
SalesforceSkills

Agent Script

Write Agent Script DSL for complex agent conversations. AI handles the tricky syntax so you can focus on the conversation design.

Skill Details

Install this skill

Versionv2.9.0AuthorJag ValaiyapathyLicenseMITSections13

Works with

Claude CodeCursorWindsurf

Agent Script is the code-first path for deterministic Agentforce agents. Use this skill when the user is authoring .agent files, building finite-state topic flows, or needs repeatable control over routing, variables, actions, and publish behavior.

Start with the shortest guide first: references/activation-checklist.md

When This Skill Owns the TaskWorkflow

Use sf-ai-agentscript when the work involves:

  • creating or editing .agent files
  • deterministic topic routing, guards, and transitions
  • Agent Script CLI workflows (sf agent generate, sf agent validate, sf agent publish)
  • slot filling, instruction resolution, post-action loops, or FSM design

Delegate elsewhere when the user is:

Required Context to Gather FirstWorkflow

Ask for or infer:

  • agent purpose and whether Agent Script is truly the right fit
  • Service Agent vs Employee Agent
  • target org and publish intent
  • expected actions / targets (Flow, Apex, PromptTemplate, etc.)
  • whether the request is authoring, validation, preview, or publish troubleshooting

Activation Checklist

Before you author or fix any .agent file, verify these first:

1
Exactly one start_agent block
2
No mixed tabs and spaces
3
Booleans are True / False
4
No else if and no nested if
5
No top-level actions: block
6
No @inputs in set expressions
7
linked variables have no defaults
8
linked variables do not use object / list types
9
Use explicit agent_type
10
Use @actions. prefixes consistently
11
Use run @actions.X only when X is a topic-level action definition with target:
12
Do not branch directly on raw @system_variables.user_input contains/startswith/endswith for intent routing
13
On prompt-template outputs, prefer is_displayable: False + is_used_by_planner: True
14
Do not assume @outputs.X is scalar — inspect the output schema before branching or assignment

For the expanded version, use references/activation-checklist.md.

Non-Negotiable Rules

1) Service Agent vs Employee Agent

Full details: references/agent-user-setup.md

2) Required block order

YAML
config:
variables:
system:
connection:
knowledge:
language:
start_agent:
topic:

3) Critical config fields

4) Syntax blockers you should treat as immediate failures

  • else if
  • nested if
  • comment-only if bodies
  • top-level actions:
  • invocation-level inputs: / outputs: blocks
  • reserved variable / field names like description and label

Canonical rule set: references/syntax-reference.md and references/validator-rule-catalog.md

Phase 1 — design the agent

  • decide whether the problem is actually deterministic enough for Agent Script
  • model topics as states and transitions as edges
  • define only the variables you truly need

Phase 2 — author the .agent

  • create config, system, start_agent, and topics first
  • add target-backed actions with full inputs: and outputs:
  • use available when for deterministic tool visibility
  • normalize raw intent/validation signals into booleans or enums before branching; avoid direct substring checks on raw user utterances for critical control flow
  • keep post-action checks at the top of instructions: ->

Phase 3 — validate continuously

Validation already runs automatically on write/edit. Use the CLI before publish:

Terminal
sf agent validate authoring-bundle --api-name MyAgent -o TARGET_ORG --json

The validator covers structure, runtime gotchas, target readiness, and org-aware Service Agent checks. Rule IDs live in references/validator-rule-catalog.md.

Phase 4 — preview smoke test

Use the preview loop before publish:

  • derive 3–5 smoke utterances
  • start preview
  • inspect topic routing / action invocation / safety / grounding
  • fix and rerun up to 3 times

Full loop: references/preview-test-loop.md

Phase 5 — publish and activate

Terminal
sf agent publish authoring-bundle --api-name MyAgent -o TARGET_ORG --json
sf agent activate --api-name MyAgent -o TARGET_ORG

Publishing does not activate the agent.

Deterministic Building Blocks

These execute as code, not suggestions:

  • conditionals
  • available when guards
  • variable checks
  • direct set / transition to
  • run @actions.X only when X is a topic-level action definition with target:
  • variable injection into LLM-facing text

Important distinction:

  • Deterministic: set, transition to, and run @actions.X for a target-backed topic action
  • LLM-directed: reasoning.actions: utilities / delegations such as @utils.setVariables, @utils.transition, and {!@actions.X} instruction references

If you need deterministic behavior for something that is currently modeled as a reasoning-level utility, either:

  • rewrite it as direct set / transition to, or
  • promote it to a topic-level target-backed action and run that action

See references/instruction-resolution.md and references/architecture-patterns.md.

Cross-Skill IntegrationReference

Cross-Skill Orchestration

High-Signal Failure Patterns

Reference Map

Start here

Publish / runtime safety

Architecture / reasoning

Validation / testing / debugging

Examples / templates

Project documentation

Score Guide

Agent typeRequiredForbidden / caution
AgentforceServiceAgentValid default_agent_user, correct permissions, target-org checksPublishing without a real Einstein Agent User
AgentforceEmployeeAgentExplicit agent_typeSupplying default_agent_user
FieldRule
developer_nameMust match folder / bundle name
agent_descriptionUse instead of legacy description
agent_typeSet explicitly every time
default_agent_userService Agents only
TaskDelegate toWhy
Build flow:// targetssf-flowFlow creation / validation
Build Apex action targetssf-apex@InvocableMethod and business logic
Test topic routing / actionssf-ai-agentforce-testingFormal test specs and fix loops
Deploy / publishsf-deployDeployment orchestration
SymptomLikely causeRead next
Internal Error during publishinvalid Service Agent user or missing action I/Oreferences/agent-user-setup.md, references/actions-reference.md
invalid input/output parameters on prompt template actionTarget template is in Draft status — activate it firstreferences/action-prompt-templates.md
Parser rejects conditionalselse if, nested if, empty if bodyreferences/syntax-reference.md
Action target issuesmissing Flow / Apex target, inactive Flow, bad schemasreferences/actions-reference.md
Prompt template runs but user sees blank responseprompt output marked is_displayable: Truereferences/production-gotchas.md, references/action-prompt-templates.md
Prompt action runs but planner behaves like output is missingoutput hidden from direct display but not planner-visiblereferences/production-gotchas.md, references/actions-reference.md
ACTION_NOT_IN_SCOPE on run @actions.Xrun points at a utility / delegation / unresolved action instead of a topic-level target-backed definitionreferences/syntax-reference.md, references/instruction-resolution.md
Deterministic cancel / revise / URL checks behave inconsistentlyraw @system_variables.user_input matching or string-method guards are being used as control-flow-critical validationreferences/syntax-reference.md, references/production-gotchas.md
@outputs.X comparisons or assignments behave unexpectedlythe action output is structured/wrapped, not a plain scalarreferences/actions-reference.md, references/syntax-reference.md
Preview and runtime disagreelinked vars / context / known platform issuesreferences/known-issues.md
Validate passes but publish failsorg-specific user / permission / retrieve-back issuereferences/production-gotchas.md, references/cli-guide.md
ScoreMeaning
90+Deploy with confidence
75–89Good, review warnings
60–74Needs focused revision
< 60Block publish

Full rubric: references/scoring-rubric.md

Official Resources

Navigate Agentforce & AI