sf-data

Automate Salesforce data access with SOQL, SOSL, and Bulk API 2.0.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/tomz/agent-skills --skill sf-data-tomz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-data
Source: https://github.com/tomz/agent-skills/tree/main/sf-data
Command: npx skills add https://github.com/tomz/agent-skills --skill sf-data-tomz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Salesforce data management tasks are complex due to layered security (OWD, sharing rules, and FLS), multiple data-access patterns (SOQL, SOSL, and Bulk API), and the need for reliable data movement during exports and imports.

Core Features & Use Cases

  • SOQL and SOSL querying for precise retrieval across Salesforce objects (Accounts, Contacts, Opportunities, etc.).
  • Data export and backup using Bulk API 2.0 and the sf data CLI for scalable data movement.
  • Data loading and upsert patterns with Data Loader and related tooling, including handling Record Types and respecting field-level security.

Quick Start

Query your Salesforce org with the sf data CLI to fetch a sample set of Account records.

Frequently Asked Questions about sf-data

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

FAQPage Schema
How do I export large volumes of Salesforce data using Bulk API 2.0?

Exporting large Salesforce data volumes with Bulk API 2.0 enables scalable data movement for backups. This approach supports bulk queries across standard objects like Accounts, Contacts, and Opportunities while respecting org-wide defaults and sharing rules.

What is the difference between SOQL and SOSL for Salesforce querying?

SOQL retrieves precise records from single objects like Accounts or Opportunities, while SOSL searches text across multiple objects simultaneously. Both methods respect field-level security and sharing rules during data access in Salesforce.

How do I handle Record Types and Field-Level Security when loading data into Salesforce?

Loading data with Record Types and Field-Level Security (FLS) requires mapping records to correct types and respecting field accessibility. Data Loader workflows validate FLS permissions during upserts to ensure secure, error-free imports across objects.

Can I use Data Loader for upsert operations across Accounts, Contacts, and Opportunities?

Data Loader supports upsert operations across standard objects like Accounts, Contacts, and Opportunities. Proper load ordering is essential when importing related records, and error handling ensures data integrity during the process.

What is the correct load ordering for importing related Salesforce records?

Correct load ordering imports parent objects like Accounts before dependent Contacts or Opportunities. This sequence maintains referential integrity during data loading, and error handling catches failures before they cascade across related records.

Why does my Salesforce data export fail due to Field-Level Security restrictions?

Salesforce data exports fail when Field-Level Security (FLS) blocks access to specific fields. Secure data handling requires checking FLS and org-wide defaults before querying or exporting, ensuring only accessible fields are retrieved.