Searching Media
Route any request to find existing CMS or Data 360 media through the mandated search workflow before calling Salesforce MCP tools.
Overview
Searching Media is an agent skill for the Build phase that routes existing image and media lookup through a required workflow before Salesforce CMS or Data 360 MCP search tools run.
Install
npx skills add https://github.com/forcedotcom/afv-library --skill searching-mediaWhat is this skill?
- Mandatory first step before search_media_cms_channels or search_electronic_media MCP calls
- Covers logos, icons, hero images, banners, thumbnails, and backgrounds from Salesforce CMS and Data 360
- Activates on find, get, fetch, retrieve, locate, and grab media phrasing
- Explicitly excludes AI image generation, image editing, and brand-only search flows
- Documents source selection workflow for reusing existing visual assets
- Skill metadata version 1.0
Adoption & trust: 1.3k installs on skills.sh; 513 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps calling Salesforce media MCP tools directly and misses the required search-and-source-selection workflow for existing assets.
Who is it for?
Solo builders on Salesforce stacks who need dependable retrieval of logos, heroes, and icons from org-connected content sources.
Skip if: Generating new AI images, editing existing bitmaps, or pure brand-name lookup without asset retrieval.
When should I use this skill?
Any user request to search, find, get, fetch, retrieve, locate, or grab existing images or media from Salesforce CMS, Data 360, or similar sources.
What do I get? / Deliverables
Media requests resolve through the skill first, then compatible MCP searches return CMS or electronic media matches ready to drop into your UI work.
- Selected existing media assets from configured sources
- Completed search-and-source-selection workflow log suitable for UI placement
Recommended Skills
Journey fit
Media retrieval is a Build-phase integration task when wiring Salesforce experiences, not a launch or growth playbook. Integrations is the canonical shelf because the skill gates MCP tools (search_media_cms_channels, search_electronic_media) for asset lookup.
How it compares
An integration router skill, not a generative media or DAM replacement—always search existing libraries first.
Common Questions / FAQ
Who is searching-media for?
It is for developers and agent authors using Salesforce AFV patterns who need consistent, tool-gated search for existing visual media.
When should I use searching-media?
Use it during Build integrations whenever a prompt asks to find, search, get, or retrieve images or graphics from CMS or Data 360—before any MCP media tool invocation.
Is searching-media safe to install?
Check the Security Audits panel on this page; the skill expects MCP tools with network access to Salesforce content APIs scoped to your org.
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