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.
MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring site infrastructure.
Install Experience UI Bundle Site Generate
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-site-generate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/experience-ui-bundle-site-generate .claude/skills/experience-ui-bundle-site-generate && rm -rf skills-srcUse ~/.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/
Install the "experience-ui-bundle-site-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generate into .claude/skills/experience-ui-bundle-site-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experience-ui-bundle-site-generate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-site-generate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/experience-ui-bundle-site-generate .agents/skills/experience-ui-bundle-site-generate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "experience-ui-bundle-site-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generate into .agents/skills/experience-ui-bundle-site-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experience-ui-bundle-site-generate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-site-generate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/experience-ui-bundle-site-generate .cursor/skills/experience-ui-bundle-site-generate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "experience-ui-bundle-site-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generate into .cursor/skills/experience-ui-bundle-site-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experience-ui-bundle-site-generate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/experience-ui-bundle-site-generate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-site-generate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/experience-ui-bundle-site-generate .gemini/skills/experience-ui-bundle-site-generate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "experience-ui-bundle-site-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generate into .gemini/skills/experience-ui-bundle-site-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experience-ui-bundle-site-generate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-site-generateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/experience-ui-bundle-site-generate .github/skills/experience-ui-bundle-site-generate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "experience-ui-bundle-site-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generate into .github/skills/experience-ui-bundle-site-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experience-ui-bundle-site-generate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-site-generate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/experience-ui-bundle-site-generate .opencode/skills/experience-ui-bundle-site-generate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "experience-ui-bundle-site-generate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/experience-ui-bundle-site-generate into .opencode/skills/experience-ui-bundle-site-generate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experience-ui-bundle-site-generate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
experience-ui-bundle-site-generate- GitHub stars
- 1.1k
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,134 words
- Files
- 8 (incl. references)
- Skills in repo
- 251
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring site infrastructure.
- Works in 4 steps: Resolve All Required Properties → Create the Project Structure → Populate All Metadata Fields → …
- Configuring a Salesforce Digital Experience Site for hosting a UI bundle
- SKILL.md covers Required Properties, Pre-flight: Target Org Release…, Generation Workflow and Verification Checklist, plus 1 more section
- Calls sf and jq
What it does
Experience UI Bundle Site Generate is an agent skill from forcedotcom/sf-skills. MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring site infrastructure. Use this skill when creating or configuring a Salesforce Digital Experience Site for hosting a UI bundle. Activate when files matching digitalExperiences/, networks/, customSite/, or DigitalExperienceBundle exist and need modification, or when the user wants to publish, host, or configure guest access for their app. Also use this skill to add multi-language, multi-locale…
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/configure-metadata-custom-site.md`, `references/configure-metadata-digital-experience-bundle.md` and `references/configure-metadata-digital-experience-config.md`).
It sits in Sales & Support, covering Internationalization, CRM management and Translation. It works with Salesforce and React. 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
- Configuring a Salesforce Digital Experience Site for hosting a UI bundle
- Wants to publish
- Configure guest access for their app
- Add multi-language
Example prompts
- “/experience-ui-bundle-site-generate”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e5164d9. 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
Shell commands in SKILL.md call:
sfjq
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
Experience UI Bundle Site Generate loads about 3.1k tokens when it runs, and up to ~8.2k if it reads all its reference files. Until then it costs about 201 tokens; SKILL.md has 1,134 words of instructions outside code blocks.
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 e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 1,134 words, ~3,146 tokens.
Download SKILL.mdSave it as
.claude/skills/experience-ui-bundle-site-generate/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- experience-ui-bundle-site-generate
- description
- MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring site infrastructure. Use this skill when creating or configuring a Salesforce Digital Experience Site for hosting a UI bundle. Activate when files matching digitalExperiences/, networks/, customSite/, or DigitalExperienceBundle exist and need modification, or when the user wants to publish, host, or configure guest access for their app. Also use this skill to add multi-language, multi-locale, internationalization, or translation support to such a site by declaring a default locale and additional supported languages via the sfdc_cms__languageSettings content type. DO NOT TRIGGER for LWR (non-React) sites; use experience-lwr-site-generate instead.
- metadata.version
- 1.3
- metadata.domains
- Experience
- metadata.minApiVersion
- 65.0
- metadata.relatedSkills
- experience-lwr-site-generate
Digital Experience Site for React UI Bundles
Create and configure Digital Experience Sites that host React UI bundles on Salesforce. This skill generates the minimum necessary site infrastructure — Network, CustomSite, DigitalExperienceConfig, DigitalExperienceBundle, and the sfdc_cms__site content type — so a React app can be served from Salesforce.
React sites differ from standard LWR sites: they don't need routes, views, theme layouts, or branding sets. The site acts as a thin container (appContainer: true) that delegates rendering to the React UI bundle referenced by appSpace.
Required Properties
Resolve all five properties before generating any metadata. Each has a fallback chain — work through each option in order until a value is found.
| Property | Format | How to Resolve |
|---|---|---|
| siteName | UpperCamelCase (e.g., MyCommunity) | Ask user or derive from context |
| siteUrlPathPrefix | All lowercase (e.g., mycommunity) | User-provided, or convert siteName to all lowercase with alphanumeric characters only |
| appNamespace | String | namespace in sfdx-project.json → sf data query -q "SELECT NamespacePrefix FROM Organization" --target-org ${usernameOrAlias} → default c |
| appDevName | String | UIBundle metadata in the project → sf data query -q "SELECT DeveloperName FROM UIBundle" --target-org ${usernameOrAlias} → default to siteName |
| enableGuestAccess | Boolean | Ask user whether unauthenticated guest users can access site APIs → default false |
The appNamespace and appDevName properties record the intended UIBundle binding for a future follow-up update; they are not substituted into appSpace at initial site creation. appSpace in the sfdc_cms__site content.json is always "" at initial creation — see configure-metadata-digital-experience.md for the reason and the follow-up flow.
Language Properties
The skill always emits sfdc_cms__languageSettings alongside sfdc_cms__site. Resolve defaultLocale for every site (defaults to en_US); resolve languages only when the user requests additional languages beyond the default.
| Property | Format | How to Resolve |
|---|---|---|
| defaultLocale | xx or xx_YY (e.g., en, en_US) | Ask user → default en_US |
| languages | List of {label, locale} | Only when the user asks for multiple languages, locales, internationalization, or translation support: ask for the additional languages the site supports. When not requested, the languageSettings content declares only the resolved defaultLocale as a single-language entry. |
The content-item folder name (languages), title (LanguageContent), and urlName (languagecontent) are fixed Experience Builder auto-defaults — they are not user-authored. See configure-metadata-language-settings.md.
Pre-flight: Target Org Release (Multi-Language Only)
The sfdc_cms__languageSettings content type accepts multi-language declarations only on Salesforce Release 264 (API v68.0 or higher). Sites reduced to a single-locale en_US declaration work on any org and do not need this check.
When the user requests multiple languages, verify the target org's maximum supported API version before writing any metadata. sf api request rest hits /services/data/ on the instance directly and handles authentication at the transport layer, so the org's true ceiling is returned without any access token entering this script's context.
MAX_API=$(sf api request rest "/services/data/" --target-org "${usernameOrAlias}" \
| jq -r '[.[].version | tonumber] | max')
awk -v v="$MAX_API" 'BEGIN{ exit !(v+0 >= 68.0) }' \
|| { echo "ERROR: multi-language site containers require Salesforce Release 264 (API v68.0+). Target org's maximum supported API version is v${MAX_API}. Retarget to a Release 264+ org, or reduce the site to a single-locale (en_US) declaration." >&2; exit 1; }If the check fails, do not write metadata. Report the version mismatch to the user and stop.
Generation Workflow
Step 1: Resolve All Required Properties
Determine values for all five required properties and the defaultLocale language property before constructing anything. Use the resolution strategies in the tables above, falling through each option until a value is found. Resolve the languages property only when the user has requested multiple languages — and when they do, run the Pre-flight check above before continuing to Step 2.
Step 2: Create the Project Structure
Use available Salesforce metadata schema and field context for Network, CustomSite, DigitalExperienceConfig, and DigitalExperienceBundle to ensure each file uses valid structure.
Create any files and directories that don't already exist, using these paths:
| Metadata Type | Path |
|---|---|
| Network | networks/{siteName}.network-meta.xml |
| CustomSite | sites/{siteName}.site-meta.xml |
| DigitalExperienceConfig | digitalExperienceConfigs/{siteName}1.digitalExperienceConfig-meta.xml |
| DigitalExperienceBundle | digitalExperiences/site/{siteName}1/{siteName}1.digitalExperience-meta.xml |
| DigitalExperience (sfdc_cms__site) | digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/* |
| DigitalExperience (sfdc_cms__languageSettings) | digitalExperiences/site/{siteName}1/sfdc_cms__languageSettings/languages/* |
Each DigitalExperience content-type directory contains only _meta.json and content.json. Both sfdc_cms__site and sfdc_cms__languageSettings are always required inside the bundle. The sfdc_cms__languageSettings default declares only the resolved defaultLocale (e.g. en_US); it is extended with additional languages when the user requests multi-language support. No other content types are permitted.
Step 3: Populate All Metadata Fields
Use the default templates in the docs below. Values in {braces} are resolved property references — substitute them with the actual values from Step 1.
| Metadata Type | Template Reference |
|---|---|
| Network | configure-metadata-network.md |
| CustomSite | configure-metadata-custom-site.md |
| DigitalExperienceConfig | configure-metadata-digital-experience-config.md |
| DigitalExperienceBundle | configure-metadata-digital-experience-bundle.md |
| DigitalExperience (sfdc_cms__site) | configure-metadata-digital-experience.md |
| DigitalExperience (sfdc_cms__languageSettings) | configure-metadata-language-settings.md |
For URL updates, see update-site-urls.md.
Show full SKILL.md (464 more words)Show less
Execution Note for Step 3: Load and use the docs
- Agents MUST read the full contents of each references/*.md file referenced in Step 3 before attempting to populate metadata fields.
- Use your platform's file-read tool (for example,
read_file) to load these files in full, then perform placeholder substitution for values in{braces}using the resolved properties from Step 1. - Files to load:
references/configure-metadata-network.mdreferences/configure-metadata-custom-site.mdreferences/configure-metadata-digital-experience-config.mdreferences/configure-metadata-digital-experience-bundle.mdreferences/configure-metadata-digital-experience.mdreferences/configure-metadata-language-settings.md
- Read entire file contents, replace placeholders (e.g.
{siteName}) with the resolved values, then use the expanded templates to populate the metadata XML/JSON content.
Step 4: Do Not Modify Non-Templated Properties
Do not modify any default property values for Network, CustomSite, DigitalExperience, DigitalExperienceConfig, or DigitalExperienceBundle metadata that are not expressed as variables wrapped in {braces}.
Verification Checklist
Before deploying, confirm:
- All five required properties are resolved, and
defaultLocaleis resolved (defaulting toen_USwhen the user does not specify one) - All metadata directories and files exist per the project structure
- All metadata fields match the Step 3 templates with
{braces}substituted only; no other default property values were added or changed -
appSpaceinsfdc_cms__sitecontent.jsonis the empty string""(initial site creation never bindsappSpace; that is a separate follow-up update after the UIBundle is deployed to the target org) - The
sfdc_cms__languageSettings/languages/files exist. The language declaration satisfies every platform rule below:-
defaultLocalematches thelocaleof one declared language, which is active - every
localeis Salesforce-supported, every language isisActive: true, eachlocale+labelcombination is unique, and the number of declared languages does not exceed the platform maximum - See configure-metadata-language-settings.md for the full rule catalog. Single-language default declarations satisfy every rule trivially.
-
- Deployment validates successfully (the
DigitalExperiencetype already coverssfdc_cms__languageSettings— no change to the--metadatalist is needed):
sf project deploy validate --metadata Network CustomSite DigitalExperienceConfig DigitalExperienceBundle DigitalExperience --target-org ${usernameOrAlias}Common Workflows
Updating Experience Site URLs
Use when user wants to update or change site URLs (urlPathPrefix).
Steps:
- Read update-site-urls.md to understand the three-component architecture and URL update workflow
- Follow the step-by-step workflow in the doc to update URLs consistently across all three components (DigitalExperienceConfig, Network, CustomSite)
Configuring Multi-Language Support
Use when user wants the site to support multiple languages, locales, internationalization, or translation — beyond the default-locale-only declaration that every site already receives.
Steps:
- Collect the additional languages the site should support and which locale is the default (resolve the
defaultLocaleandlanguagesproperties above) - Run the Pre-flight: Target Org Release check — abort if the org is below Release 264 (API v68+)
- Read configure-metadata-language-settings.md for the templates, field reference, and platform validation rules
- Extend the
sfdc_cms__languageSettings/languages/content.json(which already exists with the default locale) to include the additional language entries, then re-run deploy validation
Note: This is authoring-only — declared locales deploy cleanly, but locale-in-path routing does not resolve at request time yet. Do not translate the UI bundle content itself; this only declares the site's supported languages.
© 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 7 other files (references) in skills/experience-ui-bundle-site-generate of forcedotcom/sf-skills.
- SKILL.md
- references/configure-metadata-custom-site.md
- references/configure-metadata-digital-experience-bundle.md
- references/configure-metadata-digital-experience-config.md
- references/configure-metadata-digital-experience.md
- references/configure-metadata-language-settings.md
- references/configure-metadata-network.md
- references/update-site-urls.md
Open the folder on GitHubat commit e5164d9
Compare with similar skills
Experience UI Bundle Site Generate 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Experience UI Bundle Site Generate this skillforcedotcom/sf-skills | 1.1k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Gh Bot Commentjetstreamapp/jetstream | 125 | — | ~616 | Automated safety check: Pass | Custom licence | |
| Sf ApexJaganpro/sf-skills | 424 | — | ~2k | Automated safety check: Pass | MIT | |
| Sf DebugJaganpro/sf-skills | 424 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Churn Riskindranilbanerjee/digital-marketing-pro | 855 | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Lead Importindranilbanerjee/digital-marketing-pro | 855 | 1 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Sf Apex
Jaganpro/sf-skills
Generates and reviews Salesforce Apex code with 150-point scoring.
Sf Debug
Jaganpro/sf-skills
Salesforce debug log analysis and troubleshooting with 100-point scoring.
Churn Risk
indranilbanerjee/digital-marketing-pro
Score customer segments for churn risk from behavioral signals — email engagement decline, purchase recency, usage drops, support sentiment — producing a 0-100 risk scorecard with four tiers…
Lead Import
indranilbanerjee/digital-marketing-pro
Import leads into Salesforce, HubSpot, Zoho, or Pipedrive with validation, deduplication against existing CRM records, lead scoring, consent and compliance checks, and source attribution — then push…
Pipeline Update
indranilbanerjee/digital-marketing-pro
Update CRM deals — move stages, change values and close dates, attach notes and activities, create follow-up tasks — with validation against pipeline rules, a before-and-after comparison, and…
More from forcedotcom/sf-skills
All 251 skills in this repoAgentforce Architecture Analyze
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Design Systems Slds Apply
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
Experience Lwc Generate
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Related
Works with
Categories
Questions about Experience UI Bundle Site Generate
What does Experience UI Bundle Site Generate do?
MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring site infrastructure. Experience UI Bundle Site Generate is an agent skill from forcedotcom/sf-skills. MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring site infrastructure.
When should I use Experience UI Bundle Site Generate?
Experience UI Bundle Site Generate fits situations like: configuring a Salesforce Digital Experience Site for hosting a UI bundle; wants to publish; configure guest access for their app; add multi-language.
How do I install Experience UI Bundle Site Generate in Claude Code?
Run `npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a claude-code`. Or copy the skill folder (skills/experience-ui-bundle-site-generate in forcedotcom/sf-skills) into .claude/skills/experience-ui-bundle-site-generate in your project. Claude Code loads it when a task matches its description.
How do I install Experience UI Bundle Site Generate in Codex?
Run `npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-site-generate -a codex`. Or copy the skill folder (skills/experience-ui-bundle-site-generate in forcedotcom/sf-skills) into .agents/skills/experience-ui-bundle-site-generate in your project. Codex loads it when a task matches its description.
Can I use Experience UI Bundle Site Generate 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 experience-ui-bundle-site-generate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/experience-ui-bundle-site-generate, .gemini/skills/experience-ui-bundle-site-generate, .github/skills/experience-ui-bundle-site-generate and .opencode/skills/experience-ui-bundle-site-generate in your project.
What does Experience UI Bundle Site Generate need to run?
Going by SKILL.md and its folder, Experience UI Bundle Site Generate needs the command-line tools its instructions call (sf and jq).
Does Experience UI Bundle Site Generate 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 Experience UI Bundle Site Generate 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 Experience UI Bundle Site Generate use?
Experience UI Bundle Site Generate 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 Experience UI Bundle Site Generate use?
About 3.1k tokens (SKILL.md is roughly 13k 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 5.1k tokens, read only when the agent opens those files.
What are the alternatives to Experience UI Bundle Site Generate?
Skills that share tags, products or a category with Experience UI Bundle Site Generate: Gh Bot Comment (jetstreamapp/jetstream, 125 stars), Sf Apex (Jaganpro/sf-skills, 424 stars), Sf Debug (Jaganpro/sf-skills, 424 stars) and Churn Risk (indranilbanerjee/digital-marketing-pro, 855 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Experience UI Bundle Site Generate?
forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 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.