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.
How do I install this agent skill?
npx skills add https://github.com/forcedotcom/sf-skills --skill experience-search-coordinateIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill coordinates searches for Salesforce CMS content and media. It demonstrates strong security practices by requiring user confirmation for search parameters, providing manual selection for results, and explicitly filtering internal authenticated URLs to prevent data exposure. The skill utilizes standard Salesforce developer tools and follows a structured, human-in-the-loop workflow.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
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 search_metadata in Step 2 without having scanned for uiBundles/*/public/content-metadata.json this turn, STOP and come back here first.
- Explicit
channelIdgiven — use it directly, skip discovery entirely, proceed to the scope rule below. - Named uiBundle/app, no
channelId— resolve that uiBundle'schannelId; if it doesn't resolve, fall through to point 3 as if nothing was named. - Otherwise, discover from the local project — scan every
uiBundles/*/public/content-metadata.jsonfile (never gate this on server-side deployment status) and collect thechannelIds found. Zero → public channels only. Exactly one → public plus that channel. More than one → ask the user which one viaask_followup_question.
→ Read references/scope-resolution.md § "Step 1 points 1-3" for the full discovery mechanics before acting on points 1-3 above. Proceed to Step 2 once scope is determined.
Scope rule (applies whether the channelId was user-provided or discovered): scope is always public channels (contentAccessScope: "Public", no channelIds field) plus that one channelId (a separate call with channelIds set to it, no contentAccessScope field) — never resolve a separate ID to represent "public," and never send contentAccessScope and channelIds in the same call. This scope decides how many keyword search calls Steps 3 and 4 make: no channelId in scope → one search call (public channels only). A channelId in scope → two search calls (public channels, then that specific channelId), with results merged before presenting. Data 360 hybrid search ignores channel scope entirely and is always a single call regardless of scope — see Step 3/Step 4 point 3.
Step 2: Determine Content Type and Route
Precondition: Step 1 must have already run in this turn (its channel-scope result is what point 5 below carries into Step 3/4). Step 1 runs unconditionally — even for a plain keyword search with no obvious channel angle, not only when the request names a channel or app.
-
Identify one or more distinct search intents in the request (e.g. "find a press release about our launch and a hero image for the page" is two intents). Run the rest of this step once per intent.
If intents span both routes, sequence the routes — never interleave or merge them: run the Media Route (Step 4) to full completion for every media intent first, then the Content Route (Step 3) for every content intent. See Step 5.
-
Call
search_metadataon themetadata-groundingMCP server using the intent itself as the query. Nofiltersarray support —metadataTypeis the only narrowing parameter, passed top-level:search_metadata({ query: "<the user's intent>", metadataType: "ContentTypeBundle", limit: 100 })
Each candidate already includes a full composite identifier (e.g. 00Dxx0000000000AAA::0T1xx0000000001AAA::ContentTypeBundle) — use it as returned; never reconstruct it.
Check the outcome before doing anything else:
metadata-groundingis unavailable (the call errors/times out) — you MUST callget_content_types_for_workspace(the workspace content-type fallback) before any Step 3/4 search tool; do not attemptquery_metadata, there's nothing to look up, and do not skip straight to a search tool on an assumed FQN.- Zero candidates returned — ask the user one clarifying question to narrow the intent (
ask_followup_question, same question/options as the "intent itself is ambiguous" case at the end of this step), then retrysearch_metadataonce with the clarified query:- Still zero candidates after that one retry — apply the workspace content-type fallback. Do not ask a second clarifying question.
- One or more candidates on the retry — continue to point 3.
- One or more candidates on the first call — continue to point 3.
Fallback chain when search_metadata doesn't produce a usable candidate list → Read references/content-type-discovery.md before running it: "Workspace content-type fallback" first, then "Wording fallback" as a last resort.
-
Call
query_metadatawith each candidate's identifier from point 2 (cap at top 5, batched into onemetadataIdentifiersarray):query_metadata({ metadataIdentifiers: ["00Dxx0000000000AAA::0T1xx0000000001AAA::ContentTypeBundle"] })Read each entry's
typeDetails[].properties—mixins,typeClasses, andapiNamelive there, not in thesearch_metadataresponse. -
Filter for supported types first, THEN decide the route among survivors — do not conflate the two:
- Discard any candidate whose
properties.mixinslackssfdc_cms:deliveryApiEnabled— only delivery-API-enabled types are searchable. - Of the remainder, discard any whose
properties.typeClasseslackssfdc_cms__structured. This is the single "supported for search" gate, not a content/media split —sfdc_cms__structuredappears on both structured-content types and media types, so it only separates searchable types from unsearchable ones (e.g.sfdc_cms__emailcarriessfdc_cms__contentbut notsfdc_cms__structured, and must be discarded). - Zero survive — tell the user which types were found but aren't supported, then stop (don't guess a route). Some, but not all, survive — tell the user which got filtered out (plain statement, not a question), then continue with survivors. All survive — no message needed. → Read
references/content-type-discovery.md§ "Filter-result messages" for exact wording. - Route on the top-ranked survivor's
properties.typeClasses(order returned bysearch_metadata): containssfdc_cms__media→ Media Route (Step 4); otherwise → Content Route (Step 3). - Collect the FQN(s) — the top-ranked survivor's
properties.apiName. Add other surviving candidates' FQNs too if clearly relevant to the same intent and sharing the same classification, passing all as one comma-separatedcontentTypeFqnvalue rather than searching per type.
- Discard any candidate whose
-
Carry the scope from Step 1 (public channels only, or public channels plus a
channelId) into whichever route is invoked — see thechannelIdsfield in each route below.
If intent itself is ambiguous (e.g. "find me some content" with no hint of type or subject) → Read references/content-type-discovery.md § "Intent itself is ambiguous" for the exact question/options before calling search_metadata. Do not guess.
Step 3: Content Route
→ Read references/content-route.md § "Step 3: Content Route" and follow it for each intent Step 2 routed here.
Step 4: Media Route
→ Read references/media-route.md § "Step 4: Media Route" and follow it for each intent Step 2 routed here.
Step 5: Present Combined Results
When a request mixes media and content intents, run the two routes sequentially, each to full completion, not interleaved and not merged into one combined presentation:
- Media Route first — for every media intent, run Step 4 in full: present sources, build/confirm the query, search, present results, let the user select, and (point 6) offer the
experience-cms-content-renderhand-off (Yes/No). Finish this entire route — including the offer — before starting the Content Route. - Content Route second — for every content intent, run Step 3 in full: present sources, build/confirm the query, search, present results grouped by content type (channel shown per-item), let the user select, and (point 6) offer the
experience-cms-content-renderhand-off if a uiBundle channel is in scope.
Each route's results are labeled and presented on their own (e.g. "Images:" for the Media Route's output, then "Articles:" for the Content Route's) — never merge the two into one undifferentiated list, and never hold Media Route's results back to present alongside Content Route's.
Error Handling
| Error | Response |
|---|---|
| No content or media search tools (keyword or hybrid) found via introspection | "No content search connection is configured. Please connect a content-readonly MCP server." |
| Neither media tool available | "No automated media search sources are currently configured. Please provide a direct URL or asset library path." |
metadata-grounding unavailable or no content types match | Apply the fallback chain in references/content-type-discovery.md — do not block or ask for an FQN |
| No search results (either route) | "No [content/media] found. Try broader keywords, removing descriptive terms, or a different [content type/source]." |
| Invalid user selection | Re-display options and ask again |
| Tool returns error (invalid input, missing argument, or otherwise) | Show error message, offer retry with corrected parameters on that same tool — never fall through to the other route's search tool as a workaround (see Key Principle 3); hybrid language errors: offer one no-language retry, with the user's OK (see each route's reference) |
| Search tool on the connected server returns a server error (5xx, timeout, connection failure — not "no results") | Fail the call — do NOT silently retry against a different server. Tell the user to check that server's connection/session and wait before retrying. |
Never silently fail on a route the user asked for. If one route in a mixed request comes up empty, still present the other route's results and say so explicitly. This does not mean substituting a different server when the connected one errors — see the server-error row above.
Key Principles
- Resolve channel scope first — determine channel scope (Step 1) before any content-type discovery or search
- Search first, route second —
search_metadata+query_metadatadecide the route; fall back toget_content_types_for_workspace, then intent wording, only when that comes up empty (Step 2) - Never cross-route, including on failure — content requests never hit media search tools and vice versa; if a route's search tool errors for any reason, fix and retry that same tool or stop and report the error — never fall through to the other route's tool as a workaround
- Metadata grounding is mandatory for content — discover content type FQNs dynamically, never hardcode them
- Both routes start text-only — present sources and wait before any tool call
- Confirm before searching (both routes) — user approves query parameters before execution
- Never auto-select — always wait for user choice, across channel scope and both routes
- Run mixed requests sequentially, Media Route first — complete it fully (including the render offer) before starting the Content Route; present each route's results as its own labeled set, never merged
- Handle errors gracefully — clear feedback and alternatives, per route
- Offer to render, don't assume — both routes require Yes/No confirmation before the hand-off; only the gating differs — Content Route offers it only when a uiBundle channel was actually in scope, Media Route always offers it
- Never fail over to a different server on a server error — fail the call and tell the user to check that server's session; don't silently retry elsewhere
- Group by content type, never by channel — in both routes, channel is always a per-item field, never the group heading
- Disambiguate channel at selection, not before — an item is shown once at presentation regardless of its delivery-details array length; only after selection do you ask which channel's copy to use, one option per entry by
managedContentChannelDetails.name, in both routes - Unauthenticated URL is public-channel-only —
PUBLIC_UNAUTHENTICATED/COMMUNITYentries only; never aWEB_APP(uiBundle) entry'scontentUrl, in either route
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/forcedotcom/sf-skills/experience-search-coordinate">View experience-search-coordinate on skillZs</a>