Skip to content

forcedotcom/sf-skills / plugins/builder/agentforce-adlc/skills/agentforce-generate

agentforce-generate

Flagged

Build, 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.

FileKindSize
README.mdmarkdown5.4 KB
SKILL.mdskill md31.7 KB
assets/agent-spec-template.mdmarkdown6.4 KB
assets/agents/README.mdmarkdown2.6 KB
assets/agents/hello-world.agentother1.9 KB
assets/agents/knowledge-grounded.agentother5.6 KB
assets/agents/local-info-agent-annotated.agentother17.0 KB
assets/agents/order-service.agentother11.7 KB
assets/agents/production-faq.agentother3.9 KB
assets/agents/production-faq.bundle-meta.xmlconfig161 B
assets/agents/router-first.agentother5.6 KB
assets/agents/simple-qa.agentother1.9 KB
assets/agents/template-multi-subagent.agentother5.4 KB
assets/agents/template-single-subagent.agentother2.6 KB
assets/agents/verification-gate.agentother10.7 KB
assets/agents/voice-knowledge-grounded.agentother8.2 KB
assets/agents/voice-service-agent.agentother4.6 KB
assets/bundle-meta.xmlconfig808 B
assets/invocable-apex-template.clsother6.9 KB
assets/patterns/README.mdmarkdown10.8 KB
assets/patterns/action-callbacks.agentother4.7 KB
assets/patterns/advanced-input-bindings.agentother6.9 KB
assets/patterns/bidirectional-routing.agentother5.6 KB
assets/patterns/critical-input-collection.agentother12.2 KB
assets/patterns/delegation-routing.agentother6.4 KB
assets/patterns/lifecycle-events.agentother4.7 KB
assets/patterns/llm-controlled-actions.agentother5.1 KB
assets/patterns/multi-step-workflow.agentother10.1 KB
assets/patterns/open-gate-routing.agentother11.6 KB
assets/patterns/procedural-instructions.agentother4.8 KB
assets/patterns/prompt-template-action.agentother6.6 KB
assets/patterns/system-instruction-overrides.agentother10.6 KB
references/action-prompt-templates.mdmarkdown5.7 KB
references/actions-reference.mdmarkdown30.2 KB
references/agent-access-guide.mdmarkdown2.9 KB
references/agent-audit-and-repair.mdmarkdown7.9 KB
references/agent-audit-candidate-verification.mdmarkdown5.2 KB
references/agent-audit-diagnostic-catalog.mdmarkdown7.6 KB
references/agent-audit-diagnostics-actions-state.mdmarkdown6.9 KB
references/agent-audit-diagnostics-architecture-evaluation.mdmarkdown2.5 KB
references/agent-audit-diagnostics-instructions-routing.mdmarkdown11.8 KB
references/agent-audit-evaluation-loop.mdmarkdown6.0 KB
references/agent-audit-repair-report.mdmarkdown6.9 KB
references/agent-audit-scope-path-review.mdmarkdown8.5 KB
references/agent-design-and-spec-creation.mdmarkdown54.5 KB
references/agent-metadata-and-lifecycle.mdmarkdown30.2 KB
references/agent-script-core-language.mdmarkdown49.3 KB
references/agent-subagent-map-diagrams.mdmarkdown10.8 KB
references/agent-user-setup.mdmarkdown27.8 KB
references/agent-validation-and-debugging.mdmarkdown44.6 KB
references/agentscript-toolchain.mdmarkdown4.6 KB
references/architecture-patterns.mdmarkdown13.5 KB
references/common-control-flow-pitfalls.mdmarkdown9.4 KB
references/complex-data-types.mdmarkdown3.9 KB
references/control-flow-actions-sequencing.mdmarkdown6.9 KB
references/control-flow-lifecycle-side-effects.mdmarkdown3.3 KB
references/data-library-reference.mdmarkdown40.8 KB
references/deploy-reference.mdmarkdown6.7 KB
references/discover-reference.mdmarkdown4.3 KB
references/examples.mdmarkdown12.6 KB
references/feature-validity.mdmarkdown2.1 KB
references/instruction-resolution.mdmarkdown23.4 KB
references/known-issues.mdmarkdown27.6 KB
references/legacy-nga-regression-eval.mdmarkdown30.2 KB
references/mcp-management-reference.mdmarkdown37.6 KB
references/optimization-pattern-1-data-flow.mdmarkdown4.6 KB
references/optimization-pattern-2-deterministic-logic.mdmarkdown5.4 KB
references/optimization-pattern-3-reference-syntax.mdmarkdown4.1 KB
references/optimization-pattern-4-escalation.mdmarkdown2.2 KB
references/org-setup-for-adl.mdmarkdown23.7 KB
references/patterns-by-requirement.mdmarkdown5.4 KB
references/posture-and-determinism.mdmarkdown9.3 KB
references/production-gotchas.mdmarkdown12.6 KB
references/reference-map.mdmarkdown5.3 KB
references/safety-review-reference.mdmarkdown6.3 KB
references/salesforce-cli-for-agents.mdmarkdown16.7 KB
references/scaffold-reference.mdmarkdown6.7 KB
references/scoring-rubric.mdmarkdown3.3 KB
references/upgrade-legacy-agent-to-agentscript.mdmarkdown26.2 KB
references/version-history.mdmarkdown4.4 KB
references/voice-latency-heuristics.mdmarkdown9.7 KB
references/voice-modality-reference.mdmarkdown19.0 KB
references/voice-telephony-cli.mdmarkdown10.3 KB
references/zen-of-agentscript.mdmarkdown13.1 KB
scripts/__init__.pyscript0 B
scripts/agentscript-sdk-loader.mjsscript4.0 KB
scripts/discover.pyexecutablescript20.2 KB
scripts/generators/__init__.pyscript0 B
scripts/generators/apex_stub.pyscript13.4 KB
scripts/generators/apex_test_stub.pyscript3.8 KB
scripts/generators/flow_xml.pyscript7.6 KB
scripts/generators/permission_set_xml.pyscript1014 B
scripts/generators/remote_site_xml.pyscript1.4 KB
scripts/index-agent.mjsexecutablescript3.8 KB
scripts/org_describe.pyexecutablescript5.8 KB
scripts/scaffold.pyexecutablescript15.1 KB
scripts/setup-agentscript-sdk.mjsexecutablescript9.7 KB
scripts/upgrade-legacy-nga-analyze.pyexecutablescript20.0 KB
scripts/upgrade-legacy-nga-run-trials.shexecutablescript3.4 KB

