Applying CMS Brand

experience-cms-brand-apply

Extracts, retrieves, and applies CMS brand guidelines (voice, tone, style, colors, typography) to generated content. Use this skill ANY TIME a user request involves branding, brand voice, brand tone, brand guidelines, brand identity, brand styling, or applying a brand to content. Triggers for requests like "apply my brand", "use our brand voice", "match our brand guidelines", "find my brand", "search for brand", "get brand instructions", "apply brand tone". Handles the full workflow: searching for brands in Salesforce CMS, extracting brand instructions, and applying brand voice/tone/guidelines to generated content. Does not apply to media/image search (use experience-content-media-search skill), logo search, or creating new brand definitions.

forcedotcom/sf-skills·4.9Kinstalls1.1Kstars

SKILL.md

Full skill instructions

Applying CMS Brand

Universal skill for searching, extracting, and applying CMS brand guidelines to generated content.

Scope

This skill is for APPLYING existing brand guidelines from Salesforce CMS to content you generate.

Use this skill when the user wants to:

Apply their brand voice/tone to generated content
Find and use brand guidelines stored in Salesforce CMS
Search for an existing brand in their org
Get brand instructions for content generation
Ensure generated content matches their brand identity
Apply brand styling, tone, or voice to a page, component, or app

DO NOT use this skill when the user wants to:

Search for images or media (use experience-search-coordinate skill)
Create a new brand from scratch (use experience-cms-brand-create skill)
Edit brand definitions in CMS
Generate logos or visual brand assets

Before You Start

CRITICAL: You must retrieve brand instructions BEFORE applying any brand.

When a user requests branded content:

Search for available brands (if brand is not already identified)
Extract brand instructions for the selected brand
Apply brand guidelines to all content you generate

Never generate content first and retrofit branding later. Brand instructions must inform content generation from the start.

Workflow Overview

Copy this checklist and track your progress:

CMS Branding Progress:
- [ ] Step 1: Determine if brand is already identified or needs search
- [ ] Step 2: Search for brands (if needed) and present options to user
- [ ] Step 3: Extract brand instructions for the selected brand

Step 1: Determine Brand Context

Check if the user has already specified which brand to use:

Brand is known (user named it, or only one brand exists):

Skip to Step 3 (Extract Brand Instructions)

Brand is unknown (user says "apply my brand" without specifying which):

Proceed to Step 2 (Search for Brands)

Step 2: Search for Brands

Tool: search_media_cms_channels

Brands are stored as CMS content of type sfdc_cms__brand. Search for them by querying the CMS channels with the brand content type.

Note: Brand content search (contentTypeFqn=sfdc_cms__brand) is explicitly excluded from the experience-search-coordinate skill's scope. Calling search_media_cms_channels directly here is correct and intentional — do not route brand search through experience-search-coordinate.

Process:

Determine search query — Use the user's keyword. Brand search matches on brand title and description.
Build the request with the fixed brand-search input contract:

{
  "inputs": [{
    "searchKeyword": "keyword",
    "searchLanguage": "<detected_language>",
    "channelType": "PublicUnauthenticated",
    "contentTypeFqn": "sfdc_cms__brand",
    "pageOffset": 0,
    "searchLimit": 25
  }]
}

Field rules:

searchKeyword — the user's keyword input
searchLanguage — auto-detect from the user's input; if unsure, use en_US
channelType — always PublicUnauthenticated (brand content is delivered via the public CMS channel; authenticated-channel brand search is not supported by this tool)
contentTypeFqn — always sfdc_cms__brand
pageOffset — 0
searchLimit — 25

Call search_media_cms_channels with the request
Parse the response — A brand result has an ID starting with 9Ps. Extract:
- managedContentId — Unique ID (use this for extraction in Step 3)
- managedContentKey — Content key identifier
- title — Brand display name
- contentUrl — URL to the brand content, found under managedContentChannelDeliveryDetails[0].contentUrl
- pageNumber, pageSize, totalResults — pagination summary

