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

Commerce B2b Open Code Components Integrate

by forcedotcom in forcedotcom/sf-skills

Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores.

Apache-2.0Auto-check passedSales & Support

Install Commerce B2b Open Code Components Integrate

skills CLI
$ npx skills add forcedotcom/sf-skills --skill commerce-b2b-open-code-components-integrate -a claude-code

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

GitHub CLI
$ gh skill install forcedotcom/sf-skills commerce-b2b-open-code-components-integrate --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/commerce-b2b-open-code-components-integrate .claude/skills/commerce-b2b-open-code-components-integrate && 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
commerce-b2b-open-code-components-integrate
GitHub stars
1.1k
Token cost
~2.2k tokens
SKILL.md length
938 words
Files
1
Skills in repo
248
Repo updated
First seen
Licence
Apache-2.0

At a glance

Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores.

  • Works in 4 steps: If directory does not exist: Tell user:… → If directory exists and contains… → If directory exists but structure is… → …
  • Users mention integrate open code components
  • SKILL.md covers When to Use This Skill, Rules, Overview and Startup Flow, plus 4 more sections
  • Calls sf and git; reaches github.com

What it does

Commerce B2b Open Code Components Integrate is an agent skill from forcedotcom/sf-skills. Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention "integrate open code components", "open source B2B commerce", "add open code components", "forcedotcom/b2b-commerce-open-source-components", or want to add open source commerce components to their store. Copies all components and labels so they become available in Experience Builder.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering CRM management. It works with Salesforce and GitHub. 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

  • Users mention integrate open code components
  • Open source B2B commerce
  • Add open code components
  • Forcedotcom/b2b-commerce-open-source-components

Example prompts

  • “integrate open code components”
  • “open source B2B commerce”
  • “add open code components”
  • “/commerce-b2b-open-code-components-integrate”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git clone:*), Bash(cp:*), Bash(sf org list:*), Bash(sf config get:*), Bash(sf project retrieve start:*), Read

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. If directory does not exist: Tell user: "I'm cloning the official B2B Commerce open source components repository from GitHub into a local…
  2. If directory exists and contains force-app/main/default/sfdc_cmslwc and sfdc_cmslabel, present options
  3. If directory exists but structure is invalid: Tell user: "The cloned repository has an unexpected structure. I'll remove it and clone a…
  4. If clone fails: inform user and abort

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 these tools, so the agent can use them without asking each time:

    • Bash(git clone:*)
    • Bash(cp:*)
    • Bash(sf org list:*)
    • Bash(sf config get:*)
    • Bash(sf project retrieve start:*)
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • sf
    • git

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

Commerce B2b Open Code Components Integrate loads about 2.2k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 938 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

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). 938 words, ~2,171 tokens.