assets/patterns/system-instruction-overrides.agent

View on GitHub
# System Instruction Overrides Pattern
# Customize agent behavior with dynamic system-level instructions
#
# ★ When To Use This Pattern:
#   - Different behavior for different user segments (VIP, standard, etc.)
#   - Time-based instruction changes (business hours vs after hours)
#   - Feature flags that change agent personality
#   - A/B testing different conversation styles
#
# ★ Key Insight:
#   - Global system instructions are the default for subagents without overrides
#   - A subagent system block REPLACES the global instructions; it does not extend
#     them, so every durable safety and scope invariant must be restated
#   - Use conditionals in reasoning to dynamically adjust tone
#   - Variables can control instruction branches
#
# ★ Important Limitation:
#   - The system: block itself cannot use conditionals or variables
#   - Dynamic behavior must be implemented in subagent reasoning
#
# This is a COMPLETE template - customize for your use case

system:
    # Default instructions for subagents that do not define their own system block.
    instructions: |
        You are a professional customer service agent. Perform only the current
        operating task. Answer the underlying request only when that task calls
        for an answer; otherwise route, verify, refuse, or escalate as directed.
        Never share confidential information.
    messages:
        welcome: "Hello! How can I assist you today?"
        error: "I apologize, but I encountered an issue. Let me try that again."

access:
    default_agent_user: "agent@company.salesforce.com"

config:
    developer_name: "Dynamic_Service_Agent"
    agent_label: "Dynamic Service Agent"
    description: "Agent with dynamic instruction overrides based on context"

variables:
    # Standard linked variables
    EndUserId: linked string
        source: @MessagingSession.MessagingEndUserId
        description: "Messaging End User ID"
    RoutableId: linked string
        source: @MessagingSession.Id
        description: "Messaging Session ID"
    ContactId: linked string
        source: @MessagingEndUser.ContactId
        description: "Contact ID"

    # Variables for dynamic instruction control
    customer_tier: mutable string = "standard"
        description: "Customer tier: standard, premium, or vip"
    business_hours: mutable boolean = True
        description: "Whether we're in business hours"
language:
    default_locale: "en_US"
    additional_locales: ""
    all_additional_locales: False

start_agent agent_router:
    label: "Request Router"
    description: "Routes to the appropriate service area based on user tier"

    # ★ Use before_reasoning to set up context-based variables
    before_reasoning:
        # In a real implementation, these would come from a Flow/Apex lookup
        # Here we show the pattern
        run @actions.get_customer_tier
            with contact_id=@variables.ContactId
            set @variables.customer_tier = @outputs.tier
        run @actions.check_business_hours
            set @variables.business_hours = @outputs.is_business_hours

    reasoning:
        # The router performs classification and transition only. Response
        # guidance belongs in the service subagent that answers the request.
        instructions: ->
            | Route the customer to the appropriate service area. Do not answer the
              underlying request or provide service from the router.

        actions:
            go_orders: @utils.transition to @subagent.orders
            go_billing: @utils.transition to @subagent.billing
            go_support: @utils.transition to @subagent.support
                available when @variables.business_hours == True

    actions:
        get_customer_tier:
            description: "Get customer tier from Salesforce"
            inputs:
                contact_id: string
                    description: "Contact ID to look up"
            outputs:
                tier: string
                    description: "Customer tier: standard, premium, vip"
            target: "flow://Get_Customer_Tier"

        check_business_hours:
            description: "Check if currently in business hours"
            outputs:
                is_business_hours: boolean
                    description: "True if in business hours"
            target: "flow://Check_Business_Hours"