Presenting Brand Results

If brands found, first show a summary line, then use ask_followup_question to present options:

Showing [N] of [totalResults] total results (page [pageNumber], page size [pageSize]).

Which brand should I apply?

1. [Brand Title 1]
2. [Brand Title 2]
3. [Brand Title 3]

Which brand would you like to use?

When the user replies with their selection, do NOT perform another search — proceed immediately to Step 3.

If one brand found, confirm with the user:

I found the brand "[Brand Title]". Should I apply this brand's guidelines to the content?

If no brands found:

No brands found in Salesforce CMS. To use branding:
1. Create a brand in Salesforce CMS (Content Type: sfdc_cms__brand)
2. Provide brand guidelines directly in this conversation

Would you like to proceed without CMS branding, or provide guidelines manually?

Never auto-select a brand without confirmation. Always wait for user choice.

Step 3: Extract Brand Instructions

Tool: get_brand_instructions

Process:

Call get_brand_instructions — This retrieves the branding extraction prompt template
Parse the response:
- promptBody — Contains the full brand instruction prompt with extraction and application rules
Follow the instructions in promptBody — The prompt template contains specific guidance on:
- How to extract brand properties from the brand content
- Brand voice and tone rules
- Typography and color guidelines
- Content formatting rules
- Guardrails and restrictions

What Brand Instructions Contain

The extracted brand instructions typically include:

Property	Description
Brand Voice	How the brand speaks (e.g., professional, friendly, authoritative)
Brand Tone	Emotional quality of communication (e.g., confident, warm, empathetic)
Key Messages	Core messaging pillars and value propositions
Content Rules	Dos and don'ts for content generation
Style Guidelines	Typography, color, spacing preferences
Guardrails	Hard restrictions on language, topics, or claims

Error Handling

Error	Response
`search_media_cms_channels` unavailable	"Brand search is unavailable. Please provide your brand name or guidelines directly."
`get_brand_instructions` unavailable	"Cannot retrieve brand instructions. Please share your brand guidelines in this conversation and I'll apply them manually."
Org lacks Vibes branding	"CMS branding is not enabled for this org. Contact your admin to enable the Agentforce Vibes branding feature."
Permission denied	"You don't have permission to access CMS brands. Ensure you have Managed Content Authoring permission."
Brand extraction returns empty	"The brand exists but has no configured guidelines. Please add brand properties in CMS or provide guidelines here."

Never silently fail. Always inform the user and offer alternatives.

Key Principles

Brand first, content second — Always extract brand instructions before generating content
Never assume brand guidelines — Only apply what was explicitly retrieved from CMS
Respect guardrails absolutely — Brand content rules are hard constraints, not suggestions
Confirm brand selection — Never auto-select a brand without user confirmation
Show your work — Tell the user which guidelines you applied and how
Graceful degradation — If tools are unavailable, ask for manual guidelines rather than proceeding without branding

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/forcedotcom/sf-skills --skill experience-cms-brand-apply

View on GitHub

experience-cms-brand-apply

platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill for requests involving SObject CRUD, mapping collections, fetching related records, scheduled jobs, batch jobs, trigger design, @AuraEnabled controllers, @RestResource endpoints, custom REST APIs, or code review of existing Apex.
6.7K installs
platform-apex-test-generate
Generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking strategies, assertion best practices, and disciplined test-fix loops. Use this skill when creating new Apex test classes, improving test coverage, debugging and fixing failing Apex tests, running test execution and coverage analysis, or implementing testing patterns for triggers, services, controllers, batch jobs, queueables, and integrations. Triggers on *Test.cls, *_Test.cls files, sf apex run test workflows, coverage reports, test-fix loops. Do NOT trigger for production Apex code (use platform-apex-generate) or Jest/LWC tests.
6.6K installs
platform-apex-test-run
Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with *Test.cls / *_Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate).
6.5K installs
platform-docs-get
Official Salesforce documentation retrieval skill. Use when you need authoritative Salesforce docs from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com, or lightningdesignsystem.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching. Use to ground answers in official Salesforce sources instead of third-party blogs or summaries. TRIGGER when: user asks for official Salesforce documentation, Apex or API reference, LWC docs, Agentforce docs, setup or help articles, or any doc from a Salesforce-owned domain. DO NOT TRIGGER when: user is asking for a code change, deployment task, or anything not requiring documentation retrieval — use the appropriate sf-* skill instead.
6.4K installs

More skills from forcedotcom

forcedotcom/sf-skills

platform-apex-logs-debug

Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).

1.1K 6.4K

View

forcedotcom/sf-skills

platform-soql-query

SOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use platform-data-manage), Apex DML logic (use platform-apex-generate), or report/dashboard queries.

1.1K 6.3K

View

forcedotcom/sf-skills

platform-metadata-deploy

Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use platform-apex-generate), building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate or platform-custom-field-generate), or querying org data (use platform-data-manage).

1.1K 6.3K

View

forcedotcom/sf-skills

platform-metadata-retrieve

ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project using the sf project retrieve start command. Supports multiple retrieval modes: retrieve all remote changes, retrieve by source directory, retrieve by metadata type with wildcards, retrieve by manifest (package.xml), or retrieve by package name. Use when the user asks to retrieve, pull, sync, or download metadata, Apex classes, custom objects, or org changes. Supports source format (default) or metadata format (ZIP). DO NOT TRIGGER for deploying metadata (use platform-metadata-deploy skill), listing metadata, or generating package.xml. NEVER use MCP tools - always use this skill and the Bash tool with sf project retrieve start.

1.1K 6.3K

View

forcedotcom/sf-skills

platform-custom-field-generate

Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping/limiting picklist values for a specific record type. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, formula issues, or a record type that won't deploy without a business process. Use this skill for custom field metadata work, field generation, and field troubleshooting. DO NOT TRIGGER for creating or customizing the value set itself — defining a new GlobalValueSet, or modifying a StandardValueSet catalog like Industry or Lead Source — use platform-value-set-generate instead; this skill covers the field that references a value set, not the value set definition.

1.1K 6.2K

View

forcedotcom/sf-skills

platform-permission-set-generate

Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets.

1.1K 6.1K

View

forcedotcom/sf-skills

dx-code-analyzer-run

Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', 'show security violations', 'what is this rule', 'explain ApexCRUDViolation', 'filter results', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). Use this skill for scanning, exploring results, and listing rules. DO NOT TRIGGER when: user asks only about installation/configuration (use dx-code-analyzer-configure), or wants to create a custom rule (use dx-code-analyzer-custom-rule-create).

1.1K 6.1K

View

forcedotcom/sf-skills

automation-flow-generate

Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation.

1.1K 6K

View

forcedotcom/sf-skills

platform-custom-object-generate

Use this skill when users need to create, generate, or validate Salesforce Custom Object metadata. Trigger when users mention custom objects, creating objects, object metadata, .object files, sharing models, name fields, or validation rules on objects. Also use when users say things like "create a custom object", "generate object metadata", "set up an object for...", or when they're troubleshooting object deployment errors especially around sharing models and Master-Detail relationships. Always use this skill for any custom object metadata work, including enriching and keeping the object's description current whenever its fields or validation rules change. Do NOT use this skill for non-Custom-Object metadata (Apex, Flows, LWC, Permission Sets, Custom Metadata Types) or for standard Salesforce objects.

1.1K 6K

View

forcedotcom/sf-skills

platform-data-manage

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy).

1.1K 5.9K

View

forcedotcom/sf-skills

experience-lwc-generate

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use platform-apex-generate), Aura components, or Visualforce.

1.1K 5.9K

View

forcedotcom/sf-skills

design-systems-slds-apply

Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include "build a modal", "create a form", "data table", "SLDS styling", "style with hooks", "add an icon".

1.1K 5.8K

View