forcedotcom/sf-skills / skills/experience-search-coordinate
experience-search-coordinate
VerifiedSearches 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.7 KB |
| assets/search-payload-template.json | config | 1.1 KB |
| references/content-route.md | markdown | 43.9 KB |
| references/content-type-discovery.md | markdown | 4.5 KB |
| references/media-route.md | markdown | 24.5 KB |
| references/scope-resolution.md | markdown | 2.1 KB |
references/scope-resolution.md
View on GitHub# Channel Scope Resolution — Full Reference
## Step 1 points 1-3 — discovering channel scope
1. **Explicit `channelId` given** (e.g. "search within channel 0apXX0000001001", or passed as an input to this skill) — use it directly as the scoped channel and skip straight to the scope rule in `SKILL.md` Step 1. Do not run uiBundle discovery in this case.
2. **Named uiBundle/app, no `channelId`** (e.g. "search in this uiBundle" or "search in the Homepage app") — locate that named uiBundle (e.g. `<sfdx-source>/uiBundles/<named-uiBundle>/public/content-metadata.json`) and read its `channelId` if present:
- **Found, with a `channelId`** — use it as the scoped channel, skip to the scope rule.
- **Not found, or found but no `channelId` present** — fall through to point 3 and scan every uiBundle as if the user hadn't named one.
3. **Otherwise, discover from uiBundles by scanning the local project — never gate this on server-side deployment status:**
- **Scan the project directly** for every `uiBundles/*/public/content-metadata.json` file using whichever directory-listing/glob capability your environment exposes. Do NOT run `sf org list metadata --metadata-type UIBundle` first and use its result to gate which bundles you check — a uiBundle's CMS channel can exist even when the uiBundle itself is not (yet, or ever) deployed to the currently-targeted org, so a server-side deployed-bundle list would wrongly exclude it.
- **For each `content-metadata.json` found**, read it and collect the `channelId` if present — no server-side field or API links a UIBundle to a CMS channel, so this local file is the only source for `channelId`.
- **Zero uiBundles with a `channelId`** — scope is public channels only.
- **Exactly one** — scope is public channels **plus** that `channelId`.
- **More than one** — call `ask_followup_question` with the question `"Multiple components have their own CMS channel. Which one should I search within (in addition to public channels)?"` and one **option** per uiBundle in the tool's `options` array — never as numbered lines inside the question text. Scope is public channels plus the selected `channelId`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |