New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Agentforce Bot Upgrade

by forcedotcom in forcedotcom/sf-skills

A skill your agent uses to Upgrade Einstein Bots into Agentforce agents end-to-end in a single pass, orchestrating per-bot Agent Spec generation, planner reconciliation across bots…

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Agentforce Bot Upgrade

skills CLI
$ npx skills add forcedotcom/sf-skills --skill agentforce-bot-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills agentforce-bot-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agentforce-bot-upgrade .claude/skills/agentforce-bot-upgrade && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agentforce-bot-upgrade
GitHub stars
1.1k
Token cost
~3.6k tokens
SKILL.md length
1,562 words
Files
10 (incl. references)
Skills in repo
248
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses to Upgrade Einstein Bots into Agentforce agents end-to-end in a single pass, orchestrating per-bot Agent Spec generation, planner reconciliation across bots…

  • Works in 6 steps: Parse and Validate --bots → Run Einstein Bot Upgrade (Per Bot-Version) → Aggregation + Planner Step (Conditional) → …
  • Upgrade Einstein Bots into Agentforce agents end-to-end in a single pass
  • SKILL.md covers Purpose, Inputs, Interactive Mode and Missing Input Handling, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agentforce Bot Upgrade is an agent skill from forcedotcom/sf-skills. 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 (BotDefinition/BotVersion chatbots) to Agentforce agents; runs a multi-bot bot-to-agent upgrade; needs Einstein Bot metadata turned into Agent Spec handoffs and generated .agent agents…

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/extraction-blueprint.md`, `references/generate-agent-spec.md` and `references/handoff-output-format.md`).

It sits in Business, Finance & HR, covering Chatbots and conversational support and Accounting and bookkeeping. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • 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

Example prompts

  • “Migrate a Legacy Agent to Agent Script”
  • “/agentforce-bot-upgrade”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Parse and Validate --bots
  2. Run Einstein Bot Upgrade (Per Bot-Version)
  3. Aggregation + Planner Step (Conditional)
  4. Invoke Agentforce-Generate (Per Agent Spec)
  5. Post-Conversion Agent Script Enhancements (Per Generated Agent Script)
  6. Consolidate Run Report and Conclude

What it can do on your machine

Read from SKILL.md and the folder at commit 3c15867. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agentforce Bot Upgrade loads about 3.6k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 256 tokens; SKILL.md has 1,562 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~256
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit 3c15867, republished under its Apache-2.0 licence (© forcedotcom). 1,562 words, ~3,612 tokens.

Download SKILL.mdSave it as .claude/skills/agentforce-bot-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
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 (BotDefinition/BotVersion chatbots) to Agentforce agents; 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; user wants to migrate or upgrade an EXISTING Agentforce agent from a legacy GenAiPlannerBundle to an NGA aiAuthoringBundle (that is agentforce-generate's 'Migrate a Legacy Agent to Agent Script' flow, not an Einstein Bot upgrade); 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…
metadata.version
1.0
metadata.domains
Agentforce
metadata.minApiVersion
63.0
metadata.relatedSkills
agentforce-generate

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 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)

Scope — this skill only converts Einstein Bots (BotDefinition/BotVersion chatbots) into new Agentforce agents. It does NOT migrate an existing Agentforce agent from a legacy GenAiPlannerBundle to an NGA aiAuthoringBundle — for that, use the agentforce-generate skill's "Migrate a Legacy Agent to Agent Script" flow.

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.
    • 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 — 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
  2. Generate Agent Spec Reference
  3. Planner Workflow Reference
  4. Post-Conversion Enhancements Reference
  5. Extraction Blueprint
  6. Input Contract
  7. Mapping Rules
  8. Handoff Output Format
  9. Quality Checklist

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 halt with an explicit error per the Interactive Mode rule).
  5. Normalize workload entries:
    • mode=online: build {bot_name, bot_version} entries.
    • mode=offline: build {offline_bot_dir} entries (Annotate inferred bot name and version when derivable from the sub-directory structure; if not derivable, leave the entry unnamed and continue).
  6. Enforce one-version-per-bot rule (online mode):
    • If the same bot_name appears with multiple versions, STOP (in interactive mode ask the user to clarify; in non-interactive mode halt with an explicit error per the Interactive Mode rule).
  7. Apply offline bot filter:
    • If mode=offline and --bots is provided, use --bots only as a filter over discovered sub-directories; do not treat it as required offline input.
  8. Persist Step 1 output:
    • Save and carry forward a validated workload list for Step 2 parallel execution.
Step 2: Run Einstein Bot Upgrade (Per Bot-Version)

Execute the agent spec generation workflow from Generate Agent Spec Reference per bot-version combination:

  • --mode <online|offline> (default online if omitted)
  • mode-specific required inputs:
    • online -> --org-alias, --bot, --bot-version
    • offline -> --offline-dir
  • --interactive <true|false> (pass through the effective orchestrator value; default true)

Parallelization rule:

  • In mode=online, execute invocations in parallel because each bot-version pair is independent.
  • In mode=offline, execute the Generate Agent Spec Reference workflow in parallel over every bot sub-directory discovered in Step 1.
    • Pass --mode offline and --offline-dir <bot-subdirectory-path> per invocation. Ensure each invocation (online/offline) uses isolated working directories to avoid cross-run file collisions.

Hard rules:

  • Do not skip this step.
Show full SKILL.md (687 more words)Show less
Step 3: Aggregation + Planner Step (Conditional)

After all upgrade invocations complete:

  1. Always build a consolidated list of {bot_name, bot_version, run_project_dir, agent_spec_path}.
  2. Always build list of failed/incomplete upgrade runs (if any).
  3. Always build an initial ready-for-authoring list containing only valid Agent Spec entries.
    • Each entry must include: {bot_name, bot_version, run_project_dir, agent_spec_path, handoff_json_path, open_questions_path}.
  4. If total bot workload count is greater than 1:
    • Execute planner workflow from Planner Workflow Reference using:
      • all ready-for-authoring agent_spec_path values as spec_paths
      • orchestrator working directory as working_dir
      • the associated per-spec artifacts from each ready-for-authoring entry: handoff_json_path (handoff JSON) and open_questions_path (open questions)
    • Require output file at <orchestrator working directory>/bot-upgrade-planner-output.json.
    • Read bot-upgrade-planner-output.json and apply:
      • if specs_changed=true: replace ready-for-authoring entries using planner fields (updated_spec_path, run_project_dir, handoff_json_path, open_questions_path)
      • if specs_changed=false: keep original ready-for-authoring list unchanged
  5. If total bot workload count is 1:
    • Skip planner workflow entirely.
    • Keep original ready-for-authoring list unchanged.

Planner output expectations:

  1. boolean specs_changed
  2. updated_specs array with entries:
    • original_spec_path
    • updated_spec_path
    • run_project_dir
    • handoff_json_path
    • open_questions_path
  3. updated_specs must be empty when specs_changed=false
Step 4: Invoke Agentforce-Generate (Per Agent Spec)

For each entry in final ready-for-authoring list (post Step 3 planner reconciliation):

  1. Add this recommendation to the generated invocation context before calling /agentforce-generate:
    • Do not activate Agent Script versions in this orchestrated run.
    • Draft iteration is required: generating .agent, validating, deploying, and preview testing are allowed.
    • Activate should be deferred unless the user explicitly asks for release.
  2. Resolve effective run_project_dir from the final ready-for-authoring entry.
  3. Read <run_project_dir>/agentforce-generate-invocation-prompt.md fully.
  4. If Step 3 produced planner-updated spec paths/artifacts, apply path substitutions in the invocation context so spec/handoff/open-questions references point to updated files.
    • If planner also changed run_project_dir, use that updated run_project_dir for resolving prompt/output-contract paths.
  5. Keep all non-path instructions unchanged from the original generated prompt.
  6. Invoke /agentforce-generate with this resolved invocation context.
  7. Read <run_project_dir>/agentforce-generate-output-contract.md and capture outputs exactly as specified.

Parallelization rule:

  • Invoke /agentforce-generate in parallel across Agent Specs because each run is independent.

Output-contract capture rules:

  1. Treat the output contract as authoritative for required fields/artifacts.
  2. If any contract field is missing, mark status as partial and list missing fields explicitly.
  3. Return captured outputs with deterministic keys matching the contract names.
  4. Preserve output file paths and status of each required artifact.
  5. If expected prompt/contract files are missing for an entry, mark that entry partial, record missing paths, and continue processing other entries.
Step 5: Post-Conversion Agent Script Enhancements (Per Generated Agent Script)

After Step 4 completes, for each generated .agent artifact:

  1. Resolve the generated .agent file path from captured /agentforce-generate outputs.
  2. Execute post-conversion enhancement workflow from Post-Conversion Enhancements Reference with:
    • agentscript_file=<generated-agent-file-path>
    • mode=<online|offline> (the effective orchestrator run mode resolved in Step 1)
    • online mode only: org_alias=<org-alias> (required so the enhanced Agent Script can be redeployed)
  3. Require in-place enhancement:
    • optimized/enhanced output must be written to the same .agent file location.
  4. Capture per-file enhancement status and any partial failures.

Parallelization rule:

  • Execute post-conversion enhancement workflow in parallel across generated .agent files because each file enhancement is independent.
Step 6: Consolidate Run Report and Conclude

After Step 5 completes for every bot in the workload:

  1. Write a single consolidated, human-readable run report as a non-empty Markdown file in the orchestrator working directory. Per bot, the report must state: the effective run mode, whether the planner ran (executed or skipped), the generated Agent Spec path and generated .agent path, the action inventory (including any NEEDS_STUB items), and — when --interactive=false — the auto-applied decisions.
  2. Treat the run report as the FINAL artifact: write it only after all other artifacts (Agent Spec(s), handoff JSON, open questions, any planner output, and generated .agent file(s)) are already written.

Deliverable

Return:

  1. parsed bot/version list
  2. per-bot upgrade execution status
  3. aggregation output (full Agent Spec list + final ready-for-authoring subset)
  4. planner workflow status (executed or skipped) and bot-upgrade-planner-output.json path when executed
  5. per-spec /agentforce-generate execution status
  6. generated handoff artifact paths per bot/spec (including planner-updated artifacts when applicable)
  7. captured /agentforce-generate outputs per output contract
  8. per-agent post-conversion enhancement status (including enhanced .agent file paths)
  9. path to the consolidated run report written in Step 6

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in skills/agentforce-bot-upgrade of forcedotcom/sf-skills.

  • SKILL.md
  • references/extraction-blueprint.md
  • references/generate-agent-spec.md
  • references/handoff-output-format.md
  • references/input-contract.md
  • references/mapping-rules.md
  • references/planner-workflow-reference.md
  • references/post-conversion-enhancements-reference.md
  • references/quality-checklist.md
  • references/sf-cli-bot-reference.md

Open the folder on GitHubat commit 3c15867

Compare with similar skills

Agentforce Bot Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agentforce Bot Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agentforce Bot Upgrade this skillforcedotcom/sf-skills1.1k—~3.6kAutomated safety check: PassApache-2.0
Senpi WhySenpi-ai/senpi-skills134—~2.5kAutomated safety check: PassApache-2.0
Portfolio Management SystemsJoelLewis/finance_skills205—~3.3kAutomated safety check: PassMIT
Sync Upstreamnyaruka/phonenumbers1.6k—~2.8kAutomated safety check: PassMIT
Longbridge Value Investinghelsome/folio2692 repos~1.2kAutomated safety check: PassMIT
Radiology Tablehuang-sir1/radiology-skills1.9k—~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Senpi Why

    Senpi-ai/senpi-skills

    Answer "what makes Senpi different?" / "why Senpi?" / "Senpi vs other trading apps, bots or AI chatbots?" — the positioning answer, led by value, not a feature dump.

    134 GitHub stars~2.5k tokensUpdated today
    Business, Finance & HRAuto-check passed

  • Portfolio Management Systems

    JoelLewis/finance_skills

    Select, configure, and operate portfolio management systems for advisory firms, covering model portfolios, UMA/sleeve management, drift monitoring, rebalancing, and custodian data feeds.

    205 GitHub stars~3.3k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed

  • Sync Upstream

    nyaruka/phonenumbers

    Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.

    1.6k GitHub stars~2.8k tokensUpdated 5 days ago
    Business, Finance & HRAuto-check passed

  • Longbridge Value Investing

    helsome/folio

    Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies.

    269 GitHub starsUsed in 2 repos~1.2k tokens
    Business, Finance & HRAuto-check passed

  • Radiology Table

    huang-sir1/radiology-skills

    Create/audit editable publication tables with source reconciliation; not figures or statistical inference.

    1.9k GitHub stars~1.3k tokensUpdated 16 days ago
    Business, Finance & HRAuto-check passed

  • Odoo Agency Fleet Review

    erpipe-org/mcp-odoo

    Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…

    419 GitHub stars~699 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

More from forcedotcom/sf-skills

All 248 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~3.6k tokensUpdated 5 days ago
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~2.9k tokensUpdated 5 days ago
    Auto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated 5 days ago
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated 5 days ago
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated 5 days ago
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Agentforce Bot Upgrade

What does Agentforce Bot Upgrade do?

A skill your agent uses 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 Bot Upgrade is an agent skill from forcedotcom/sf-skills.agent enhancements.

When should I use Agentforce Bot Upgrade?

Agentforce Bot Upgrade fits situations like: 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.

How do I install Agentforce Bot Upgrade in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill agentforce-bot-upgrade -a claude-code`. Or copy the skill folder (skills/agentforce-bot-upgrade in forcedotcom/sf-skills) into .claude/skills/agentforce-bot-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Agentforce Bot Upgrade in Codex?

