sf-data

Manage Salesforce org data with describe-first validation and Bulk API 2.0.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Provides a validated, safety-first workflow to create, update, import, export, and remove Salesforce org data without guesswork or accidental production impact by enforcing describe-first checks, bulk-safe patterns, and clear cleanup strategies.

Core Features & Use Cases

  • CLI-first CRUD & Bulk: Wraps sf data commands and Bulk API 2.0 for single-record operations, large imports/exports, and tree imports.
  • Describe-first validation & safety: Inspects required/createable fields and picklists before writes, enforces savepoint/rollback and delete-by-pattern cleanup, and grades operations against a 130-point checklist.
  • Factories, anonymous Apex & assets: Provides Apex factory patterns, JSON/CSV/tree assets for hierarchical seeding, and guidance for 201/251+ record bulk-trigger testing.
  • Real-world example: Seed 251 Accounts with varied Industries to validate trigger bulkification, verify relationships, and then run a cleanup-by-pattern or savepoint rollback.

Quick Start

Create 251 test Account records with varied Industries in org dev using the sf-data workflow.

Frequently Asked Questions about sf-data

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

FAQPage Schema
How do I generate test data in Salesforce for bulk Apex trigger testing?

Salesforce test data generation for bulk trigger testing uses anonymous Apex factories and JSON/CSV tree assets to seed 251+ records with varied picklist values. This validates trigger bulkification and relationship integrity before cleanup rollback.

What's the best way to safely clean up imported records in a Salesforce org?

Safe Salesforce record cleanup enforces delete-by-pattern matching and savepoint rollback strategies. This prevents accidental production impact by evaluating operations against a 130-point safety checklist before executing any destructive data commands.

How do I validate required fields and picklists before importing data via the Salesforce Bulk API 2.0?

Required fields and picklist validation happens via a describe-first inspection of createable fields before any Bulk API 2.0 import. This pre-write check prevents failed batches by ensuring all incoming data matches the org's schema constraints.

Can I use the sf CLI for single-record CRUD and large tree imports in the same workflow?

The sf CLI handles both single-record CRUD operations and large hierarchical tree imports. It wraps sf data commands and Bulk API 2.0 to manage everything from individual record updates to complex parent-child data migrations.

What limitations exist when seeding hierarchical Salesforce data with anonymous Apex?

Anonymous Apex seeding is limited by transaction governor limits and requires JSON/tree assets for hierarchical relationships. It is best paired with savepoint rollback patterns to ensure test data doesn't persist and pollute the org environment.