Agent skill · software engineering · jeremylongshore
salesforce-core-workflow-b
Analyze and run the correct Salesforce high-volume operation using Bulk API 2.0, Composite, Graph, or sObject Collections with reconciliation. Use when handling large or dependent batches. Trigger with "run a Salesforce bulk workflow".
Why this skill is useful
Adds executable scripts for Salesforce Bulk API 2.0 and Composite API operations that streamline high-volume data handling.
What it needs
Requires jsforce installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce High-Volume and Composite Operation Overview Choose an API from workload evidence, make every batch restartable, and prove final state across partial, asynchronous, and dependent outcomes. Prerequisites Dataset classification, object dependencies, operation, expected counts, external IDs, and owners Current Bulk API 2.0, Composite, Graph, and sObject Collections documentation Org limits, automation cost, error budget, maintenance window, quarantine, and rollback plans Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Bulk API 2.0 performs asynchronous CSV ingest and large queries. Composite APIs combine supported REST subrequests with documented dependency and limit semantics; the best choice depends on volume, dependency graph, latency, and atomicity needs. Authentication Use a dedicated approved principal with only the required API, object, and field permissions. Keep tokens and payload data out of logs, plans, fixtures, and support bundles. Instructions 1. Profile row count, payload size, dependencies, ordering, latency, atomicity, retry, and reconciliation requirements. 2. Inspect org entitlements, current API versions, limits, object metadata, automation, external IDs, and lock risks. 3. Select Bulk API 2.0 for suitable asynchronous volume or the documented Composite resource for bounded dependent requests. 4. Normalize and validate data, split deterministic batches, assign stable source keys, and create a quarantine ledger. 5. Run a synthetic or read-only proof, then a small approved non-production write canary. 6. Execute within the approved capacity window while recording job, graph, batch, request, and result identifiers. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-core-workflow-b