Run `npx skills add forcedotcom/sf-skills --skill agentforce-bot-upgrade -a codex`. Or copy the skill folder (skills/agentforce-bot-upgrade in forcedotcom/sf-skills) into .agents/skills/agentforce-bot-upgrade in your project. Codex loads it when a task matches its description.

Can I use Agentforce Bot Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill agentforce-bot-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agentforce-bot-upgrade, .gemini/skills/agentforce-bot-upgrade, .github/skills/agentforce-bot-upgrade and .opencode/skills/agentforce-bot-upgrade in your project.

What does Agentforce Bot Upgrade need to run?

SKILL.md names no scripts, command-line tools or credentials: Agentforce Bot Upgrade is instructions for the agent only.

Does Agentforce Bot Upgrade access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agentforce Bot Upgrade safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agentforce Bot Upgrade use?

Agentforce Bot Upgrade is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agentforce Bot Upgrade use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.

What are the alternatives to Agentforce Bot Upgrade?

Skills that share tags, products or a category with Agentforce Bot Upgrade: Senpi Why (Senpi-ai/senpi-skills, 134 stars), Portfolio Management Systems (JoelLewis/finance_skills, 205 stars), Sync Upstream (nyaruka/phonenumbers, 1.6k stars) and Longbridge Value Investing (helsome/folio, 269 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agentforce Bot Upgrade?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,058 GitHub stars. The repository holds 248 skills in this directory. The repository was last updated on October 3, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.