
Media Search
OfficialFreeEfficiently find and retrieve existing visual media assets.
Free · Opens the source repo
What Media Search does
The Media Search skill is designed to streamline the process of locating and retrieving existing visual media assets such as images, logos, icons, and graphics from various sources like Salesforce CMS and Data 360. It acts as a universal routing skill, ensuring that any requests for media search are handled through a structured workflow. This skill is particularly useful for developers and designers who need quick access to pre-existing media for their applications or projects without the need to create new assets from scratch.
When a user requests to find a specific image or media asset, the Media Search skill requires them to choose a source from a predefined list of available search options. This ensures that the search is conducted efficiently and accurately, as the skill does not perform any searches until the user has made a selection. By adhering to this workflow, the skill helps prevent errors and miscommunication, allowing for a more organized approach to media retrieval.
It's important to note that this skill is strictly for searching and retrieving existing media. It does not support generating new images or modifying existing ones. As such, it is best utilized in scenarios where users are looking to source visual content that is already available, rather than creating new graphics or designs. This makes it an essential tool for anyone working within environments that rely on existing media assets, such as marketing teams, app developers, and content creators.
In summary, the Media Search skill provides a systematic approach to finding and retrieving visual media, ensuring that users can efficiently access the assets they need while maintaining a clear and structured workflow.
When to use it
Use this skill whenever you need to find and retrieve existing images or media assets from specified sources.
When not to use it
Avoid using this skill for generating new media or editing existing images, as it is not designed for those tasks.
What you can build with it
Finding Company Logos
Use the Media Search skill to quickly locate and retrieve a company's logo from Salesforce CMS.
Retrieving Background Images
Easily find and fetch suitable background images for your application or project using this skill.
Accessing Icons for UI Design
Utilize the Media Search skill to browse and select icons needed for user interface design.
How to install Media Search
View source1. Install with the skills CLI
npx skills add forcedotcom/sf-skills/experience-content-media-search --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by forcedotcomMedia 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.
- Use ask_followup_question to present available search sources as options
- Receive the user's selection from the tool response
- 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_mediaorsearch_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 or asset library path.
Wait for the user to select before proceeding.
Executing the Selected Search Method
⚠️ ONLY reach this step if the user has explicitly selected an option from your numbered list.
If you haven't shown options yet, go back to the "Presenting Search Sources" section first.
After the user selects an option, execute the corresponding search method below.
Search using keywords
Tool: search_media_cms_channels
Process:
-
Analyze the query — Understand what the user is searching for (subject, attributes, domain)
-
Extract keywords — Concrete nouns that would appear in image metadata
- Use domain-specific synonyms
- Maximum 10 terms
- Examples:
- "luxury apartments" → apartment, villa, penthouse, residence, condo
- "company logo" → logo, emblem, corporate logo
- "bright room" → (empty if no concrete nouns)
-
Extract taxonomies — Descriptive qualities, styles, moods, categories
- Only adjectives and attributes
- Examples:
- "luxury apartment with river view" → Luxury, Premium, Waterfront, Riverside, Panoramic
- "bright spacious room" → Bright, Spacious, Open, Airy, Light
- "car" → (empty if no descriptive terms)
-
Determine locale — Use format
en_US,es_MX,fr_FR(default:en_US) -
Build the JSON payload — Construct this exact structure:
{
"inputs": [{
"searchKeyword": "keyword1 OR keyword2 OR keyword3",
"taxonomyExpression": "{\"OR\": [\"Taxonomy1\", \"Taxonomy2\"]}",
"searchLanguage": "en_US",
"channelIds": "",
"channelType": "PublicUnauthenticated",
"contentTypeFqn": "sfdc_cms__image",
"pageOffset": 0,
"searchLimit": 5
}]
}
Field rules:
searchKeyword: Join keywords withOR(space-OR-space). Use empty string if no keywords.taxonomyExpression: Stringify JSON object{"OR": ["term1", "term2"]}. Use"{}"if no taxonomies.searchLanguage: Locale with underscore (e.g.,en_US)channelIds: Always empty stringchannelType: Always"PublicUnauthenticated"contentTypeFqn: Always"sfdc_cms__image"pageOffset: Start at0, increment bysearchLimitfor paginationsearchLimit: Default5, adjust if user requests more
Examples:
Query: "luxury apartment with river view"
{
"inputs": [{
"searchKeyword": "apartment OR villa OR penthouse OR residence",
"taxonomyExpression": "{\"OR\": [\"Luxury\", \"Premium\", \"Waterfront\", \"Riverside\"]}",
"searchLanguage": "en_US",
"channelIds": "",
"channelType": "PublicUnauthenticated",
"contentTypeFqn": "sfdc_cms__image",
"pageOffset": 0,
"searchLimit": 5
}]
}
Query: "bright spacious room" (no concrete nouns)
{
"inputs": [{
"searchKeyword": "",
"taxonomyExpression": "{\"OR\": [\"Bright\", \"Spacious\", \"Open\", \"Airy\"]}",
"searchLanguage": "en_US",
"channelIds": "",
"channelType": "PublicUnauthenticated",
"contentTypeFqn": "sfdc_cms__image",
"pageOffset": 0,
"searchLimit": 5
}]
}
Query: "car images" (no descriptive terms)
{
"inputs": [{
"searchKeyword": "car OR automobile OR vehicle OR auto",
"taxonomyExpression": "{}",
"searchLanguage": "en_US",
"channelIds": "",
"channelType": "PublicUnauthenticated",
"contentTypeFqn": "sfdc_cms__image",
"pageOffset": 0,
"searchLimit": 5
}]
}
- Call the tool with the exact JSON payload
Search using Data 360 hybrid search
Tool: search_electronic_media
Process:
- Use the user's query as-is — no keyword extraction or transformation needed
- Call
search_electronic_media - Pass the query to the tool's
searchQueryparameter
Example:
- User query: "modern luxury apartment with natural lighting"
- Tool call:
search_electronic_media(searchQuery="modern luxury apartment with natural lighting")
Other (User-Provided URL)
Ask the user to provide:
- Direct URL to the image
- Asset library path
- Specific system/location to check
Presenting Search Results
Your action MUST use the ask_followup_question tool to present search results as options.
- Parse the tool response — Extract all image results (title and source)
- Use
ask_followup_questionto present ALL results as selectable options. Show the image title only — do not display the URL. - Receive the user's selection from the tool response
- Then apply the selected image
I found 4 images. Which one would you like to use?
1. Luxury Apartment Exterior
Source: Salesforce CMS
2. Modern High-Rise Building
Source: Salesforce CMS
3. Waterfront Residence
Source: Salesforce CMS
4. Premium Condominium
Source: Salesforce CMS
Never auto-select an image. Always wait for user choice.
Applying the Selected Image
After the user chooses:
- Confirm the selection with image name and URL
- Use the complete URL returned by the tool, including all query parameters. CMS and DAM URLs rely on query parameters for authentication, resizing, and CDN routing — dropping them breaks the image. For example, a URL like
https://cms.example.com/media/img.jpg?oid=00D&refid=0EM&v=2must be used in full. - Apply the URL to the user's code/component
- Show what was changed (file path and line number)
Error Handling
| Error | Response |
|---|---|
| Tool unavailable | "The [source name] tool is unavailable. Would you like to try a different source?" |
| Tool returns error | Show error message, offer retry with different terms or alternative source |
| No results found | "No results found. Try broader keywords, removing descriptive terms, or a different source." |
| Invalid user selection | Re-display options and ask again |
Never silently fail. Always inform the user and offer alternatives.
Search Behavior Notes
Search using keywords:
- Both keyword and taxonomy → results match keyword OR (keyword + taxonomy)
- Empty keyword → search by taxonomy only
- Empty taxonomy → search by keyword only
- Use
pageOffsetfor pagination (increment bysearchLimit)
Search using Data 360 hybrid search:
- Handles natural language queries
- Semantic similarity matching
- Searches across multiple connected systems
Key Principles
- First response is always text-only — Present search sources without calling any tool
- Only show configured sources — Check your own tool list (introspection, not tool calls) and only present sources whose tools you have
- Wait for user selection — Never auto-select a source or image
- Show all results — Let the user choose the best match
- Confirm before applying — Verify the selection before modifying code
- Handle errors gracefully — Provide clear feedback and alternatives
Frequently asked questions about Media Search
Similar skills
VSS Search Archive
Efficiently search archived video content with VSS.
Find Skills
Discover and install agent skills effortlessly.
Shop CLI
Streamline your shopping experience with command-line access.
Maps
Location intelligence using open data sources.
SearXNG Search
Meta-search across 70+ engines without an API key.
DuckDuckGo Search
Perform free web searches without an API key.
