From jaganpro-sf-skills-7
Retrieves Salesforce Data Cloud data via sf data360 CLI with sync/async SQL queries, vector/hybrid search, search-index workflows, and metadata introspection.
npx claudepluginhub jaganpro/sf-skillsThis skill uses the workspace's default tool permissions.
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.
Guides Salesforce Data Cloud (2025) integration patterns and architecture: data ingestion from 200+ sources, harmonization, identity resolution, real-time activation, zero-copy querying.
Orchestrates Salesforce Data Cloud multi-phase pipelines (connect→prepare→harmonize→segment→act), manages data spaces/kits, and troubleshoots cross-phase workflows via sf data360 CLI.
Query and manage Salesforce CRM data via Salesforce CLI (sf). Run SOQL/SOSL queries, inspect schemas, CRUD records, bulk import/export, execute Apex, deploy metadata, raw REST API calls.
Share bugs, ideas, or general feedback.
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.
Use sf-datacloud-retrieve when the work involves:
sf data360 query *sf data360 search-index *sf data360 metadata *sf data360 profile * or sf data360 insight * inspectionDelegate elsewhere when the user is:
Ask for or infer:
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json.sqlv2 or async query flows for larger result sets.node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
# optional query-plane probe, only with a real table name
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
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
sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
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
Use the phase-owned examples instead of inventing JSON from scratch:
examples/search-indexes/vector-knowledge.jsonexamples/search-indexes/hybrid-structured.jsonsqlv2 is better than ad hoc OFFSET paging for medium result sets.--prefilter, but only on fields configured as prefilter-capable when the search index was created.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.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>