data360-query

Runs SQL, async queries, vector search, and metadata introspection against Salesforce Data Cloud.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill data360-query-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data360-query
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/data360-query
Command: npx skills add https://github.com/padjei/SF_Build --skill data360-query-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Salesforce Data Cloud requires a different query language than standard SOQL, plus specialized workflows for paginated results, async queries, vector search, and search index management. This Skill guides an AI agent through the correct Data Cloud retrieve-phase commands so queries are shaped properly and search indexes are used only when healthy. ## Core Features & Use Cases - Data Cloud SQL Execution: Run quick counts with sf data360 query sql, paginated results with sqlv2, and async query lifecycles for large exports. - Schema Introspection: Describe Data Cloud tables (DMOs/DLOs) before writing SQL to avoid guessing column names. - Vector and Hybrid Search: Execute semantic and hybrid queries with optional prefilters against existing search indexes, and manage the search index lifecycle. - Use Case: A developer needs to find knowledge articles semantically similar to "reset password" in Data Cloud. The Skill first checks org readiness, lists available search indexes, then runs a vector query with a result limit. ## Quick Start Ask the agent to run a Data Cloud SQL count query against the unified Individual table in your target org.

Frequently Asked Questions about data360-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a SQL query against Salesforce Data Cloud?▼

Use `sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"'` for quick counts. Data Cloud SQL is its own query language, not SOQL, and table names should be double-quoted.

How do I handle large Data Cloud query result sets?▼

Use `sf data360 query sqlv2` for medium result sets instead of ad hoc OFFSET paging, and `sf data360 query async-create` for large exports. The async lifecycle is preferable when result volumes are high.

What is the difference between vector and hybrid search in Data Cloud?▼

Vector search performs pure semantic similarity queries against a search index, while hybrid search combines semantic and structured retrieval and supports a `--prefilter` flag. Prefilters only work on fields configured as prefilter-capable when the index was created.

Does this skill work with standard Salesforce SOQL queries?▼

No, standard CRM SOQL is explicitly out of scope and delegated to the platform-soql-query skill. This skill only covers Data Cloud SQL, search indexes, and Data Cloud metadata introspection.

Why does my Data Cloud vector search fail?▼

Vector and hybrid queries depend on the search index lifecycle being healthy, so verify indexes with `sf data360 search-index list` first. Also run the readiness classifier `diagnose-org.mjs --phase retrieve` to confirm the org supports query surfaces.

What are the prerequisites for using Data Cloud query commands?▼

You need a Data Cloud-enabled Salesforce org and the external community sf data360 CLI plugin installed. The skill also recommends running the shared readiness classifier before relying on query or search surfaces.