Download SKILL.mdSave it as .claude/skills/commerce-b2b-open-code-components-integrate/SKILL.md (or your agent's skills folder).
name
commerce-b2b-open-code-components-integrate
description
Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention "integrate open code components", "open source B2B commerce", "add open code components", "forcedotcom/b2b-commerce-open-source-components", or want to add open source commerce components to their store. Copies all components and labels so they become available in Experience Builder.
allowed-tools
Bash(git clone:*), Bash(cp:*), Bash(sf org list:*), Bash(sf config get:*), Bash(sf project retrieve start:*), Read
metadata.version
1.0
metadata.domains
Commerce, Experience
metadata.minApiVersion
56.0
metadata.relatedSkills
commerce-b2b-store-create

When to Use This Skill

Use this skill when you need to:

  • Integrate all open source B2B Commerce components into a store
  • Add open source components to a new or existing B2B Commerce store
  • Make open code components available in Experience Builder

Rules

  1. Always explain before executing. Before running any command, you MUST tell the user what the command does and why you are running it. Never just show a raw command and ask for permission. The user should be able to read your explanation and understand the purpose before approving.

Overview

This skill copies all open source B2B Commerce components from the official Salesforce repository (https://github.com/forcedotcom/b2b-commerce-open-source-components) into a B2B Commerce store's site metadata. After integration, the components appear in the Experience Builder component palette.

Startup Flow

When this skill is triggered, perform these checks automatically before copying.

Check 0: Resolve Package Directory

Read sfdx-project.json and pick the active package directory. Extract packageDirectories[] and use the entry with "default": true; if no entry is flagged default, use the first entry. Use this value as <package-dir> everywhere below. If sfdx-project.json is missing or has no packageDirectories, tell the user and abort.

Check 1: Open Source Repository

Verify the repo is cloned at .tmp/b2b-commerce-open-source-components:

  1. If directory does not exist: Tell user: "I'm cloning the official B2B Commerce open source components repository from GitHub into a local .tmp/ folder. This gives us access to all the open code components." Then run: git clone https://github.com/forcedotcom/b2b-commerce-open-source-components .tmp/b2b-commerce-open-source-components
  2. If directory exists and contains force-app/main/default/sfdc_cms__lwc and sfdc_cms__label, present options:

    "Open source repository is already cloned. How would you like to proceed?"

    1. Reuse existing — Use the already cloned repository
    2. Re-clone — Remove and clone fresh from GitHub
  3. If directory exists but structure is invalid: Tell user: "The cloned repository has an unexpected structure. I'll remove it and clone a fresh copy." Then remove and re-clone.
  4. If clone fails: inform user and abort
Check 2: Store and Site Metadata

Verify a store is selected and site metadata is available locally:

  1. Tell user: "I'm checking if your project already has B2B store metadata locally." Check if <package-dir>/main/default/digitalExperiences/site/ contains any store directories.
  2. If store metadata exists: use it. If multiple stores found, ask user to select one.
  3. If no store metadata found: Try retrieving from the connected org before delegating:
    1. Run sf org list (or check sf config get target-org) to find a connected org. Ask the user to confirm or pick one if more than one.
    2. List DigitalExperienceBundle site bundles in that org with sf org list metadata --metadata-type DigitalExperienceBundle --target-org <alias>. Filter to site/* entries.
    3. If at least one site bundle exists, ask the user which to use, then run: sf project retrieve start --metadata "DigitalExperienceBundle:site/<storeName>" --target-org <alias> The bundle lands at <package-dir>/main/default/digitalExperiences/site/<storeName>/.
    4. Only if no connected org is available, or no site bundles are found, or retrieve fails: delegate to the commerce-b2b-store-create skill.

Required state after all checks:

  • Package dir — the value resolved in Check 0 (e.g., force-app)
  • Store name — the selected fullName value (e.g., My_B2B_Store1)
  • Site metadata path — <package-dir>/main/default/digitalExperiences/site/<store-name>/
  • Repo path — .tmp/b2b-commerce-open-source-components/
Show full SKILL.md (420 more words)Show less

Integration Task

Copy all components and labels from cloned repo to site directory:

  • Source: .tmp/b2b-commerce-open-source-components/force-app/main/default/sfdc_cms__lwc/* and sfdc_cms__label/* (the open source repo's own layout — always force-app)
  • Destination: <package-dir>/main/default/digitalExperiences/site/<store-name>/sfdc_cms__lwc/ and sfdc_cms__label/ (<package-dir> resolved in Check 0)

Steps:

  1. Tell user: "I'm checking if open code components already exist in your store's site metadata." Check if destination directories already contain files.
  2. If files exist, present options:

    "Components already exist in {store-name}. How would you like to proceed?"

    1. Overwrite all — Replace all existing components with latest from repo
    2. Copy only new — Skip existing components, copy only ones not yet present
  3. Tell user: "I'm now copying all open code LWC components from the cloned repository into your store's site metadata directory." Copy all component directories from source to destination.
  4. Tell user: "I'm copying the associated label files that these components need." Copy all label directories from source to destination.
  5. Report: "Copied X components and Y label sets"

Output:

text
Integration Complete!

Copied: X components and Y label sets to <store-name>

Next Steps:
1. Deploy: sf project deploy start -d <package-dir>/main/default/digitalExperiences/site/<store-name>
2. Open Experience Builder and use new components from the palette
3. Publish your site when ready

Example Interaction

User: "Integrate open code components to my store"

Agent: "I'm checking if the open source components repository is already cloned locally..."

Agent: (repo exists)

"Open source repository is already cloned. How would you like to proceed?"

  1. Reuse existing — Use the already cloned repository
  2. Re-clone — Remove and clone fresh from GitHub

User: "1"

Agent: "I'm checking if your project already has B2B store metadata locally..."

  • [done] Found store metadata for My_B2B_Store1

Agent: "I'm checking if open code components already exist in your store's site metadata..."

Agent: (files exist)

"Components already exist in My_B2B_Store1. How would you like to proceed?"

  1. Overwrite all — Replace all existing components with latest from repo
  2. Copy only new — Skip existing components, copy only ones not yet present

User: "1"

Agent: "I'm now copying all open code LWC components from the cloned repository into your store's site metadata directory..." Agent: "I'm copying the associated label files that these components need..."

  • [done] Copied 45 components and 38 label sets
text
Integration Complete!

Copied: 45 components and 38 label sets to My_B2B_Store1

Next Steps:
1. Deploy: sf project deploy start -d force-app/main/default/digitalExperiences/site/My_B2B_Store1
2. Open Experience Builder and use new components from the palette
3. Publish your site when ready

Error Handling

ErrorMessageAction
Store not found"Store '{name}' not found in org."List stores again
Git clone failed"Failed to clone repository. Check internet connection."Retry or abort
Invalid repo structure"Repository structure has changed. Expected sfdc_cms__lwc and sfdc_cms__label."Warn user, abort
File copy failed"Failed to copy files. Check file permissions."Show error details

Verification Checklist

  • Startup Flow completed: repo cloned, store metadata available
  • Components copied to correct destination path (sfdc_cms__lwc/)
  • Labels copied to correct destination path (sfdc_cms__label/)
  • No file permission errors during copy
  • Deployment command provided and user informed about testing

© 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

Just SKILL.md in skills/commerce-b2b-open-code-components-integrate of forcedotcom/sf-skills.

Open the folder on GitHubat commit 3c15867

Compare with similar skills

Commerce B2b Open Code Components Integrate 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.

Commerce B2b Open Code Components Integrate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commerce B2b Open Code Components Integrate this skillforcedotcom/sf-skills1.1k—~2.2kAutomated safety check: PassApache-2.0
Integrationsbutterbase-ai/butterbase-skills534—~832Automated safety check: PassMIT
Airbyte AgentKilo-Org/kilo-marketplace189—~2.2kAutomated safety check: PassCustom licence
Gh Bot Commentjetstreamapp/jetstream125—~616Automated safety check: PassCustom licence
AirweaveCraftOS-dev/CraftBot392—~1.1kAutomated safety check: PassMIT
Sf ApexJaganpro/sf-skills424—~2kAutomated safety check: PassMIT

Similar skills

  • Integrations

    butterbase-ai/butterbase-skills

    Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…

    534 GitHub stars~832 tokensUpdated 2 days ago
    Sales & SupportAuto-check passed

  • Airbyte Agent

    Kilo-Org/kilo-marketplace

    Drive the airbyte-agent CLI to manage Airbyte connectors, workspaces, and organizations.

    189 GitHub stars~2.2k tokensUpdated 9 days ago
    Sales & SupportAuto-check passed

  • Gh Bot Comment

    jetstreamapp/jetstream

    Post GitHub PR/issue comments, reviews, and review replies as the Jetstream bot account instead of the user's personal account.

    125 GitHub stars~616 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Airweave

    CraftOS-dev/CraftBot

    Context retrieval layer for AI agents across users' applications.

    392 GitHub stars~1.1k tokensUpdated today
    Sales & SupportAuto-check passed

  • Sf Apex

    Jaganpro/sf-skills

    Generates and reviews Salesforce Apex code with 150-point scoring.

    424 GitHub stars~2k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Sf Debug

    Jaganpro/sf-skills

    Salesforce debug log analysis and troubleshooting with 100-point scoring.

    424 GitHub stars~1.3k tokensUpdated 5 mo ago
    Sales & SupportAuto-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

Works with

Categories

Questions about Commerce B2b Open Code Components Integrate

What does Commerce B2b Open Code Components Integrate do?

Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Commerce B2b Open Code Components Integrate is an agent skill from forcedotcom/sf-skills. Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores.

When should I use Commerce B2b Open Code Components Integrate?

Commerce B2b Open Code Components Integrate fits situations like: users mention integrate open code components; open source B2B commerce; add open code components; forcedotcom/b2b-commerce-open-source-components.

How do I install Commerce B2b Open Code Components Integrate in Claude Code?

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

How do I install Commerce B2b Open Code Components Integrate in Codex?

Run `npx skills add forcedotcom/sf-skills --skill commerce-b2b-open-code-components-integrate -a codex`. Or copy the skill folder (skills/commerce-b2b-open-code-components-integrate in forcedotcom/sf-skills) into .agents/skills/commerce-b2b-open-code-components-integrate in your project. Codex loads it when a task matches its description.

Can I use Commerce B2b Open Code Components Integrate 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 commerce-b2b-open-code-components-integrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commerce-b2b-open-code-components-integrate, .gemini/skills/commerce-b2b-open-code-components-integrate, .github/skills/commerce-b2b-open-code-components-integrate and .opencode/skills/commerce-b2b-open-code-components-integrate in your project.

What does Commerce B2b Open Code Components Integrate need to run?

Going by SKILL.md and its folder, Commerce B2b Open Code Components Integrate needs the command-line tools its instructions call (sf and git). Its frontmatter pre-approves these tools: Bash(git clone:*), Bash(cp:*), Bash(sf org list:*), Bash(sf config get:*), Bash(sf project retrieve start:*), Read.

Does Commerce B2b Open Code Components Integrate access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Commerce B2b Open Code Components Integrate 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 Commerce B2b Open Code Components Integrate use?

Commerce B2b Open Code Components Integrate 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 Commerce B2b Open Code Components Integrate use?

About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commerce B2b Open Code Components Integrate?

Skills that share tags, products or a category with Commerce B2b Open Code Components Integrate: Integrations (butterbase-ai/butterbase-skills, 534 stars), Airbyte Agent (Kilo-Org/kilo-marketplace, 189 stars), Gh Bot Comment (jetstreamapp/jetstream, 125 stars) and Airweave (CraftOS-dev/CraftBot, 392 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commerce B2b Open Code Components Integrate?

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.