Agent skill · forcedotcom
experience-search-coordinate
Searches for and retrieves existing content and media (articles, blogs, news, FAQs, events, products, images, logos, icons, photos, graphics, banners, hero images, audio clips, videos, documents) from Salesforce CMS or other connected sources. Use this skill ANY TIME a user says \"find\", \"search\", \"get\", \"fetch\", \"retrieve\", \"look up\", \"locate\", \"show me\", \"list\", or \"I need\" followed by content or media words like \"blog\", \"article\", \"news\", \"FAQ\", \"event\", \"product page\", \"image\", \"logo\", \"icon\", \"photo\", \"banner\", \"audio\", \"video\", \"document\". Also use for requests that mix both, like \"reuse existing assets\" for a page. Routes each intent to the correct sub-workflow — structured content search or media search — and can run both in the same request. Does not apply when the request is to generate NEW content or images from scratch, define content type schemas, or apply brand guidelines.
What it needs
About 11k tokens when loaded.
What this skill does
Search Coordinator Routes search requests to the correct sub-workflow — structured CMS content or media — and runs both when a request mixes the two. A → Read pointer below is a required action, not FYI — open that file before continuing past that point; this skill has drifted before from steps followed off memory. Scope This skill is for SEARCHING FOR existing content or media, not creating new content or images. Use this skill when the user wants to: Search for articles, blog posts, news, FAQs, events, products, or custom content Search for images, logos, icons, photos, graphics, banners, hero images, audio clips, videos, or documents Reuse existing assets instead of creating new ones, or any combination of the above in one request DO NOT use this skill when the user wants to: Generate new content (use experience-cms-content-generate) Generate new images (use image generation tools) Define content type schemas (use experience-cms-content-type-generate) Apply brand guidelines (use experience-cms-brand-apply) Create, edit, or publish content records Step 1: Determine Channel Scope Mandatory on every request that reaches it — never skip straight to Step 2. No phrasing of the request ("just find me an article," a plain keyword search, etc.) skips this step's local-file scan. If you're about to call searchmetadata in Step 2 without having scanned for uiBundles//public/content-metadata.json this turn, STOP and come back here first. 1. Explicit channelId given — use it directly, skip discovery entirely, proceed to the scope rule below. 2. Named uiBundle/app, no channelId — resolve that uiBundle's channelId; if it doesn't resolve, fall through to point 3 as if nothing was named. 3. Otherwise, discover from the local project — scan every uiBundles//public/content-metadata.json file (never gate this on server-side deployment status) and collect the channelIds found. Zero → public channels only. Exactly one → public plus that channel. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/experience-search-coordinate