/experience-content-media-search
Searches for and retrieves existing visual media (images, logos, icons, photos, graphics, banners, thumbnails, hero images, backgrounds) from sources such as Salesforce CMS, Data 360 or any other source. Use this skill ANY TIME a user request involves finding, searching,
$ npx -y skills add forcedotcom/sf-skills --skill experience-content-media-search --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/experience-content-media-search
Context preview
The summary Claude sees to decide when to auto-load this skill.
Searches for and retrieves existing visual media (images, logos, icons, photos, graphics, banners, thumbnails, hero images, backgrounds) from sources such as Salesforce CMS, Data 360 or any other source. Use this skill ANY TIME a user request involves finding, searching,
SKILL.md
experience-content-media-search.SKILL.mdname: experience-content-media-search
description: "Searches for and retrieves existing visual media (images, logos, icons, photos, graphics, banners, thumbnails, hero images, backgrounds) from sources such as Salesforce CMS, Data 360 or any other source. Use this skill ANY TIME a user request involves finding, searching, getting, fetching, retrieving, grab, looking up, locating media. NEVER call search_media_cms_channels, search_electronic_media tools directly — always go through this skill first. This skill must be activated before any tool is used for media search or retrieval, without exception. Takes PRIORITY and activates FIRST when ANY media search/retrieval is mentioned, regardless of what else happens with the media afterward. Triggers for requests like \"search for logo\", \"find hero image\", \"get company logo\", \"locate icons\", \"fetch background image\", \"retrieve product photos\". Handles the search and source selection workflow. Does not apply when the request is about brand search, to generate NEW images with AI, or edit existing images."
compatibility: "Requires search_media_cms_channels and/or search_electronic_media MCP tools"
metadata:
version: "1.0"
Media Search
Universal routing skill for searching and retrieving existing images and media.
Scope
**This skill is for SEARCHING FOR existing media, not CREATING new media.**
**Use this skill when the user wants to:**
- Search for images in Salesforce CMS, Data Cloud
- Find existing visual assets to use in their app
- Retrieve media from connected sources
- Browse available images for their project
- Locate specific photos or graphics
**DO NOT use this skill when the user wants to:**
- Generate new images with AI (use image generation tools)
- Create graphics or designs from scratch
- Edit or modify existing images
- Build custom visuals or diagrams
Before You Search
**CRITICAL: This is a routing skill, not a direct search skill.**
When a user requests to find an image:
**Your first action MUST use the ask_followup_question tool to present search sources.**
1. **Use ask_followup_question** to present available search sources as options 2. **Receive the user's selection** from the tool response 3. **Then** call the appropriate search tool based on their choice
**Example of what NOT to do:**
- ❌ Calling ANY tool before the user picks a source (MCP tools, file reads, descriptor checks, etc.)
- ❌ "Checking which MCP tools are available" — do not probe or discover tools via tool calls
- ❌ Immediately calling `search_electronic_media` or `search_media_cms_channels`
- ❌ Reading MCP tool descriptors or schemas to see what's available
- ❌ Deciding which search source to use without asking
**Example of what TO do:**
- ✅ Respond with ONLY text — a numbered list of search sources
- ✅ Ask: "Which option would you like to use?"
- ✅ Wait for user to reply with their choice
- ✅ Then (and only then) call the tool they selected
**Your first response when this skill triggers MUST be a text-only message presenting search sources. No tool calls. No exceptions.**
Workflow Overview
**The user MUST choose the search source. You CANNOT skip this step.**
Copy this checklist and track your progress:
Media Search Progress:
- [ ] Step 1: Check your own tool list for available search tools (no tool calls — just inspect what's in your context)
- [ ] Step 2: Present only the available options to the user as a numbered list (plain text, no tool calls)
- [ ] Step 3: Wait for the user to reply with their selection
- [ ] Step 4: Execute the selected search method (this is the first tool call)
- [ ] Step 5: Present all results to user for selection
- [ ] Step 6: Apply selected image to code
If you call any tool before step 4, you are not following this skill correctly.
Presenting Search Sources (First Response)
**DO NOT call any tool, read any MCP descriptor, or make any external request to determine available tools.**
Your tools are already loaded into your context. Look at the tool names you already have access to — this is introspection, not a tool call.
**Step 1: Check your own tool list (no tool calls)**
Look at the tools already in your context and check for these names:
- `search_media_cms_channels` → If present, include **"Search using keywords"**
- `search_electronic_media` → If present, include **"Search using Data 360 hybrid search"**
- Always include **"Other"** as the last option
**Step 2: Build your response**
Include ONLY the sources whose tools you actually have. Number them sequentially.
I can help you find that image. Where would you like to search?
[NUMBER]. [SEARCH SOURCE NAME] — [Brief description]
...
[NUMBER]. Other — Provide your own URL or path
Which option would you like to use?
**Step 3: Stop and wait**
After presenting the list, STOP. Do not call any tool. Do not proceed. Wait for the user to reply with their choice.
Examples
**Both tools available:**
I can help you find that image. Where would you like to search?
1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs
2. Search using keywords — Search Salesforce CMS by keywords and taxonomies
3. Other — Provide your own URL or path
Which option would you like to use?
**Only `search_media_cms_channels` available:**
I can help you find that image. Where would you like to search?
1. Search using keywords — Search Salesforce CMS by keywords and taxonomies
2. Other — Provide your own URL or path
Which option would you like to use?
**Only `search_electronic_media` available:**
I can help you find that image. Where would you like to search?
1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs
2. Other — Provide your own URL or path
Which option would you like to use?
**Neither tool available:**
No automated media search sources are currently configured. Please provide a direct URL o
Read more
name: experience-content-media-search description: "Searches for and retrieves existing visual media (images, logos, icons, photos, graphics, banners, thumbnails, hero images, backgrounds) from sources such as Salesforce CMS, Data 360 or any other source. Use this skill ANY TIME a user request involves finding, searching, getting, fetching, retrieving, grab, looking up, locating media. NEVER call search_media_cms_channels, search_electronic_media tools directly — always go through this skill first. This skill must be activated before any tool is used for media search or retrieval, without exception. Takes PRIORITY and activates FIRST when ANY media search/retrieval is mentioned, regardless of what else happens with the media afterward. Triggers for requests like \"search for logo\", \"find hero image\", \"get company logo\", \"locate icons\", \"fetch background image\", \"retrieve product photos\". Handles the search and source selection workflow. Does not apply when the request is about brand search, to generate NEW images with AI, or edit existing images." compatibility: "Requires search_media_cms_channels and/or search_electronic_media MCP tools" metadata: version: "1.0"
Media Search
Universal routing skill for searching and retrieving existing images and media.
Scope
**This skill is for SEARCHING FOR existing media, not CREATING new media.**
**Use this skill when the user wants to:**
- Search for images in Salesforce CMS, Data Cloud
- Find existing visual assets to use in their app
- Retrieve media from connected sources
- Browse available images for their project
- Locate specific photos or graphics
**DO NOT use this skill when the user wants to:**
- Generate new images with AI (use image generation tools)
- Create graphics or designs from scratch
- Edit or modify existing images
- Build custom visuals or diagrams
Before You Search
**CRITICAL: This is a routing skill, not a direct search skill.**
When a user requests to find an image:
**Your first action MUST use the ask_followup_question tool to present search sources.**
1. **Use ask_followup_question** to present available search sources as options 2. **Receive the user's selection** from the tool response 3. **Then** call the appropriate search tool based on their choice
**Example of what NOT to do:**
- ❌ Calling ANY tool before the user picks a source (MCP tools, file reads, descriptor checks, etc.)
- ❌ "Checking which MCP tools are available" — do not probe or discover tools via tool calls
- ❌ Immediately calling `search_electronic_media` or `search_media_cms_channels`
- ❌ Reading MCP tool descriptors or schemas to see what's available
- ❌ Deciding which search source to use without asking
**Example of what TO do:**
- ✅ Respond with ONLY text — a numbered list of search sources
- ✅ Ask: "Which option would you like to use?"
- ✅ Wait for user to reply with their choice
- ✅ Then (and only then) call the tool they selected
**Your first response when this skill triggers MUST be a text-only message presenting search sources. No tool calls. No exceptions.**
Workflow Overview
**The user MUST choose the search source. You CANNOT skip this step.**
Copy this checklist and track your progress:
Media Search Progress: - [ ] Step 1: Check your own tool list for available search tools (no tool calls — just inspect what's in your context) - [ ] Step 2: Present only the available options to the user as a numbered list (plain text, no tool calls) - [ ] Step 3: Wait for the user to reply with their selection - [ ] Step 4: Execute the selected search method (this is the first tool call) - [ ] Step 5: Present all results to user for selection - [ ] Step 6: Apply selected image to code
If you call any tool before step 4, you are not following this skill correctly.
Presenting Search Sources (First Response)
**DO NOT call any tool, read any MCP descriptor, or make any external request to determine available tools.**
Your tools are already loaded into your context. Look at the tool names you already have access to — this is introspection, not a tool call.
**Step 1: Check your own tool list (no tool calls)**
Look at the tools already in your context and check for these names:
- `search_media_cms_channels` → If present, include **"Search using keywords"**
- `search_electronic_media` → If present, include **"Search using Data 360 hybrid search"**
- Always include **"Other"** as the last option
**Step 2: Build your response**
Include ONLY the sources whose tools you actually have. Number them sequentially.
I can help you find that image. Where would you like to search? [NUMBER]. [SEARCH SOURCE NAME] — [Brief description] ... [NUMBER]. Other — Provide your own URL or path Which option would you like to use?
**Step 3: Stop and wait**
After presenting the list, STOP. Do not call any tool. Do not proceed. Wait for the user to reply with their choice.
Examples
**Both tools available:**
I can help you find that image. Where would you like to search? 1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs 2. Search using keywords — Search Salesforce CMS by keywords and taxonomies 3. Other — Provide your own URL or path Which option would you like to use?
**Only `search_media_cms_channels` available:**
I can help you find that image. Where would you like to search? 1. Search using keywords — Search Salesforce CMS by keywords and taxonomies 2. Other — Provide your own URL or path Which option would you like to use?
**Only `search_electronic_media` available:**
I can help you find that image. Where would you like to search? 1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs 2. Other — Provide your own URL or path Which option would you like to use?
**Neither tool available:**
No automated media search sources are currently configured. Please provide a direct URL o
This repository provides a curated collection of Salesforce agent skills for building applications.
Repo: forcedotcom/sf-skills
Other skills on sf-skills.
- /agentforce-generate
Build, modify, optimize, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, modifies, optimizes, or asks about .agent files or aiAuthoringBundle metadata; changes agent behavior, responses, or conversation logic; designs agent actions, tools,
Open skill - /agentforce-observe
Analyze production Agentforce agent behavior using session traces and Data Cloud. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs,
Open skill - /agentforce-test
Write, run, and analyze structured test suites for Agentforce agents — functional AND security. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric
Open skill - /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
Open skill - /dx-code-analyzer-configure
Set up, configure, and troubleshoot Salesforce Code Analyzer for any project. Handles installation, prerequisite checks, diagnosing broken setups, creating and editing code-analyzer.yml overrides, engine-specific settings, ignore patterns, severity overrides, and CI/CD pipeline
Open skill - /dx-code-analyzer-custom-rule-create
Create custom Code Analyzer rules for Regex (pattern matching), PMD (XPath/AST for Apex and metadata XML), and ESLint (LWC/JavaScript/TypeScript). Use when users want to enforce coding standards, ban patterns, detect hardcoded values, govern metadata, or add rules not in the
Open skill

