Searching Media
Route every Salesforce media lookup through one skill before calling CMS or electronic media search MCP tools.
Overview
Searching Media is an agent skill for the Build phase that searches and retrieves existing Salesforce CMS and Data 360 visual assets before any media MCP tool runs.
Install
npx skills add https://github.com/forcedotcom/sf-skills --skill searching-mediaWhat is this skill?
- Mandatory router: never call search_media_cms_channels or search_electronic_media without this skill first
- Triggers on find, fetch, retrieve, locate, or grab existing images and logos
- Scopes to existing media search—not AI image generation or brand-name-only search
- Source selection workflow across Salesforce CMS and electronic media
- Declares compatibility with search_media_cms_channels and/or search_electronic_media MCP tools
- Skill metadata version 1.0
- Two MCP tool families gated: search_media_cms_channels and search_electronic_media
Adoption & trust: 645 installs on skills.sh; 513 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Agents call Salesforce media tools directly and miss the required search-and-source-selection workflow for existing images and logos.
Who is it for?
Salesforce builders wiring agents to reuse CMS and Data Cloud visuals in experiences, emails, or composable apps.
Skip if: Creating new generative images, editing existing creatives, or brand lookups with no asset retrieval.
When should I use this skill?
ANY user request involves finding, searching, getting, fetching, retrieving, locating, or grabbing existing visual media from Salesforce or related sources—activate FIRST; do not use for AI image generation or brand-only
What do I get? / Deliverables
Media requests flow through a single skill that selects the right Salesforce source and then invokes the approved MCP search tools.
- Selected media source and retrieved asset references from CMS or electronic media search
- Completed search workflow without direct unscoped MCP calls
Recommended Skills
Journey fit
Salesforce builders integrate existing brand assets during product build—not when ideating unrelated apps. Integrations covers MCP-gated search across Salesforce CMS and Data 360 (Data Cloud) sources.
How it compares
Orchestration skill for existing-asset search—not an image generator or DAM replacement outside Salesforce.
Common Questions / FAQ
Who is searching-media for?
Developers and admins using agent + MCP stacks on Salesforce who need logos, icons, photos, or banners from CMS or Data 360.
When should I use searching-media?
Use it whenever a user asks to search, find, get, fetch, retrieve, locate, or grab existing media—before any search_media_cms_channels or search_electronic_media tool call—in Build integrations work.
Is searching-media safe to install?
Review the Security Audits panel on this Prism page and validate MCP tool access, org permissions, and content licensing before production use.
SKILL.md
READMESKILL.md - Searching Media
# 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