Agent skill · data analytics · jeremylongshore
salesforce-load-scale
Test Salesforce integration capacity in an authorized non-production org with synthetic data, bounded load, org limits, and business-invariant checks. Use when planning scale. Trigger with "load test Salesforce".
Why this skill is useful
Provides specific load testing scripts and API limit budgeting strategies tailored for Salesforce integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires jq, k6 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 Bounded Load and Scale Validation Overview Measure useful throughput and failure behavior without treating Salesforce as an unconstrained HTTP endpoint or using production records as test data. Prerequisites Representative workload mix, service objectives, business invariants, expected growth, and capacity owner Dedicated authorized org, synthetic dataset, matching automation where possible, current limits, and peer-workload schedule Load stages, concurrency ceilings, stop thresholds, cleanup, reconciliation, and incident contacts 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 Salesforce enforces org-, edition-, license-, API-, Apex-, bulk-, event-, and concurrency-dependent limits. Limits and usage must be discovered in the target org, and non-production fidelity to production must be documented. Authentication Use a dedicated non-production principal with minimum objects and fields. Keep authorization outside load scripts and prevent tools, results, and fixtures from containing production tokens or personal data. Instructions 1. Model read, write, query, bulk, composite, async, and event workload proportions plus business deadlines and growth. 2. Capture org identity, edition, features, metadata, automation, relevant limits, peer workloads, and fidelity gaps. 3. Generate synthetic records with stable keys and safe relationships; precompute expected counts and outcomes. 4. Define stepped load, warm-up, duration, concurrency, request budget, stop thresholds, cooldown, cleanup, and rollback. 5. Run small stages while measuring latency, throughput, errors, limits, locks, async lag, event lag, automation, and business outcomes. 6. Stop on the first approved threshold; never retry hard limits or uncertain writes as additional load. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-load-scale--94c59e