Agent skill · data analytics · jeremylongshore
salesforce-performance-tuning
Analyze and tune Salesforce query, pagination, batching, caching, automation, and asynchronous performance using measured org evidence. Use when resolving latency or throughput problems. Trigger with "tune Salesforce performance".
Why this skill is useful
Provides specific SOQL optimization techniques and caching strategies that are not commonly known.
What it needs
Requires jsforce, lru-cache 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
Evidence-Driven Salesforce Performance Tuning Overview Optimize the end-to-end workload without trading correctness, permission enforcement, shared capacity, or recovery for a synthetic benchmark. Prerequisites Representative workload, latency and throughput objectives, business invariant, and current telemetry Queries, object volumes, selectivity, pagination, automation, locks, API mode, limits, and downstream timing Authorized performance org or sandbox, synthetic dataset, stop thresholds, and rollback owner 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 offers versioned query and limits resources; query performance feedback through REST explain is explicitly Beta. Query plans, indexes, object cardinality, automation cost, and limits depend on the target org and must be measured. Authentication Use an approved read-only performance principal first and a separately approved principal for canary writes. Do not collect broad record payloads or use administrator access to mask real permission cost. Instructions 1. Define the business invariant and measure end-to-end latency, throughput, error rate, API consumption, locks, retries, and downstream lag. 2. Trace time across client, network, authentication, query, pagination, automation, async jobs, event delivery, and reconciliation. 3. Inspect query shape, selected fields, predicates, cardinality, selectivity, ordering, pagination, and current metadata. 4. Use documented explain or query-plan tooling only under its current status and corroborate recommendations with measured tests. 5. Compare bounded changes to query design, caching, conditional requests, composite or bulk modes, concurrency, and scheduling. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-performance-tuning--fc862b