subagent orders:
    label: "Order Management"
    description: "Handle order inquiries with tier-appropriate service"

    reasoning:
        instructions: ->
            # ★ Tier-specific instructions carry through to subagents
            if @variables.customer_tier == "vip":
                | This is a VIP customer. Expedite all order requests.
                  Offer free shipping upgrades proactively.

            | Help the customer with their order inquiry.
              Look up order status, process changes, or handle returns.

        actions:
            back: @utils.transition to @subagent.agent_router

subagent billing:
    label: "Billing Support"
    description: "Handle billing with appropriate authority levels"

    reasoning:
        instructions: ->
            # ★ Different authority based on tier
            if @variables.customer_tier == "vip":
                | You can waive fees up to $100 for VIP customers.
                  Proactively offer payment plan options.
            else if @variables.customer_tier == "premium":
                | You can waive fees up to $25 for premium customers.
            else if @variables.customer_tier == "standard":
                | Fee waivers require manager approval. Escalate if requested.

            | Help the customer understand their bill and resolve issues.

        actions:
            back: @utils.transition to @subagent.agent_router
            escalate: @utils.escalate
                description: "Transfer to billing specialist"
                available when @variables.customer_tier == "standard"

subagent support:
    label: "Technical Support"
    description: "Technical support with business hours awareness"

    reasoning:
        instructions: ->
            if @variables.business_hours == False:
                | Technical support is limited outside business hours.
                  Log the issue for follow-up and provide self-service resources.

            if @variables.business_hours == True:
                | Full technical support available. Troubleshoot thoroughly.

            | Help resolve the customer's technical issue.

        actions:
            back: @utils.transition to @subagent.agent_router

# ═══════════════════════════════════════════════════════════════════════════
# ★ SUBAGENT-LEVEL SYSTEM OVERRIDES (NEW PATTERN)
# These subagents demonstrate complete persona switching using subagent-level
# system: blocks that OVERRIDE the global system instructions.
# ═══════════════════════════════════════════════════════════════════════════

subagent formal_mode:
    label: "Formal Communication"
    description: "Professional business communication mode"

    # ★ SUBAGENT-LEVEL SYSTEM OVERRIDE
    # This completely replaces global system instructions for this subagent
    system:
        instructions: |
            You are a formal business professional. Use professional language,
            focus on efficiency and clarity, and maintain a respectful corporate
            tone. Never share confidential information.

    reasoning:
        instructions: ->
            | Greet the user in the formal style defined by the system
              instructions and ask what business matter they need help with.

        actions:
            back: @utils.transition to @subagent.agent_router

subagent creative_mode:
    label: "Creative Assistant"
    description: "Creative and imaginative communication mode"

    # ★ SUBAGENT-LEVEL SYSTEM OVERRIDE
    # Different persona entirely
    system:
        instructions: |
            You are a creative and imaginative assistant. Be playful, use
            metaphors and analogies, and encourage brainstorming. Never share
            confidential information.

    reasoning:
        instructions: ->
            | Greet the user in the playful, imaginative style defined by the
              system instructions and ask what they want to create or explore.

        actions:
            back: @utils.transition to @subagent.agent_router

subagent technical_expert:
    label: "Technical Expert"
    description: "Deep technical expertise mode"

    # ★ SUBAGENT-LEVEL SYSTEM OVERRIDE
    # Specialist persona
    system:
        instructions: |
            You are a technical expert. Use precise terminology and detailed
            examples, and reference documentation when helpful. Never share
            confidential information.

    reasoning:
        instructions: ->
            | Greet the user as a technical expert, match their apparent level
              of technical detail, and ask what technical problem they need to
              solve.

        actions:
            back: @utils.transition to @subagent.agent_router

# ★ Insight: Three Levels of Instruction Control
#
# LEVEL 1: GLOBAL SYSTEM BLOCK
#   - Static text only (no variables, no conditionals)
#   - Applies only where a subagent system block does not replace it
#   - Good for: Default guardrails, scope, and personality
#   - Example: "Never share confidential information"
#
# LEVEL 2: SUBAGENT-LEVEL SYSTEM BLOCK (NEW!)
#   - Placed inside subagent definition
#   - COMPLETELY OVERRIDES global system for that subagent
#   - Good for: Persona switching, mode changes, specialist behavior
#   - Example: subagent formal_mode: system: instructions: "Be professional..."
#
# LEVEL 3: SUBAGENT REASONING INSTRUCTIONS
#   - Dynamic (variables, conditionals, template expressions)
#   - Extends/adjusts behavior within subagent
#   - Good for: Context-aware responses, personalization
#   - Example: if @variables.is_vip: | Provide priority service
#
# OVERRIDE HIERARCHY:
#   Subagent system: > Global system: > Default behavior
#
# COMBINING APPROACHES:
#   - Use GLOBAL system for default guardrails
#   - Use SUBAGENT system only for a necessary complete replacement
#   - Restate every durable guardrail in each subagent replacement
#   - Use SUBAGENT reasoning for dynamic conditional behavior
#
# Best Practice: Prefer reasoning instructions for persona adjustments. If a
# subagent system replacement is necessary, restate all required guardrails.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall