Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
forcedotcom avatar

Searching Media

  • 2.1k installs
  • 763 repo stars
  • Updated July 24, 2026
  • forcedotcom/sf-skills

data360-query runs Data Cloud SQL, async queries, vector or hybrid search, and metadata describe via sf data360 CLI.

About

The data360-query skill covers Salesforce Data Cloud retrieve-phase work: sync SQL, paginated sqlv2, async query workflows, table describe, vector search, hybrid search, and search-index operations. Use when tasks involve sf data360 query, search-index, metadata, profile, or insight inspection. Delegate standard CRM SOQL to platform-soql-query, segment design to data360-segment, and STDM tracing to agentforce-observe. Gather org alias, result-set size needs, and table or index names first. Run diagnose-org with phase retrieve before relying on query surfaces. Prefer describe before guessing columns, sqlv2 or async for larger sets, and vector or hybrid only when index lifecycle is healthy. Examples include COUNT on ssot__Individual__dlm, describe table, vector and hybrid queries against Knowledge_Index with optional prefilter. Gotchas: Data Cloud SQL is not SOQL, double-quote table names, HNSW userValues often empty on create, and query describe needs a known DMO after readiness passes. Output reports retrieve task type, org, object, commands, verification, and next step.

  • Owns sf data360 query, search-index, metadata, profile, and insight retrieve tasks.
  • Run diagnose-org --phase retrieve before query or search-index work.
  • sqlv2 and async-create for medium and large result sets; describe before guessing fields.
  • Vector and hybrid search require healthy search-index lifecycle and real index names.
  • Not SOQL: double-quote DMO table names; delegate CRM SOQL to platform-soql-query.

Searching Media by the numbers

  • 2,131 all-time installs (skills.sh)
  • +7 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #46 of 2,066 Data Science & ML skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

searching-media capabilities & compatibility

Capabilities
retrieve phase org readiness classification · sync, sqlv2, and async sql execution · table describe and field discovery · vector and hybrid search with prefilter · search index list and curated json examples
Use cases
database · data analysis · research
From the docs

What searching-media says it does

Treat Data Cloud SQL as its own query language, not SOQL.
SKILL.md
Use vector search or hybrid search only when the search index lifecycle is healthy.
SKILL.md
npx skills add https://github.com/forcedotcom/sf-skills --skill searching-media

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.1k
repo stars763
Security audit2 / 3 scanners passed
Last updatedJuly 24, 2026
Repositoryforcedotcom/sf-skills

How do I query, describe, or search Salesforce Data Cloud objects with the community sf data360 plugin?

Run Salesforce Data Cloud SQL, async queries, vector or hybrid search, and metadata describe via sf data360 CLI with readiness checks.

Who is it for?

Data Cloud-enabled orgs needing SQL counts, exports, schema describe, or semantic vector or hybrid search.

Skip if: Skip for plain CRM SOQL, segment or calculated insight design, or STDM parquet session tracing.

When should I use this skill?

User runs Data Cloud SQL, async queries, vector search, search-index workflows, or metadata introspection.

What you get

Verified retrieve output with task type, org, object, commands run, row or schema proof, and suggested next step.

  • Retrieved media asset references
  • Routed CMS search results

Files

SKILL.mdMarkdownGitHub ↗

data360-query: Data Cloud Retrieve Phase

Use this skill when the user needs query, search, and metadata introspection for Data Cloud: sync SQL, paginated SQL, async query workflows, table describe, vector search, hybrid search, or search index operations.

When This Skill Owns the Task

Use data360-query when the work involves:

  • sf data360 query *
  • sf data360 search-index *
  • sf data360 metadata *
  • sf data360 profile * or sf data360 insight * inspection
  • understanding Data Cloud SQL results or query shape

Delegate elsewhere when the user is:

  • writing standard CRM SOQL only → platform-soql-query
  • designing segment or calculated insight assets → data360-segment
  • analyzing STDM/session tracing/parquet telemetry → agentforce-observe

---

Required Context to Gather First

Ask for or infer:

  • target org alias
  • whether the user needs quick count, medium result set, large export, schema inspection, or semantic search
  • table/index name if known
  • whether the task is read-only SQL or search-index lifecycle management

---

Core Operating Rules

  • Treat Data Cloud SQL as its own query language, not SOQL.
  • Run the shared readiness classifier before relying on query/search surfaces: node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json.
  • Use describe before guessing columns.
  • Prefer sqlv2 or async query flows for larger result sets.
  • Use vector search or hybrid search only when the search index lifecycle is healthy.
  • Keep STDM/parquet/session-tracing workflows out of this skill family.

---

Recommended Workflow

1. Classify readiness for retrieve work

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
# optional query-plane probe, only with a real table name
node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json

2. Choose the smallest correct query shape

sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query sqlv2 -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
sf data360 query async-create -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null

3. Use describe before guessing fields

sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null

4. Use vector or hybrid search only when an index exists

sf data360 search-index list -o <org> 2>/dev/null
sf data360 query vector -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
sf data360 query hybrid -o <org> --index Insurance_Index --query "weather damage coverage" --prefilter "Type_of_Insurance__c='Home'" --limit 10 2>/dev/null

5. Reuse curated search-index examples when creating indexes

Use the phase-owned examples instead of inventing JSON from scratch:

  • examples/search-indexes/vector-knowledge.json
  • examples/search-indexes/hybrid-structured.json

---

High-Signal Gotchas

  • Data Cloud SQL is not SOQL.
  • Table names should be double-quoted in SQL.
  • sqlv2 is better than ad hoc OFFSET paging for medium result sets.
  • async query is preferable for large results.
  • search-index operations and vector/hybrid queries depend on the index lifecycle being healthy.
  • Hybrid search can use --prefilter, but only on fields configured as prefilter-capable when the search index was created.
  • HNSW index parameters are typically read-only on create; leave userValues: [] unless the platform explicitly documents otherwise.
  • query describe is not a universal tenant probe; only run it with a known DMO or DLO table after broader readiness has been confirmed.

---

Output Format

Retrieve task: <sql / sqlv2 / async / describe / vector / search-index>
Target org: <alias>
Target object: <table or index>
Commands: <key commands run>
Verification: <query rows / schema / status>
Next step: <segment / harmonize / follow-up>

---

References

  • README.md
  • examples/search-indexes/vector-knowledge.json
  • examples/search-indexes/hybrid-structured.json
  • ../data360-orchestrate/assets/definitions/search-index.template.json
  • ../data360-orchestrate/references/plugin-setup.md
  • ../data360-orchestrate/references/feature-readiness.md

Related skills

Forks & variants (1)

Searching Media has 1 known copy in the catalog totaling 1.5k installs. They canonicalize to this original listing.

How it compares

Activate searching-media as the single media gateway in Salesforce agent stacks instead of invoking CMS search tools ad hoc.

FAQ

Is Data Cloud SQL the same as SOQL?

No. Treat Data Cloud SQL as its own language with double-quoted table names; use platform-soql-query for CRM SOQL.

When should I use async query instead of sql?

Prefer sqlv2 for medium sets and async-create for large exports after readiness diagnose passes.

What before vector or hybrid search?

Confirm search-index list health and use real index names; hybrid prefilter only on configured prefilter fields.

Is Searching Media safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Data Science & MLdatabasesanalytics

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.