How to install applying-cms-brand
npx skills add https://github.com/forcedotcom/sf-skills --skill applying-cms-brandFull instructions (SKILL.md)
Source of truth, from forcedotcom/sf-skills.
name: applying-cms-brand description: "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 searching-media skill), logo search, or creating new brand definitions." compatibility: "Requires get_brand_instructions and/or search_brands MCP tools" metadata: version: "1.0"
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 searching-media skill)
- Create a new brand from scratch
- Edit brand definitions in CMS
- Generate logos or visual brand assets
Before You Start
CRITICAL: You must retrieve brand instructions BEFORE generating or modifying 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_brands
Process:
- Determine search query — Use the user's description, company name, or a general keyword
- Build the request:
{
"inputs": [{
"searchQuery": "keyword or brand name"
}]
}
- Call
search_brandswith the query - Parse the response — Extract brand results:
managedContentId— Unique ID (use this for extraction in Step 3)managedContentKey— Content key identifiertitle— Brand display namecontentUrl— URL to the brand contenttotalResults— Number of brands found
Presenting Brand Results
If multiple brands found, use ask_followup_question to present options:
I found [N] brands in your CMS. Which one should I apply?
1. [Brand Title 1]
2. [Brand Title 2]
3. [Brand Title 3]
Which brand would you like to use?
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_brands 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
Related skills
More from forcedotcom/sf-skills and the wider catalog.
generating-apex
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.
generating-apex-test
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 generating-apex) or Jest/LWC tests.
generating-lwc-components
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 generating-apex), Aura components, or Visualforce.
generating-flow
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.
querying-soql
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 handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
generating-custom-object
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.