/agentforce-bot-upgrade

name: agentforce-bot-upgrade
description: "Use this skill to Upgrade Einstein Bots into Agentforce agents end-to-end in a single pass, orchestrating per-bot Agent Spec generation, planner reconciliation across bots, agentforce-generate authoring, and post-conversion .agent enhancements. TRIGGER when: user asks to migrate, upgrade, or convert one or more Einstein Bots to Agentforce; runs a multi-bot bot-to-agent upgrade; needs Einstein Bot metadata turned into Agent Spec handoffs and generated .agent agents; convert bots to agents; upgrade my service bots; move bots to Agentforce. DO NOT TRIGGER when: user already has an approved Agent Spec and only wants direct .agent authoring, deploy, test, or observe flows; the request is unrelated to Einstein Bot migration."
argument-hint: "[--mode <online|offline>] [--org-alias <org-alias> --bots <bot1:v1,bot2:v2,...> | --offline-dir <offline-dir> [--bots <bot1,bot2,...>]] [--interactive <true|false>]"
metadata:
  version: "1.0"
  domains: ["Agentforce"]
  minApiVersion: "63.0"
  relatedSkills:
    - "agentforce-generate"
  cliTools:
    - tool: ["sf"]
      semver: ">=2.0.0"

Einstein Bot Upgrade Orchestrator

Purpose

Run a multi-bot upgrade-and-handoff cycle:

1. Parse and validate bot/version pairs from `--bots` 2. Follow [Generate Agent Spec Reference](references/generate-agent-spec.md) per bot-version pair (parallelizable) 3. Aggregation step that requires all generated Agent Specs 4. `/agentforce-generate` per Agent Spec (parallelizable) 5. Post-conversion enhancement pass per generated Agent Script (parallelizable)

Inputs

Inputs:

• `--mode <online|offline>` is optional; default is `online` when omitted.
• If `mode=online`, required:
• `--org-alias <org-alias>`
• `--bots <bot1:v1,bot2:v2,...>`
• If `mode=offline`, required:
• `--offline-dir <offline-dir>`
• `--interactive <true|false>` is optional; default is `true` when omitted.

If required inputs are missing, handle per the Missing Input Handling and Interactive Mode rules below.

Interactive Mode

`--interactive` controls whether the skill pauses for user input during execution:

• `--interactive true` (default): resolve ambiguities, open questions, and approval gates by asking the user, as described in this skill and its references.
• `--interactive false`: run autonomously. Do NOT prompt the user at any decision point. For every open question, ambiguity, or approval gate, apply the documented recommended default/solution and record the auto-applied decision in the run artifacts (Agent Spec, open questions, extraction summary). The only hard stops permitted without prompting are inputs that are missing or contradictory with no safe recommended default — a missing mandatory launch input (`--org-alias`/`--bots` for online, `--offline-dir` for offline), no bots discovered, or the same bot given multiple versions. In those cases, report the issue and halt without prompting.

Propagate the effective `--interactive` value to the per-bot Generate Agent Spec workflow (Step 2), the planner workflow (Step 3), and the post-conversion enhancement pass (Step 5).

Missing Input Handling

Resolve missing required launch inputs before Step 1:

1. **Online mode — `--org-alias` not provided.** Resolve this before attempting to list bots (listing requires a target org).

• Interactive: list the available aliases of logged-in orgs and ask the user to select the target org. Use the SF CLI patterns in [SF CLI Bot Reference](references/sf-cli-bot-reference.md).
• Non-interactive: halt with an explicit error naming the missing `--org-alias` input (do not prompt or list).

2. **Online mode — bot name and version (`--bots`) not available.**

• Interactive: using `--org-alias` as the target org, list every bot and its versions in the org, then ask the user to select the bot/version entries they want to convert to agents. Use the `BotDefinition` and `BotVersion` query patterns in [SF CLI Bot Reference](references/sf-cli-bot-reference.md) — omit the name/version filters to enumerate all bots and versions — present the results, and build the `--bots` workload from the user's selection.
• Non-interactive: halt with an explicit error naming the missing `--bots` input (do not prompt or list).

3. **Offline mode — `--offline-dir` not available.**

• Interactive: ask the user to provide the `--offline-dir` path, then continue.
• Non-interactive: fail with an explicit error naming the missing `--offline-dir` input (do not prompt).

References

Use these reference files during execution:

1. [SF CLI Bot Reference](references/sf-cli-bot-reference.md) 2. [Generate Agent Spec Reference](references/generate-agent-spec.md) 3. [Planner Workflow Reference](references/planner-workflow-reference.md) 4. [Post-Conversion Enhancements Reference](references/post-conversion-enhancements-reference.md) 5. [Extraction Blueprint](references/extraction-blueprint.md) 6. [Input Contract](references/input-contract.md) 7. [Mapping Rules](references/mapping-rules.md) 8. [Handoff Output Format](references/handoff-output-format.md) 9. [Quality Checklist](references/quality-checklist.md)

Execution Contract

Step 1: Parse and Validate `--bots`

Execute Step 1 in this order:

1. Resolve mode:

• If `--mode` omitted, use `online`.

2. Start fresh for this invocation:

• do not discover, inspect, or reuse outputs from previously existing runs
• treat this invocation as a clean execution context
• only use artifacts produced during the current invocation flow

3. Build initial workload list:

• `mode=online`: read `--bots` and split by comma.
• `mode=offline`: scan `<offline-dir>` and collect immediate sub-directories as bot workload roots.

4. Validate input shape:

• `mode=online`: each `--bots` token must match `<bot-name>:<version>`.
• `mode=offline`: ensure at least one bot sub-directory exists; otherwise STOP (in interactive mode ask the user to clarify; in non-interactive mode h